Content
38%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.
The body functions as an agent-activation persona file rather than a lean skill overview: it is heavily padded with persona ritual, duplicates command listings, and relies on dependency files that are not bundled. Actionability and workflow are moderate but weakened by absent bundle files and missing explicit validation gates.
Suggestions
Replace the embedded YAML persona/activation block with a concise overview, and move the CodeRabbit integration detail, command catalog, and dependency list into separate reference files that are actually bundled (references/).
Remove persona padding (zodiac, vocabulary, greeting/signature levels) and de-duplicate the command listings so each command appears once.
Add explicit validation checkpoints to the migration workflow (snapshot → dry-run → validate → apply → smoke-test) with failure/retry feedback loops so destructive operations are gated.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~500-line body is noticeably verbose: persona ritual ('zodiac: ♊ Gemini', Portuguese vocabulary lists, archetypal greeting/signature strings) is pure padding, command lists are duplicated across the YAML, Quick Commands, and Guide sections, and the CodeRabbit block restates the same severity/pattern lists multiple times. | 2 / 5 |
Actionability | Commands are named with arguments (e.g. '*apply-migration {path}', '*security-audit {scope}') and the CodeRabbit workflow gives an executable invocation, but most real guidance lives in dependency task files (db-apply-migration.md, security-audit.md) that are not bundled here, so the body itself is incomplete rather than copy-paste ready. | 3 / 5 |
Workflow Clarity | A 'Typical Workflow' sequence (Design → Bootstrap → Migrate → Secure → Optimize → Test) and 'Common Pitfalls' exist, but because database migrations are destructive/batch operations with only implicit validation gates, the missing explicit validate-before-proceed checkpoints cap this at 3. | 3 / 5 |
Progressive Disclosure | The body is a monolithic YAML config dump whose 'dependencies' section lists task/template/checklist/data filenames, but no bundle files exist under references/scripts/assets and the references are bare filenames in a YAML list rather than signaled, navigable links, so content that belongs in separate files is inlined and the pointers dangle. | 2 / 5 |
Total | 10 / 20 Passed |