ln-610-docs-auditor
Use when auditing project documentation through the evaluation platform with mandatory research, coordinated audit workers, and structured summaries.
- License 许可
- MIT
- 最近更新
- 2026-06-15
- Stars
- ★ 2
- Forks
- 1
01 前言 Front Matter
- name
- ln-610-docs-auditor
- license
- MIT
- description
- Use when auditing project documentation through the evaluation platform with mandatory research, coordinated audit workers, and structured summaries.
02 资源文件 7
- 参考文档references/audit_final_report_contract.md2.6 KB
- 参考文档references/epistemic_protocol.md3.4 KB
- 参考文档references/evaluation_coordinator_runtime_contract.md3.6 KB
- 参考文档references/evaluation_research_contract.md2.0 KB
- 参考文档references/evaluation_summary_contract.md1.8 KB
- 参考文档references/meta_analysis_protocol.md1.5 KB
- 参考文档references/research_tool_fallback.md1.2 KB
03 SKILL.md 正文
Paths: File paths (
references/,../ln-*) are relative to this skill directory.
Type: L2 Coordinator Category: 6XX Audit
Docs Auditor
Mandatory Read
MANDATORY READ: Load references/evaluation_coordinator_runtime_contract.md, references/evaluation_summary_contract.md, references/evaluation_research_contract.md
MANDATORY READ: Load references/audit_final_report_contract.md
MANDATORY READ: Load references/research_tool_fallback.md
Conditional read: load references/epistemic_protocol.md only when source confidence or claim uncertainty affects issue validation.
Purpose
- audit documentation structure, relevance, comments, and factual accuracy
- coordinate
ln-611,ln-612,ln-613,ln-614 - require research-backed standards before final scoring
Runtime Contract
Runtime family:
evaluation-runtime
Identifier:
docs-audit
Phase order:
PHASE_0_CONFIGPHASE_1_DISCOVERYPHASE_2_RESEARCHPHASE_3_DELEGATEPHASE_4_AGGREGATEPHASE_5_REPORTPHASE_6_SELF_CHECK
Worker Set
ln-611-docs-structure-auditorln-612-semantic-content-auditorln-613-code-comments-auditorln-614-docs-fact-checker
Worker Invocation (MANDATORY)
Host Skill Invocation: Skill(skill: "...", args: "...") is mandatory delegation.
- Claude: call the Skill tool exactly as shown.
- Codex: if no Skill tool exists, locate the named skill in available skills, read its
SKILL.md, treatargsas$ARGUMENTS, execute that skill workflow, then return here with its result/artifact. - Do not inline worker logic or mark the worker complete without executing the target skill.
Use the Skill tool for delegated workers. Do not inline worker logic inside the coordinator.
TodoWrite format (mandatory):
Resolve audit scope and build manifestLoad project documentation treeRun best-practice researchDelegate to domain audit workersAggregate worker findingsGenerate final audit report and remediation planVerify cleanup and self-check
Representative invocations:
Skill(skill: "ln-611-docs-structure-auditor", args: "{scope}")
Skill(skill: "ln-612-semantic-content-auditor", args: "{scope}")
Skill(skill: "ln-613-code-comments-auditor", args: "{scope}")
Skill(skill: "ln-614-docs-fact-checker", args: "{scope}")
Workflow
Phase 0: Config
Start evaluation-runtime with required_research=true.
Phase 1: Discovery
Discover documentation surfaces and scope.
Phase 2: Research
Mandatory research sources:
- official docs or standards
- MCP Ref
- Context7 when framework docs matter
- current web best-practice research
Phase 3: Delegate
Delegate specialized audit workers.
Child workers must use evaluation-worker-runtime and emit evaluation-compatible summaries recorded through evaluation-runtime.
Phase 4: Aggregate
Merge worker summaries into one documentation audit result. Read every worker report_path, normalize findings, deduplicate repeated issues, and validate each actionable problem against the research source order in references/evaluation_research_contract.md.
Phase 5: Report
Write .hex-skills/runtime-artifacts/runs/{run_id}/audit-report/ln-610--final-report.md per references/audit_final_report_contract.md. Include the remediation plan, source-backed validation for each confirmed issue, and cleanup note. Remove temporary worker markdown reports after consolidation. The evaluation-coordinator summary report_path must point to the final report only.
Phase 6: Self-Check
Required checks:
- [ ] mandatory research completed
- [ ] all worker summaries recorded
- [ ] aggregate summary exists
- [ ] final remediation report written
- [ ] temporary worker markdown reports removed
- [ ] cleanup verified
- [ ] coordinator summary recorded
Summary Contract
Write summary_kind=evaluation-coordinator.
Definition of Done
- [ ] Evaluation runtime started
- [ ] Research completed
- [ ] All documentation audit workers completed
- [ ] Aggregation completed
- [ ] Final report and remediation plan written
- [ ] Temporary worker markdown reports removed
- [ ]
evaluation-coordinatorsummary written - [ ] Runtime completed
Meta-Analysis
Optional reference: load references/meta_analysis_protocol.md only when the user asks for post-run meta-analysis or protocol-formatted run reflection.
When requested after the coordinator run, analyze the session per protocol section 7 and include the protocol-formatted output with the final documentation audit result.
References
- Workers:
../ln-611-docs-structure-auditor/SKILL.md,../ln-612-semantic-content-auditor/SKILL.md,../ln-613-code-comments-auditor/SKILL.md,../ln-614-docs-fact-checker/SKILL.md
Version: 5.0.0 Last Updated: 2026-03-01
04 同仓库更多 Skills
solana-dev
Use when user asks to "build a Solana dapp", "write an Anchor program", "create a token", "debug Solana errors", "set up wallet connection", "test my Solana program", "deploy to devnet", or "explain Solana concepts" (rent, accounts, PDAs, CPIs, etc.). End-to-end Solana development playbook covering wallet connection, Anchor/Pinocchio programs, Codama client generation, LiteSVM/Mollusk/Surfpool testing, and security checklists. Integrates with the Solana MCP server for live documentation search. Prefers framework-kit (@solana/client + @solana/react-hooks) for UI, wallet-standard-first connection (incl. ConnectorKit), @solana/kit for client/RPC code, and @solana/web3-compat for legacy boundaries.
generating-trading-signals
Generate trading signals using technical indicators (RSI, MACD, Bollinger Bands, etc.). Combines multiple indicators into composite signals with confidence scores. Use when analyzing assets for trading opportunities or checking technical indicators. Trigger with phrases like "get trading signals", "check indicators", "analyze for entry", "scan for opportunities", "generate buy/sell signals", or "technical analysis".
prediction-monitor
Prediction Monitor - Auto-activating skill for ML Deployment. Triggers on: prediction monitor, prediction monitor Part of the ML Deployment skill category.
strategy-advisor
High-level strategic thinking and business decision guidance for planning and direction-setting. Use when: making strategic decisions, evaluating business options, setting direction, analyzing trade-offs, or when user mentions strategy, business planning, competitive analysis, or long-term planning.
app-paywall-pilot
Design, audit, debug, and implement App Store-compliant mobile paywalls, subscription flows, pricing screens, trials, offers, feature gates, and subscription lifecycle UX. Use when the user asks to audit my paywall, fix App Store 3.1.2 rejection, improve trial-to-paid, choose plans/prices/trials, review RevenueCat/Adapty/Apphud/Superwall setup, calculate LTV/ROAS, or build paywall implementation.
figma
Use the Figma MCP server to fetch design context, screenshots, variables, and assets from Figma, and to translate Figma nodes into production code. Trigger when a task involves Figma URLs, node IDs, design-to-code implementation, or Figma MCP setup and troubleshooting.