Content
85%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 skill body with strong validation checkpoints, held back only by repeated DynamicSourceSetup guidance and a lack of progressive disclosure — everything is inlined in one large file with no reference bundle.
Suggestions
Split the source catalog table and the per-repo checklists (posthog/code items 1-9, posthog/posthog items 1-7) into separate reference files under references/ and link to them from SKILL.md to enable progressive disclosure.
Consolidate the 'route the DataSourceSetup case to DynamicSourceSetup, no bespoke form' guidance, which is currently repeated in 'The setup form', 'posthog/code checklist > Setup-form specifics', and 'OAuth plumbing' sections, into a single authoritative statement.
Move the created_via attribution table into its own reference file, since it is reference material rather than steps the agent performs.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with high-signal specifics (paths, enums, commands) and assumes Claude's competence without explaining basic concepts, but the 'route to DynamicSourceSetup, no bespoke form' guidance is restated across ~4 sections and could be trimmed. Not a 5 due to that repetition; not a 3 because almost every token is actionable rather than padded. | 4 / 5 |
Actionability | Provides copy-paste-ready commands ('python manage.py makemigrations signals', the worktree block), exact file paths, enum/symbol names, a worked payload-key catalog, and concrete 'copy github_issues.py and adapt' guidance covering common cases. | 5 / 5 |
Workflow Clarity | Clear sequencing with explicit deploy ordering ('do not skip'), numbered per-repo checklists, dedicated 'Verify' sections with validation commands, and feedback loops (migration-collision batching, 'can only be confirmed by running a sync') for risky batch/migration operations. | 5 / 5 |
Progressive Disclosure | Section headers and tables give good structure, but the ~250-line body is monolithic with no bundle/reference files at all, despite clearly separable chunks (source catalog, per-repo checklists, created_via attribution) that belong in one-level-deep references. Not a 4 because no references exist; not a 2 because the in-file organization is solid. | 3 / 5 |
Total | 17 / 20 Passed |