Content
92%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, tight skill body: platform-specific gotchas, an executable migration command, and an explicit validate-before-promote workflow with rollback guidance. The only gap is that the migration-script authoring section and validation steps could be slightly more concrete with a worked example and literal commands.
Suggestions
Add a minimal complete migration.js example (createContentType with one validated field) alongside the method-name list, since writing migrations is the skill's primary task.
Give a concrete sample query or CLI command for validation step 1 (e.g., fetching entries of the migrated content type and asserting a required field) to make the checkpoint literal rather than descriptive.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~30-line body is dense with Contentful-specific knowledge Claude would not have ("Rollback is *recreate*, not undo", "REST needs `include`", "Use `sys.publishedAt` as the cache-invalidation key", ".validations([{ unique: true }])") and contains no padding or explanations of general concepts. Every line earns its place, matching the lean 5 anchor. | 5 / 5 |
Actionability | Provides a copy-paste-ready migration command with exact flags ("contentful space migration --space-id <SPACE_ID> --environment-id sandbox migration.js") and executable snippets for `linkContentType` and uniqueness validations. It stops short of the 5 anchor because the migration script section only names methods ("use `createContentType` / `createField` / `displayField`") without a worked example, and the post-migration validation steps are directives ("Query a representative sample... exit non-zero on a miss") rather than literal commands. | 4 / 5 |
Workflow Clarity | The destructive migration workflow is explicitly sequenced ("Create a sandbox environment, migrate there, validate, then promote or re-run against `master` in a maintenance window") with a numbered validation checklist (sample entries with exit-non-zero failure signal, site build, integration tests) and an error-recovery feedback loop ("delete the sandbox, re-clone from `master`, re-run a corrected migration"). This clears the destructive-operation validation cap and matches the 5 anchor's explicit validation plus rollback loops. | 5 / 5 |
Progressive Disclosure | The body is under 50 lines with well-organized sections (Gotchas, Migration command, Post-migration validation) and no bundle files to reference, so the simple-skill exception applies and organization alone supports a 5. External pointers (".opencastle/stack/cms-config.md", the Contentful docs URL) are appropriate one-level references. | 5 / 5 |
Total | 19 / 20 Passed |