Content
86%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-engineered advisory skill body: concrete, citation-safe guidance with clearly sequenced workflows and exemplary progressive disclosure. The residual slack is minor — a few terminology rows and partial duplication of the classification table that could live solely in the reference file.
Suggestions
Trim the Key Terminology table to NZ-specific entries only (drop generic rows like "Need-to-know" and common expansions such as BCP/DRP) to save tokens.
Replace the inline classification-level table with a two-row summary and defer the full table to references/classification-framework.md, which already contains it.
Add an explicit verification step to the gap-analysis workflow (e.g., 'confirm the table covers every applicable section for the stated classification before presenting') to close the workflow-clarity gap.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and table-driven with no prose padding and no explanation of generic concepts, but the Key Terminology table includes entries Claude already knows ("Need-to-know", BCP/DRP expansions) and the classification table partially duplicates references/classification-framework.md. It is above anchor 3 (only minor trim opportunities, not whole unnecessary sections) but below anchor 5 (not every token earns its place). | 4 / 5 |
Actionability | Guidance is fully concrete and executable for an advisory skill: exact output-table columns, a verified-CID citation rule with real examples (16.1.46.C.02) and an explicit never-invent-IDs fallback, named assurance artifacts (SOC 2 Type II, IRAP, ISO 27001), and stepwise pathways (7-step C&A, 5-step offshore/cloud) with specific control requirements. | 5 / 5 |
Workflow Clarity | The multi-step workflows are clearly sequenced with real gates ("formal risk acceptance by the Accreditation Authority / agency head before go-live", control validation "not documentation alone") and status definitions/checklists, matching anchor 4. It falls short of anchor 5 because there is no explicit validate-then-correct feedback loop on produced outputs (e.g., a completeness check that a gap table covers all applicable sections before presenting it). | 4 / 5 |
Progressive Disclosure | The body is a genuine overview with three real, one-level-deep reference files (verified: no nested references inside them), each signposted with its purpose plus a "When to load reference files" decision list — a textbook match to the top anchor. | 5 / 5 |
Total | 18 / 20 Passed |