Content
86%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.
An exemplary single-file automation skill: copy-paste executable commands, explicit defaults and failure paths, and tight structure. The only gaps are minor — a small duplication of the read-only constraint and no verification step between writing the digest and opening the PR.
Suggestions
Add a verification checkpoint after the write/push, e.g. confirm the digest rendered N items (or is non-empty) before opening the PR, and check that git push succeeded before running gh pr create.
Trim the duplicated read-only/unattended constraint — state it once (e.g. keep the Notes invariant) rather than in both the intro and Notes.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is very lean — "Read posthog, write a doc, open a PR. Nothing else." — with no explanation of concepts Claude already knows and only non-obvious operational detail. Minor trims exist: the read-only/unattended constraint is stated both at the top ("Never prompt for confirmation and never write to posthog") and again in Notes ("Read-only. The only write is the digest file in the PR"), fitting anchor 4 rather than 5. | 4 / 5 |
Actionability | Fully executable: an exact bash block for branch/commit/push/gh pr create, explicit input defaults ({{DIGEST_FILE}} -> docs/posthog-digest.md, {{LIMIT}} -> 20), a precise digest format spec, and concrete error paths. Matches anchor 5 (copy-paste ready commands covering the common cases). | 5 / 5 |
Workflow Clarity | A clear 1-2-3 sequence with explicit precondition checkpoints (list MCP tools first, check credentials, "stop and report which one", "An empty result is a valid outcome"). It lacks verification after the digest write and after git push/PR creation, matching anchor 4 ("most checkpoints present; minor validation gaps") rather than 5. The destructive/batch cap does not apply since the operation is read-only toward posthog and the single file write is an explicitly idempotent generated artifact. | 4 / 5 |
Progressive Disclosure | No bundle files exist and none are needed — the ~74-line body is operational detail that splitting would hurt. Sections (Inputs, Procedure, Notes) are well organized and easy to navigate, which per the simple-skill guidance merits a 5; there are no inlined blocks that belong in separate files. | 5 / 5 |
Total | 18 / 20 Passed |