Content
63%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 well-organized, reference-rich body with genuinely actionable numbers and a concrete output format, weakened by redundancy (overlapping length tables, repeated mobile stat), a knowledge-restating platform-comparison table, and ~40 lines of profile-SEO/GEO material inlined in SKILL.md that should be a separate reference file. As an instruction-only skill it needs no code, and its guidance is executable as written.
Suggestions
Delete or compress the "Platform Positioning" comparison table — that LinkedIn is professional and TikTok is entertainment is knowledge Claude already has; keep only the "Prioritize LinkedIn when" line.
Merge "Character Limits" and "Optimal Length by Content Type" into one table (they repeat the same ranges), and state the 88% mobile-browsing stat once instead of in both Image Specs and Best Practices.
Move the "Off-Site Search Visibility (SEO & GEO)" and "Profile Modules" sections into a separate reference file (e.g. references/seo-geo.md) linked from the body, keeping SKILL.md focused on post copy creation and output format.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Tables keep most sections dense, but the "LinkedIn vs Meta / X / TikTok" positioning table restates common knowledge (LinkedIn is professional and real-name; TikTok is entertainment), the "Character Limits" and "Optimal Length" tables repeat the same 100–200 and 1,300–1,600 ranges, the 88%-mobile stat appears twice, and the ~40-line Off-Site SEO/GEO section drifts beyond post-copy creation. Mostly efficient with clear trimmable padding, matching anchor 3; not 2 because the bulk is genuinely useful reference data, not filler. | 3 / 5 |
Actionability | Concrete, usable numbers throughout — 3,000-char limit, 210–235 first-line window, per-type length ranges, 1200×627 / 1200×1200 image dims, ≤10MB files, up to 20 carousel images — plus a numbered 5-item Output Format and a form-note convention. Per the instruction-skill note, absence of code is not penalized; it falls short of 5 only because there is no worked example post and some guidance stays soft ("a few, relevant" hashtags, "Often strong for reach"). | 4 / 5 |
Workflow Clarity | The Output Format section gives a clear numbered sequence of what to produce (first line ≤210 chars → full post with count → hashtags → image specs → form note), and post-type selection is tabulated. Checkpoints as such aren't needed since nothing is destructive or batch, so no cap applies; it is not 5 because the path from "user request" to "finished post" (pick type → match length → write hook → assemble per format) must be assembled by the reader rather than stated. | 4 / 5 |
Progressive Disclosure | No bundle files exist (references/, scripts/, assets/ all absent), and the ~180-line body inlines a ~40-line SEO/GEO-plus-profile-modules block that is tangential to post copy creation and belongs in a separate reference file. Section headers are clear and cross-skill references are well signaled, which lifts it above anchor 2's "minimal structure," but the single-file scope creep matches anchor 3's "content that should be separate is inline." | 3 / 5 |
Total | 14 / 20 Passed |