AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Audit Docs

skill-talont-org-autoskillit-audit-docs · by TalonT-Org

>

No reviews yet
0 installs
11 views
0.0% view→install

Install

$ agentstack add skill-talont-org-autoskillit-audit-docs

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-talont-org-autoskillit-audit-docs)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
20d ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Audit Docs? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Documentation Audit Skill

Audit all documentation sources for drift, staleness, and inconsistency against actual codebase behavior.

When to Use

  • User says "audit docs", "check documentation", "docs audit", "documentation review", "docs drift", "stale docs"

Critical Constraints

NEVER:

  • Modify any source files
  • Update an existing report — always generate a new one
  • Compare doc-to-doc without first grounding claims in actual code behavior
  • Run subagents in the background (run_in_background: true is prohibited)

ALWAYS:

  • Ground every cross-reference finding in what the code actually does (not what other docs say)
  • Use subagents for parallel exploration
  • Write report to {{AUTOSKILLIT_TEMP}}/audit-docs/docs_audit_{YYYY-MM-DD_HHMMSS}.md
  • Provide file:line references for every finding
  • Categorize findings by severity (CRITICAL, HIGH, MEDIUM, LOW)
  • Produce a usable report even when one or more subagents fail

Documentation Sources

Enumerate and audit all of the following:

  • CLAUDE.md — project instructions, architecture tree, file path references, tool/skill counts, layer descriptions
  • docs/architecture/**/*.md — component names, module paths, layer assignments
  • docs/requirements/**/*.md and docs/specs/**/*.md — API surface, behavioral contracts
  • All README.md files at any depth in the repository
  • Module/class/function docstrings in Python files under src/
  • Recipe YAML description, summary, and note fields in .autoskillit/recipes/ and src/autoskillit/recipes/

Inconsistency Categories

Flag findings in these categories (maps to REQ-SKILL-004):

  • Stale claims — doc asserts X, actual code behavior is Y
  • Orphaned references — doc mentions a file, module, tool, class, or skill that no longer exists
  • Missing docs — new subsystem or module with no mention in CLAUDE.md tree or arch docs
  • Path/name drift — hyphen-vs-underscore mismatches, renamed symbols, old module paths
  • Count mismatches — CLAUDE.md states N tools/skills/hooks but actual count differs
  • Inter-doc contradictions — CLAUDE.md says A, arch doc says B about the same entity

Audit Workflow

  1. Pre-flight: Verify {{AUTOSKILLIT_TEMP}}/audit-docs/ directory exists; create it if not.
  1. Familiarization wave — spawn 6 parallel subagents, one per subsystem group. Each subagent reports: actual module/component names, exported symbols, behavioral summary (2–5 sentences per module). If any subagent fails, record the gap and continue.

| Agent | Subsystems | Focus | |---|---|---| | Agent 1 | core/, config/ | What these modules actually expose and do | | Agent 2 | execution/, workspace/ | Runtime orchestration and workspace lifecycle | | Agent 3 | recipe/, migration/ | Recipe schema, rules, validation, migration engine | | Agent 4 | server/ | MCP tool surface, gating, lifespan, factory | | Agent 5 | cli/, hooks/ | CLI commands, hook scripts, what each does | | Agent 6 | skills/, skills_extended/ | Bundled skills, categories, tiers |

  1. Doc inventory — enumerate all documentation sources (list files found under each source category above).
  1. Cross-reference wave — spawn 4 parallel subagents, each checking one doc domain against the familiarization findings:

| Agent | Domain | What to check | |---|---|---| | Agent A | CLAUDE.md | Architecture tree accuracy, file path references, tool/skill counts, layer descriptions | | Agent B | docs/architecture/** | Component names, module paths, layer assignments | | Agent C | docs/requirements/** and docs/specs/** | API surface, behavioral contracts | | Agent D | Recipe YAML descriptions + docstrings | Step descriptions, ingredient names, parameter docs |

  1. Consolidate — merge findings from all 4 agents, deduplicate by file:line, assign severity.
  1. Self-validation pass — for every CRITICAL or HIGH finding, re-read the cited file line to confirm the claim; downgrade or remove if not confirmed.
  1. Write report to {{AUTOSKILLIT_TEMP}}/audit-docs/docs_audit_{YYYY-MM-DD_HHMMSS}.md (relative to the current working directory) using the format below.
  1. Output summary — print finding counts by severity to terminal.

Report Format

# Documentation Audit Report — {YYYY-MM-DD HH:MM}

## Summary
| Severity | Count |
|----------|-------|
| CRITICAL | N     |
| HIGH     | N     |
| MEDIUM   | N     |
| LOW      | N     |

## Findings

### CRITICAL

#### [DOC-001] {Title}
- **File:** `path/to/doc.md:42`
- **Claim:** "..."
- **Actual:** "..."
- **Fix:** ...

...

## Coverage Gaps
{If any familiarization subagent failed, list affected subsystems here}

Exclusions

Do NOT flag:

  • Test files (tests/)
  • Generated files ({{AUTOSKILLIT_TEMP}}/, uv.lock, *.pyc)
  • Comment-only files or changelog entries
  • External tool output or CI logs
  • Doc-to-doc wording differences that don't contradict each other factually

Severity Guidelines

CRITICAL:

  • Orphaned references to deleted modules/tools
  • CLAUDE.md architecture tree listing a path that doesn't exist

HIGH:

  • Stale behavioral claim that would mislead an implementer
  • Count mismatch (e.g., CLAUDE.md says N skills, actual is M)

MEDIUM:

  • Path/name drift (hyphen vs underscore, module moved)
  • Missing doc for a significant new subsystem

LOW:

  • Minor wording drift
  • Docstring describes a parameter that was renamed

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.