Content
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is lean, well-organized, and makes command selection unambiguous, scoring well on conciseness and workflow clarity. Its weaknesses are actionability and progressive disclosure: usage examples reference a command name not tied to the actual scripts/icp.sh entry point, and the bundle file is never referenced or signaled.
Suggestions
Tie the usage examples to the real entry point, e.g. 'bash scripts/icp.sh checklist company', or document how 'icp-filing' is installed/aliased so commands are copy-paste executable.
Add a brief reference to the bundle, e.g. a line under the command table noting that all commands are implemented in scripts/icp.sh, so the command-to-script mapping is explicit.
Consider moving the per-province prefix logic and full FAQ detail to a references file and linking it one level deep from the body, keeping SKILL.md as a concise overview.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Lean ~48-line body with tight tables and lists, no padding or explanation of concepts Claude already knows; every section earns its place. Not 2 because there is no unnecessary explanation to tighten. | 3 / 3 |
Actionability | Provides a concrete command table and bash examples ('icp-filing checklist company', 'icp-filing footer "京ICP备2024001234号-1"'), but the usage invokes 'icp-filing' while the actual entry point is scripts/icp.sh with no invocation/install mapping, so commands are not copy-paste executable as written. Not 3 because key execution details are missing; not 1 because concrete commands and examples are present. | 2 / 3 |
Workflow Clarity | A simple command-reference skill under 50 lines with an unambiguous command table, usage examples, and trigger scenarios; per the simple-skills note, command selection is clear and well-organized. Not 2 because the single action (pick and run a command) is unambiguous, and no destructive/batch operations require validation checkpoints. | 3 / 3 |
Progressive Disclosure | Sections are well-organized, but the body never signals or references the bundle scripts/icp.sh, and the relationship between the 'icp-filing' commands and the actual script is unclear, with no one-level-deep reference. Not 3 because there are no well-signaled references to the bundle file; not 1 because the body itself is reasonably structured rather than a monolithic wall of text. | 2 / 3 |
Total | 10 / 12 Passed |