template-validation-quality
Run validation CLI, prerender, markdown/PDF/integrity gates, and QA workflows for the Research Project Template. USE WHEN validate manuscript, check PDF for ?? refs, prerender gate, link checker, output integrity, or pre-commit validation — even without validation_quality prompt.
Best use case
template-validation-quality is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Run validation CLI, prerender, markdown/PDF/integrity gates, and QA workflows for the Research Project Template. USE WHEN validate manuscript, check PDF for ?? refs, prerender gate, link checker, output integrity, or pre-commit validation — even without validation_quality prompt.
Teams using template-validation-quality 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/validation-quality/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How template-validation-quality Compares
| Feature / Agent | template-validation-quality | 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?
Run validation CLI, prerender, markdown/PDF/integrity gates, and QA workflows for the Research Project Template. USE WHEN validate manuscript, check PDF for ?? refs, prerender gate, link checker, output integrity, or pre-commit validation — even without validation_quality prompt.
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
# Validation quality Prefer **actual CLI entrypoints** in [`CLAUDE.md`](../../../CLAUDE.md) — not illustrative Python stubs. ## Natural invoke - "Validate markdown under projects/templates/template_prose_project/manuscript/" - "PDF has unresolved references — run validation" - "Strict prerender before render" ## Inputs to confirm - **Target** — manuscript dir, PDF path, or `output/<project>/`. - **Project** — from active_projects when path ambiguous. ## Workflow 1. **Source markdown** — `infrastructure.validation.cli markdown` and/or `prerender`. 2. **Citations** — `infrastructure.reference.citation validate` on `.bib`. 3. **Links** — `infrastructure.validation.cli links --repo-root .` 4. **PDF** — after render: `cli pdf output/<project>/pdf/` 5. **Integrity** — `cli integrity output/<project>/` 6. **Report** — diagnostic codes from validation; path + fix per issue. ## Deliverables - Command list with exit codes - Issue table: code | file | message | fix ## Verification commands ```bash uv run python -m infrastructure.validation.cli prerender projects/<project>/manuscript --repo-root . uv run python -m infrastructure.validation.cli markdown projects/<project>/manuscript --repo-root . --strict uv run python -m infrastructure.reference.citation validate projects/<project>/manuscript/references.bib uv run python -m infrastructure.validation.cli links --repo-root . uv run python -m infrastructure.validation.cli pdf output/<project>/pdf/ uv run python -m infrastructure.validation.cli integrity output/<project>/ uv run python -m infrastructure.prose.cli report projects/<project>/manuscript ``` ## When NOT to use - **Failing pipeline stage triage** → [pipeline-debugging](../pipeline-debugging/SKILL.md) - **Claim-by-claim manuscript audit** → [manuscript-claim-verification](../manuscript-claim-verification/SKILL.md) ## References - [`infrastructure/validation/AGENTS.md`](../../../infrastructure/validation/AGENTS.md)