Use when a complete research workflow — its instructions, skills, data boundaries, and tool connections — must be assessed for portability across AI agents or environments, so each component is explicitly mapped before migration rather than assumed to transfer.
The English summary is being prepared. Showing the original description.
Use when a Claude Code session loops, drifts from scope, claims a fix that CI rejects, hits context, PATH, or permission walls, or fails in a way another retry will not solve and a root cause diagnosis is needed instead.
The English summary is being prepared. Showing the original description.
Use when a draft in Turkish, English, or both reads as AI-generated and needs revision that removes machine writing patterns and translation calques while preserving meaning, citations, statistics, and the author's voice.
The English summary is being prepared. Showing the original description.
Use when authorship order, CRediT contribution roles, or AI-assistance attribution must be recorded transparently for a manuscript, when an author dispute needs an evidence trail, or before a contributorship statement is required at submission; this skill maintains the human-attribution ledger of who contributed what and in which role (authorship order, CRediT taxonomy, revision responsibilities), which is distinct from the disclosure-metadata audit owned by ai-disclosure-auditor.
The English summary is being prepared. Showing the original description.
Use when a high-stakes analysis, citation set, or decision should be checked by a second independent AI agent that verifies rather than decides, or when disagreement between agents must be surfaced for the human to adjudicate.
The English summary is being prepared. Showing the original description.
Use when a research proposal needs work packages, milestones, deliverables, a timeline, a risk register, and budget-justification scaffolding, while keeping scientific claims and feasibility honest and human-owned.
The English summary is being prepared. Showing the original description.
Use when a research note system needs architecture, when MOCs, frontmatter standards, and retrieval patterns must be designed for years of work, or when an existing vault has outgrown its structure and must migrate without breaking years of links.
The English summary is being prepared. Showing the original description.
Use when a construct, scale, or key term crosses Turkish and English and conceptual equivalence must be audited: translation and back-translation, construct drift, and culturally bound meaning, before measurement or cross-cultural claims.
The English summary is being prepared. Showing the original description.
Use when adapting academic findings for a public audience (op-ed, social post, podcast) and the simplification must stay evidence-faithful, avoid overclaiming, respect embargoes, and disclose AI assistance.
The English summary is being prepared. Showing the original description.
Use when coding interviews, focus groups, or open-ended responses with AI assistance, when a codebook needs building or auditing, when intercoder reliability must be computed, or when qualitative quotes need integrity checks before publication.
The English summary is being prepared. Showing the original description.
Use when reviewer comments arrive and each one needs a tracked decision, when a revise and resubmit letter must map every comment to a manuscript change, or when contradictory reviewer demands need evidence-based, editor-facing framing.
The English summary is being prepared. Showing the original description.
Use when a researcher asks where to start, which project skill fits the current stage of a study, or in what order literature scoping, source access, vault upkeep, drafting, citation verification, disclosure, and review response should run.
The English summary is being prepared. Showing the original description.
Use when sources must stay traceable across sessions and years, when each reference needs a passport recording where it was found, how it was verified, and where it is cited, or when a draft needs a cited-but-unverified sweep before submission.
The English summary is being prepared. Showing the original description.
Use when selecting a statistical test with AI consultation, when assumptions need checking against the actual data, when an analysis plan or decision log must be written before running anything, or when results need APA-style reporting with effect sizes.
The English summary is being prepared. Showing the original description.
Use when designing a course, assessment, or student-feedback workflow and deciding where AI assistance is acceptable, when grading or feedback must stay within academic-integrity and FERPA/KVKK boundaries, or when AI-use rules for students need stating.
The English summary is being prepared. Showing the original description.
Use before a tag, GitHub release, or Zenodo archive, when README, CATALOG, CHANGELOG, CITATION.cff, the disclosure aggregate, and skill discovery must agree, or when a go or no-go release verdict needs recorded evidence behind it.
The English summary is being prepared. Showing the original description.
Use when choosing or configuring MCP servers for research work, when a literature, reference manager, or scholarly search server needs a trust check before installation, or when an existing research tool stack needs a data flow and permission audit.
The English summary is being prepared. Showing the original description.
Use when a study's materials, data, code, or preprint need an open-science release: license choice, a persistent DOI (Zenodo/OSF), README and metadata, and an access-and-embargo decision that respects ethics constraints.
The English summary is being prepared. Showing the original description.
Use when authoring a new manuscript, thesis chapter, or abstract from scratch in Turkish and English in parallel — building the claim skeleton first, then drafting Turkish and re-authoring English — not for auditing parity between existing versions.
The English summary is being prepared. Showing the original description.
Use when a systematic, scoping, or rapid review needs a reproducible pipeline: protocol framing (PICO/SPIDER/PCC), a logged search string, title/abstract and full-text screening with recorded exclusion reasons, and PRISMA flow counts, with the human as the deciding screener.
The English summary is being prepared. Showing the original description.
Use when choosing a journal for a finished or nearly finished manuscript, when index status in Scopus, SSCI, ESCI, or TR Dizin must be confirmed, when a venue looks predatory, or when a cover letter needs drafting from the manuscript's actual claims.
The English summary is being prepared. Showing the original description.
Use when a source must be reached through DergiPark, ULAKBIM TR Dizin, HEAL-Link, YOK Thesis Center, or an institutional library route, when off-campus access fails, or when a lawful retrieval plan is needed for Turkish, Greek, or European materials.
The English summary is being prepared. Showing the original description.
Use for the search-planning stage of a literature review, when database lanes and language layers must be chosen, when DOI coverage policy is unclear, or when inclusion and exclusion criteria need drafting before any source is read; not for running the screening and PRISMA pipeline of a formal review, which is prisma-scoping-review-pipeline.
The English summary is being prepared. Showing the original description.
Use when a reference list needs APA 7 cleanup, when DOIs must be confirmed real against Crossref or PubMed, when the user asks whether AI-suggested citations actually exist, or when a manuscript needs a citation hygiene pass before submission or defense.
The English summary is being prepared. Showing the original description.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)