template-workflows
Router and workflow hub for the Research Project Template — code, tests, manuscripts, pipeline, validation, docs, and reproducibility. USE WHEN the user wants to audit the repo, debug ./run.sh or execute_pipeline.py, add a feature, write tests, scaffold a manuscript, verify claims, fix cross-references, run validation gates, refactor, or prepare a Zenodo release, research a topic, write/review/revise a paper, or run a research-to-publication workflow — even if they never say "prompt", "skill", or docs/prompts. Also USE WHEN intent is ambiguous ("something wrong with my manuscript", "full health check", "fix the pipeline") — pick ONE child skill from the routing table and follow it. Do NOT use for generic homework, unrelated app security scans, or casual PDF summarization.
Best use case
template-workflows is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Router and workflow hub for the Research Project Template — code, tests, manuscripts, pipeline, validation, docs, and reproducibility. USE WHEN the user wants to audit the repo, debug ./run.sh or execute_pipeline.py, add a feature, write tests, scaffold a manuscript, verify claims, fix cross-references, run validation gates, refactor, or prepare a Zenodo release, research a topic, write/review/revise a paper, or run a research-to-publication workflow — even if they never say "prompt", "skill", or docs/prompts. Also USE WHEN intent is ambiguous ("something wrong with my manuscript", "full health check", "fix the pipeline") — pick ONE child skill from the routing table and follow it. Do NOT use for generic homework, unrelated app security scans, or casual PDF summarization.
Teams using template-workflows should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/prompts/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How template-workflows Compares
| Feature / Agent | template-workflows | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Router and workflow hub for the Research Project Template — code, tests, manuscripts, pipeline, validation, docs, and reproducibility. USE WHEN the user wants to audit the repo, debug ./run.sh or execute_pipeline.py, add a feature, write tests, scaffold a manuscript, verify claims, fix cross-references, run validation gates, refactor, or prepare a Zenodo release, research a topic, write/review/revise a paper, or run a research-to-publication workflow — even if they never say "prompt", "skill", or docs/prompts. Also USE WHEN intent is ambiguous ("something wrong with my manuscript", "full health check", "fix the pipeline") — pick ONE child skill from the routing table and follow it. Do NOT use for generic homework, unrelated app security scans, or casual PDF summarization.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
SKILL.md Source
# Template workflow hub When intent is clear, open the matching child `SKILL.md` directly. When ambiguous, use the routing table, then load exactly one child skill. ## Ambiguous routing - **Broken refs / "manuscript wrong"** — ask whether the failure is pipeline (validate/render) or prose (tokens/registry). Route to [manuscript-cross-references](manuscript-cross-references/SKILL.md), [validation-quality](validation-quality/SKILL.md), or [manuscript-claim-verification](manuscript-claim-verification/SKILL.md). Do **not** open [code-development](code-development/SKILL.md). - **Example:** "refs broken, not sure if pipeline or prose" → clarify stage vs registry; default to cross-refs when `[[FIG:]]` / `labels.yaml` mentioned. - **Full health check with no symptom** → [comprehensive-assessment](comprehensive-assessment/SKILL.md). - **Generic coding homework or unrelated app** → do not load template workflow skills. ## Routing table | Symptom or goal | Child skill | | --- | --- | | Research question, literature review, fact check, systematic review | [deep-research/SKILL.md](deep-research/SKILL.md) | | Draft, outline, revise, format, or disclose AI use in a manuscript | [academic-paper/SKILL.md](academic-paper/SKILL.md) | | Peer review, methodology review, re-review, or calibration | [academic-paper-reviewer/SKILL.md](academic-paper-reviewer/SKILL.md) | | Research → write → verify → review → revise → finalize | [academic-pipeline/SKILL.md](academic-pipeline/SKILL.md) | | Methods, methodology, stage contracts, artifact/evidence wiring | [methods-orchestration/SKILL.md](methods-orchestration/SKILL.md) | | Pipeline stage failed, stuck, or flaky | [pipeline-debugging/SKILL.md](pipeline-debugging/SKILL.md) | | Regenerate-from-clean / determinism / double-run diff | [reproducibility-audit/SKILL.md](reproducibility-audit/SKILL.md) | | Triple-check every manuscript claim; pre-submission | [manuscript-claim-verification/SKILL.md](manuscript-claim-verification/SKILL.md) | | `[[FIG:]]` / `labels.yaml` registry audit | [manuscript-cross-references/SKILL.md](manuscript-cross-references/SKILL.md) | | New manuscript + project from research brief | [manuscript-creation/SKILL.md](manuscript-creation/SKILL.md) | | Literature search corpus synthesis (LLM blocks) | [literature-synthesis/SKILL.md](literature-synthesis/SKILL.md) | | Full repo audit (tests, docs, manuscript, pipeline) | [comprehensive-assessment/SKILL.md](comprehensive-assessment/SKILL.md) | | Validation CLI, gates, markdown/PDF checks | [validation-quality/SKILL.md](validation-quality/SKILL.md) | | New module or algorithm (thin orchestrator) | [code-development/SKILL.md](code-development/SKILL.md) | | Tests under no-mocks policy | [test-creation/SKILL.md](test-creation/SKILL.md) | | End-to-end feature across layers | [feature-addition/SKILL.md](feature-addition/SKILL.md) | | Clean-break refactor with migration | [refactoring/SKILL.md](refactoring/SKILL.md) | | New `infrastructure/*` package | [infrastructure-module/SKILL.md](infrastructure-module/SKILL.md) | | AGENTS.md / README.md for a directory | [documentation-creation/SKILL.md](documentation-creation/SKILL.md) | **New project scaffold (one-shot):** [docs/guides/new-project-one-shot-prompt.md](../guides/new-project-one-shot-prompt.md) — not a separate skill; link from manuscript-creation when starting from zero. ## Conventions (all children) - Project names: [`docs/_generated/active_projects.md`](../_generated/active_projects.md) — never hard-code rotating paths. - Business logic: `infrastructure/` or `projects/<name>/src/` only; scripts orchestrate. - Tests: no mocks; infra ≥60%, project ≥90% unless CI documents an exception. - Metrics: measure with pytest or cite [`docs/_generated/canonical_facts.md`](../_generated/canonical_facts.md). ## Discovery These skills are indexed in `.cursor/skill_manifest.json` (`uv run python -m infrastructure.skills write`). Human index: [README.md](README.md). ## External design note This workflow set includes original, template-native adaptations of patterns observed in [Imbad0202/academic-research-skills](https://github.com/Imbad0202/academic-research-skills): mode registries, data-access labels, provenance checkpoints, and benchmark disclosure. ARS content is not vendored or copied because ARS is CC-BY-NC-4.0 while this repository is Apache-2.0.