expert-audit

Audits expert-team documentation assets for readability and format compliance from a zero-context user perspective.

2|Updated Jun 8, 2026
One-click install
npx skills add https://github.com/HACK-WU/skills --skill expert-audit-hack-wu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: expert-audit
Source: https://github.com/HACK-WU/skills/tree/main/skills/expert-audit
Command: npx skills add https://github.com/HACK-WU/skills --skill expert-audit-hack-wu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Expert documentation generated by AI can pass format checks while still being incomprehensible to users who lack code context. This Skill provides an independent, user-perspective acceptance review of expert-team assets, catching cases where the author understands the content but readers cannot. ## Core Features & Use Cases - Cold-Read Testing: Reads documentation without source code first, simulating a zero-context user, then verifies against source code to distinguish documentation problems from misreadings. - Dual-Track Review: Combines usability tests (cold-read questions, terminology self-sufficiency, example reproducibility, navigation reachability) with format compliance checks (R1-R7, CR1-CR9, INDEX rules). - Graded Reports with Auto-Fix: Outputs P0/P1/P2 prioritized findings, automatically repairs mechanical format issues, and routes content-level problems to expert-team or expert-lookup. - Use Case: After expert-team finishes generating documentation for a module, trigger this Skill to verify a new team member could understand and use the docs without reading the source code. ## Quick Start Ask the AI to audit the expert assets for a specific module by saying "审查专家资产" or "expert audit" followed by the expert name.

Frequently Asked Questions about expert-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit expert-team documentation for readability?

Trigger the audit by saying "审查专家资产" or "expert audit" with a target expert name. The Skill runs a cold-read test simulating a zero-context user, then verifies examples and symbols against source code, producing a P0/P1/P2 graded report.

What does the expert audit check in documentation assets?

It runs two tracks: usability tests covering cold-read comprehension, terminology self-sufficiency, example reproducibility, and navigation reachability, plus format compliance against R1-R7 implementation rules, CR1-CR9 contract rules, and INDEX record structure.

Can the audit automatically fix documentation problems?

It auto-fixes only mechanical format issues like missing file:// prefixes, broken anchors, and incomplete INDEX fields. Content-level problems such as wrong examples or missing explanations are reported with repair paths pointing to expert-team or expert-lookup.

Does expert-audit review the PROJECT.md shared asset?

No, PROJECT.md is excluded by default since expert-team maintains it. It is only reviewed when the user explicitly requests it, checking content completeness like service inventories, architecture diagrams, and data flow documentation.

When should I use expert-audit instead of auto-review?

Use expert-audit for acceptance review of already-saved expert documentation assets with domain-specific structure knowledge. auto-review is a general quality loop triggered by file writes and lacks expert asset format rules.