Content
75%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 a compact, well-sectioned router for six subcommands with concrete defaults, explicit error-handling and output rules, and unusually strong security guidance (untrusted-data treatment and read-only credential scoping). It falls short of top marks mainly on actionability (no example invocations or sample HogQL) and mild redundancy in the Security section.
Suggestions
Add one example invocation with options (e.g., `/seo posthog organic --days 90`) and a sample HogQL query or MCP exec call so the guidance is copy-paste ready.
Dedupe the Security section: state the read-only rule and the no-credential rule once each instead of twice.
State an explicit sequence, e.g., "Run `/seo posthog check` before any data command", to add a validation checkpoint to the workflow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is tight and operational (routing table, defaults, error handling, output format) with no explanations of concepts Claude already knows. Minor redundancy could be trimmed: "this extension ships no script and stores no token" (intro) repeats "This extension stores no credential" (Security), and the read-only rule appears in both the second and third Security bullets. | 4 / 5 |
Actionability | Concrete guidance dominates: six named commands in the routing table, "Options: days (default 28) and limit (default 50)", and the delegation mechanism "runs HogQL queries through the MCP `exec` tool (`call execute-sql`)". It stops short of anchor 5 because there is no example invocation with options and no sample HogQL query or MCP call to copy. | 4 / 5 |
Workflow Clarity | Sections sequence logically from Prerequisites to Routing to Error Handling, and validation is present: "/seo posthog check" verifies connectivity, and empty results trigger a verification step ("verify project, window, and that $referring_domain is captured before reporting zero organic traffic"). It misses anchor 5 because no explicit end-to-end ordering (e.g., run check before data commands) or re-check loop is stated. | 4 / 5 |
Progressive Disclosure | Good structure with clear, flat section headers and no nested references; no bundle files exist, so nothing is over-inlined. The minor gap is that referenced paths such as "extensions/posthog/install.sh" and "extensions/posthog/docs/POSTHOG-SETUP.md" point outside the skill bundle and cannot be resolved from the skill itself. | 4 / 5 |
Total | 16 / 20 Passed |