Content
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, highly actionable skill with a clear multi-step workflow that takes the user from competitor identification through content creation to CMS publishing. Its main weakness is that it's monolithic — the three content templates and six CMS-specific push instructions inflate the document significantly and would benefit from being split into referenced files. The content is mostly efficient but includes some unnecessary explanatory sections.
Suggestions
Extract the three content templates (comparison page, alternatives page, category capture page) into a separate TEMPLATES.md file referenced from Step 5 to reduce the main skill's length.
Move the CMS-specific push instructions into a shared CMS_PUSH.md reference file, since this guidance appears to overlap with the 'prompt-gap-to-publish' skill already mentioned.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly long (~300 lines) but most content earns its place — the CMS table, bucket definitions, and content templates are all necessary. However, some sections are verbose (e.g., the 'What makes competitor content get cited' section explains things Claude likely already knows about SEO/citation principles), and the CMS discovery step repeats guidance from another skill. | 2 / 3 |
Actionability | Highly actionable throughout: specific API calls (get_ai_visibility_competitors, get_ai_visibility_prompts), concrete filtering criteria (competitor visibility >50%, Amplitude <30%), detailed content templates with exact H1 formats, section structures, and word counts, plus CMS-specific push commands with exact field mappings and status settings. | 3 / 3 |
Workflow Clarity | The 7-step workflow (Steps 0-6) is clearly sequenced with logical dependencies. Each step has explicit outputs and decision points (e.g., 'Which bucket do you want to attack first?'). Step 4's diagnosis before writing serves as a validation checkpoint, and Step 6 includes a fallback (Markdown copy) and confirmation message. The workflow handles branching well across three content buckets. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and tables, but it's entirely monolithic — all content templates (Bucket 1, 2, 3) and all CMS instructions are inline rather than split into referenced files. The comparison page template, alternatives page template, and CMS push instructions could each be separate files. There's a reference to 'prompt-gap-to-publish' but no other file references. | 2 / 3 |
Total | 10 / 12 Passed |