template-comprehensive-assessment
Full checkout audit for the Research Project Template — tests, architecture, docs, manuscript, pipeline. USE WHEN user asks for comprehensive assessment, full repo review, health check across projects, audit everything, or pre-merge sanity sweep for template exemplars — even without naming docs/prompts or a skill. Not for single failing stage only.
Best use case
template-comprehensive-assessment is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Full checkout audit for the Research Project Template — tests, architecture, docs, manuscript, pipeline. USE WHEN user asks for comprehensive assessment, full repo review, health check across projects, audit everything, or pre-merge sanity sweep for template exemplars — even without naming docs/prompts or a skill. Not for single failing stage only.
Teams using template-comprehensive-assessment 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/comprehensive-assessment/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How template-comprehensive-assessment Compares
| Feature / Agent | template-comprehensive-assessment | 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?
Full checkout audit for the Research Project Template — tests, architecture, docs, manuscript, pipeline. USE WHEN user asks for comprehensive assessment, full repo review, health check across projects, audit everything, or pre-merge sanity sweep for template exemplars — even without naming docs/prompts or a skill. Not for single failing stage only.
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.
SKILL.md Source
# Comprehensive assessment ## Natural invoke - "Audit the whole repo for template_active_inference, template_autoresearch_project, template_code_project, template_prose_project, and template_template" - "Full health check — tests, docs, manuscript, pipeline" - "What's broken across all active projects?" ## Inputs to confirm - **Project(s)** — names from [`docs/_generated/active_projects.md`](../../_generated/active_projects.md) or "all active". - **Scope** — single project vs multi-project (one pytest process per project test dir). ## Workflow Work through: 1. **Tests** — appropriate pytest invocations; one project test dir per project. Coverage: infra ≥60%, project ≥90% unless CI exception. No mocks ([`docs/rules/testing_standards.md`](../../rules/testing_standards.md)). 2. **Architecture** — thin orchestrators in `scripts/`; algorithms in `projects/<n>/src/` or `infrastructure/`. No cross-project imports. 3. **Documentation** — meaningful dirs have accurate AGENTS.md + README.md; links resolve; link `_generated/active_projects.md`, do not duplicate roster. 4. **Manuscript** — Pandoc-crossref + `.bib` → [`docs/guides/manuscript-semantics.md`](../../guides/manuscript-semantics.md). Registry `labels.yaml` + `[[FIG:]]` → [manuscript-cross-references](../manuscript-cross-references/SKILL.md). Validate markdown; PDF/logs if outputs exist. 5. **Pipeline** — core vs full DAG, optional LLM stages, copy to `output/<name>/` per CLAUDE.md / RUN_GUIDE. ## Deliverables - Executive summary (pass/fail per area). - Concrete issues: path, symptom, suggested fix. - Commands run + raw exit status. - Do not invent coverage percentages. ## Verification commands ```bash uv sync uv run pytest projects/<project>/tests/ --cov=projects/<project>/src --cov-fail-under=90 -q uv run pytest tests/infra_tests/ --cov=infrastructure --cov-fail-under=60 -q uv run python scripts/01_run_tests.py --project <project> uv run python -m infrastructure.validation.cli markdown projects/<project>/manuscript/ uv run python -m infrastructure.validation.cli prerender projects/<project>/manuscript --repo-root . ``` ## When NOT to use - **Single failing stage** → [pipeline-debugging](../pipeline-debugging/SKILL.md) - **Claim-by-claim manuscript pass** → [manuscript-claim-verification](../manuscript-claim-verification/SKILL.md) - **Determinism only** → [reproducibility-audit](../reproducibility-audit/SKILL.md)