Content
63%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 is highly actionable with concrete commands, configs, and a clear workflow diagram, but it is verbose for a SKILL.md — duplicating the command list and carrying changelog/marketing/link padding — and keeps all reference material inlined rather than splitting it into separate files.
Suggestions
Remove the duplicate command listing: keep only the 命令 table and drop the redundant bash block in quick-start step 3 (or vice versa).
Move the two version-changelog tables, the file-structure tree, the config-key reference, and the scope-decision guide into a separate references/ file (e.g. REFERENCE.md) linked from a short overview, cutting the inlined bulk.
Trim the marketing intro, the "相关链接" external-link section, and the "为什么用钩子而非技能" rationale to the essential operational points.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Most content is operationally useful, but the 355-line body includes clear padding: the command set is listed twice (quick-start bash block and the 命令 table), two version-changelog tables (v1→v2, v2.0→v2.1), a marketing-style intro, and an external-links section that could be trimmed. | 3 / 5 |
Actionability | It provides concrete, copy-pasteable guidance — real CLI calls ("python3 instinct-cli.py promote prefer-explicit-errors", "--dry-run"), slash commands, JSON hook/config blocks, a YAML instinct example, and an explicit directory tree — with only minor gaps in specifying command output/behavior. | 4 / 5 |
Workflow Clarity | The pipeline is laid out clearly via the ASCII workflow diagram (session → hook capture → observer → pattern detection → create/update → /evolve + /promote) and a numbered quick-start, and promotion offers a --dry-run checkpoint; minor validation gaps remain (e.g. no explicit feedback loop for /evolve). | 4 / 5 |
Progressive Disclosure | Section headers are well-organized, but at 355 lines everything is inlined into SKILL.md with no one-level-deep references to separate files; material like the file-structure tree, config reference, and scope-decision guide are candidates for split reference docs, and no bundle reference files are provided. | 3 / 5 |
Total | 14 / 20 Passed |