Content
56%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-sequenced instruction set undermined by heavy redundancy — the MCP/tdx fallback logic is repeated five times — and by a monolithic structure that inlines a 240-line template with no external references. Consolidating the duplicated access instructions and splitting the template into a reference file would lift both weak dimensions.
Suggestions
State the TD-MCP-preferred / tdx-fallback logic once (e.g., in a short 'Database Access' section) and have Phases 1–2 reference it instead of repeating the if/else branches verbatim.
Move the ~240-line documentation template to references/template.md and link to it, keeping SKILL.md as an overview of the three phases.
Add one concrete TD MCP tool invocation example and a sample SQL query so the preferred access path is as executable as the tdx path.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The TD-MCP-vs-tdx fallback is restated roughly five times (Methods 1/2, 'Before proceeding', Phases 1 and 2, Key Principles, Summary, and 'Fallback Strategy'), and the 'When to Use' section duplicates the frontmatter description. This repetition is pervasive padding, though the file avoids explaining concepts Claude already knows. | 2 / 5 |
Actionability | Provides concrete tdx commands ('tdx use database cdp_audience_<id>', 'tdx describe <table>'), explicit SQL ('SHOW TABLES IN', 'DESCRIBE'), and a detailed template with conditional generation rules. Minor gaps: the preferred MCP path is vague ('mcp__treasuredata__* tools' with no actual tool calls) and 'Working SQL examples' is mandated without any example shown. | 4 / 5 |
Workflow Clarity | Phases 1–3 (discovery → schema extraction → generation) are clearly sequenced with checkpoints ('Confirm master segment database exists', 'STOP if cannot access database'). No error-recovery guidance exists for failure cases like an empty schema or ambiguous master table, keeping it below a 5; the operations are read-only queries, so the destructive/batch cap does not apply. | 4 / 5 |
Progressive Disclosure | No bundle files exist and the ~240-line documentation template is inlined directly in SKILL.md where it clearly belongs in a references/ file. Real section headers and a navigable structure keep this above the minimal-structure anchor. | 3 / 5 |
Total | 13 / 20 Passed |