Content
57%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 concise and well-organized as an index, but its value collapses because every referenced sub-skill file is missing, leaving no executable guidance or reachable detail. The generic principles block adds little actionable content.
Suggestions
Provide the referenced bundle files (agent-dev.md, llm-security.md, rag-system.md, prompt-and-eval.md) so the routing matrix resolves to real content.
Replace or tighten the generic "AI 工程原则" platitudes with concrete, non-obvious guidance, or move them into the relevant sub-skill files.
Add a brief note on how routing resolves (e.g., 'read the matched sub-skill and follow its steps') so the workflow has a complete, verifiable endpoint.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean with no padding or over-explanation of concepts, but the "AI 工程原则" block states generic maxims Claude already knows (e.g., "人机协作,AI 增强而非替代"), so a few tokens could be trimmed, fitting the efficient-with-minor-over-explanation anchor. | 4 / 5 |
Actionability | The capability matrix gives a concrete need→sub-skill mapping, but there are no commands or code and the linked sub-skill files do not exist, leaving the guidance incomplete. | 3 / 5 |
Workflow Clarity | The single routing action is clear, but the routing targets (agent-dev.md, llm-security.md, rag-system.md, prompt-and-eval.md) are missing, so the workflow dead-ends rather than completing. | 3 / 5 |
Progressive Disclosure | Structure is a clean, well-signaled one-level-deep table of references, but the referenced files are absent from the bundle, so navigation is broken and the disclosure structure is non-functional. | 3 / 5 |
Total | 13 / 20 Passed |