Content
75%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 highly actionable, well-structured instruction skill: concrete artifact templates for all four output formats, a clear five-step dialogue workflow with safety checkpoints, and honest limitations. The main cost is duplication-driven verbosity, with the example CSV row and Notion mapping guidance each stated twice, and the long inline artifact templates could be externalized.
Suggestions
Remove the duplication between the CSV example block, the Field Reference 'CSV example' column, and the Notion mapping 'Set after import' column - state each fact once in the Field Reference.
Move the full SQL DDL and JSON Schema examples into a reference file (or generate them from the Field Reference) to shrink the always-loaded body.
Add an explicit post-build validation step (e.g., check the emitted CSV/JSON against the field list before delivering) to close the workflow-clarity gap.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body avoids explaining concepts Claude already knows and its prose is tight, but the example CSV row is fully duplicated in the Field Reference table, the Notion mapping table's 'Set after import' column repeats the Field Reference's Notion column, and sections like Reusable Prompt add length with limited payoff. | 3 / 5 |
Actionability | Guidance is fully concrete and copy-paste ready: exact CSV header and example row, complete PostgreSQL DDL, complete JSON Schema, a per-field Notion property mapping, an internal context YAML shape, and a worked example dialogue covering the common cases. | 5 / 5 |
Workflow Clarity | Steps 1-5 are clearly sequenced with intent routing, one-question-at-a-time rules, an internal context shape, and several validation checkpoints ("verify actual tool access and the target before writing", post-import property mapping, reporting validation failures), but there is no explicit validate-the-emitted-artifact feedback loop. | 4 / 5 |
Progressive Disclosure | The skill is a single well-sectioned file with no bundle files and clearly signaled one-level-deep references to sibling skills (@notion-manual-import, @people-directory); however, the inline four-artifact templates and ~320-line body are content that could arguably be split into reference files. | 4 / 5 |
Total | 16 / 20 Passed |