Content
88%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 strong, highly actionable skill body: executable test-first workflow with explicit validation gates and a checklist, and reference-manual density with essentially no wasted tokens. The main weakness is that the exhaustive definition-language and mapping schema material lives inline in SKILL.md rather than in a reference file, which affects both conciseness and progressive disclosure at the margin.
Suggestions
Move the exhaustive per-case option lists (the credential/fetch/mapping sums table and the per-data-source options like errors, fallbackOn, cache.ttl) into a references/definition-language.md file, keeping only the shape overview and one worked example in SKILL.md.
Move the full JSON mapping grammar section (quotas/notes/cost/whenEmpty path rules) to a references/json-mapping.md and keep a single compact example inline, shortening the body by ~80 lines.
Trim inline decoration detail such as the full look color/gradient arrays in the profile example to placeholder values, since the icon guide reference already covers visual specifics.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is extremely dense with no padding and no explanations of concepts Claude already knows ("A provider is data: one file... There is no registration step and no Swift line that names it"), consistently assuming competence. Not 5 because minor detail could be trimmed or moved (full look color/gradient arrays, exhaustive per-case option lists packed into table cells such as the credential/fetch/mapping sums). Not 3 because there is no unnecessary explanation anywhere. | 4 / 5 |
Actionability | Fully executable throughout: copy-paste-ready Swift golden-test code (StubbedProvider, #expect assertions), concrete JSON definition examples, exact file paths, and exact commands ("tuist test", "python3 scripts/gen-docs.py && python3 scripts/check-docs.py --strict", "npm test in website/"). Not 4 because there are no gaps in executable coverage of the common cases. | 5 / 5 |
Workflow Clarity | A six-step numbered TDD workflow with explicit red-green sequencing ("Golden tests first (red)... They fail first because <id>.json doesn't exist"), explicit validation checkpoints (ProviderFactory.builtIn validates, "tuist test green", docs check passes, npm test fails until counts match), a feedback loop in step 4 for when the language can't say something, and a final checklist. Not 4 because checkpoints are explicit and complete, not implicit. | 5 / 5 |
Progressive Disclosure | One real, well-signaled one-level-deep bundle reference (references/provider-icon-guide.md, verified present) plus clearly flagged repo docs ("Read first: TARGET_ARCHITECTURE.md, MODULAR_DESIGN.md, CANONICAL_MODEL.md") and good section structure. Not 5 because substantial reference material — the full definition-language spec, settings/accounts schemas, and the complete JSON mapping grammar — is inlined, making the body ~340 lines; not 3 because references are clearly signaled and content is well organized, not buried. | 4 / 5 |
Total | 18 / 20 Passed |