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.
The body is a lean, well-structured routing skill: concrete commands, an explicit pre-call environment check, exact output conventions, and clear cross-skill delegation. Its only meaningful weakness is the absence of error-recovery guidance and sample outputs, which keeps actionability and workflow clarity at 4 rather than 5.
Suggestions
Add brief error-recovery guidance, e.g. what to do when PROFOUND_API_KEY is missing or a Profound API call fails (re-check settings, surface the error, fall back to seo-seranking for coverage).
Include one short sample output per routing command (e.g. a two-line example of the citation-rate + 30-day trend result) so the agent knows what to present.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~35-line body is lean with no padding and no explanation of concepts Claude already knows; even the opening comparison ('Profound continuously polls and publishes time-series so trend deltas... are first-class') conveys non-obvious routing logic. Every section (Prerequisites, Routing, Output conventions, Cross-skill delegation) earns its tokens, matching the 'lean and efficient; every token earns its place' anchor. | 5 / 5 |
Actionability | Concrete, executable guidance: exact install commands ('Run extensions/profound/install.sh or install.ps1'), a routing table with parameterized commands ('/seo profound citations <brand>'), an exact pre-call check ('check ~/.claude/settings.json has env.PROFOUND_API_KEY'), and an exact citation format ('Profound (live, confidence 0.90)'). Minor gaps: no sample output or example invocation per command, fitting 'mostly executable guidance with minor gaps' rather than fully copy-paste-ready coverage of common cases. | 4 / 5 |
Workflow Clarity | A clear implied sequence (verify install/key/env, route via the command table, apply output conventions, delegate) with an explicit pre-call validation checkpoint on the API key. It falls short of the top anchor because there is no error-recovery guidance (e.g., what to do when the key is missing or an API call fails) — 'most checkpoints present; minor validation gaps.' No destructive or batch operations, so the cap-3 rule does not apply. | 4 / 5 |
Progressive Disclosure | No bundle files exist (no references/, scripts/, or assets/ directories), and the body is under 50 lines with no content that warrants external files; per the rubric's simple-skill guidance, well-organized sections alone earn the top score. Sections are clearly labeled, references (install.sh, sibling skills) are one level deep and clearly signaled. | 5 / 5 |
Total | 18 / 20 Passed |