Content
68%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 well-structured overview skill: concise, rule-dense, and easy to navigate, with concrete commands for the most common operations. Its weaknesses are a core workflow that is implied rather than sequenced, and a reference layer that is structurally excellent but points at files missing from the bundle.
Suggestions
Assemble the core lifecycle (git clone -> `apm install` -> edit apm.yml -> commit apm.yml + apm.lock.yaml + .apm/) into one ordered, numbered workflow with a verification step (e.g., check `apm install` output or run `apm audit`) before the Key rules section.
Ship the eight referenced files (installation.md, workflow.md, commands.md, dependencies.md, authentication.md, governance.md, package-authoring.md, troubleshooting.md) in the bundle — ideally under references/ — so the links resolve; currently none exist next to SKILL.md.
Trim the "When to activate" bullet list, which duplicates the frontmatter description's triggers, to reclaim tokens in the always-loaded body.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and rule-focused with a brief, informative intro; every section carries operational content. Not 5 because the "When to activate" section largely restates the frontmatter description's trigger list, which could be trimmed, and the intro slightly overlaps what the description already establishes. | 4 / 5 |
Actionability | Concrete, executable directives throughout: "after `git clone`, run `apm install`", "`apm install --update` refreshes to latest refs", "use tags (`#v1.0.0`) in production", and an explicit commit/ignore file list. For an instruction-only skill this is actionable; not 5 because most operations (compile, audit, auth setup) are delegated to references without a single inline example. | 4 / 5 |
Workflow Clarity | The pieces of the core workflow (clone -> `apm install` -> edit apm.yml -> commit apm.yml + apm.lock.yaml) are present but scattered across "Key rules" rather than assembled into an ordered sequence, and no validation checkpoints are given. Fits anchor 3 (steps present but sequence/checkpoints implicit); not 2 because the individual directives are concrete and correctly gated (e.g., "after `git clone`"). | 3 / 5 |
Progressive Disclosure | A clean overview with well-labeled, one-level-deep references, each with a short descriptor ("-- install and update APM", "-- full CLI command reference"). Not 5 because all eight linked files (installation.md, workflow.md, commands.md, dependencies.md, authentication.md, governance.md, package-authoring.md, troubleshooting.md) are absent from the bundle — no references/ directory exists — so the links cannot be verified as real targets. | 4 / 5 |
Total | 15 / 20 Passed |