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.
A strong, highly actionable body: concrete templates, timing blueprints, and tool names throughout, with well-signaled one-level-deep references and approval/feedback checkpoints in the publishing workflow. The main weaknesses are token efficiency — several sections restate generic social-media knowledge Claude already has and the question lists are duplicated — and a couple of reference-hygiene gaps (one broken nested link, one second-level link).
Suggestions
Trim or move to a reference file the sections that restate knowledge Claude already has (Analytics & Optimization metrics, Quality Comments, Building Relationships, Content Ideas by Situation), keeping only the skill's opinionated specifics inline.
Remove the 'Task-Specific Questions' section or fold it into 'Before Creating Content' — the two question lists substantially overlap.
Fix the broken nested reference: platforms.md points to references/telegram-channels.md, which is not present in the bundle.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The high-value sections are dense and non-obvious (hook formulas, the 'No AI Tells' blacklist, content-atom tables, timestamped video structures), but several sections restate knowledge Claude already has: "Metrics That Matter: Impressions, Reach, Follower growth rate", "Quality Comments: Add new insight, not just 'Great post!'", and "Content Ideas by Situation: Document your journey". The 'Task-Specific Questions' section also duplicates the 'Before Creating Content' question list, so the body could be tightened — matching 'mostly efficient but includes some unnecessary explanation'. | 3 / 5 |
Actionability | For an instruction-only skill, the guidance is copy-paste ready: fill-in-the-blank hook templates ("I was wrong about [common belief]."), timestamped video blueprints ("[0-3s] Hook: State the problem... [25-30s] CTA"), concrete caption specs ("MAX 2 lines... 3-5 words per line"), a literal weekly calendar table, and named tools ("Whisper, Descript, or your podcast host's transcription"). Specific examples cover the common cases (posts, threads, carousels, short-form video, repurposing), which is the anchor-5 standard; the few advisory spots ('Test new hooks') are minor relative to the whole. | 5 / 5 |
Workflow Clarity | Multi-step processes are clearly sequenced (6-step podcast workflow, 6-step repurposing workflow, batching checklist) and the publishing workflow has explicit validation checkpoints and a feedback loop: "Create posts as drafts first — the user approves before anything is scheduled. Never auto-publish without an explicit go-ahead" and "Close the loop... feed real engagement data back". It is not a 5 because several other workflows (repurposing, engagement routine) have implicit rather than explicit checkpoints, and steps like "Analyze patterns" are loosely defined — matching 'clear sequence with most checkpoints present; minor validation gaps'. | 4 / 5 |
Progressive Disclosure | The body is well split: eight focused reference files, each signaled with purpose and usage conditions ("For X (Twitter) ranking mechanics... Use it whenever the task involves posting on X"), and all eight referenced paths exist in the bundle. It is not a 5 because of minor organization gaps: platforms.md links to references/telegram-channels.md which does not exist in the bundle, listening.md nests a second-level link to listening-sources-template.md, and some inline sections (short-form video, ~80 lines) arguably belong in references. | 4 / 5 |
Total | 16 / 20 Passed |