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 highly actionable, well-structured skill body with concrete commands, a request-to-command map, and real validation checkpoints for the destructive publish operation. The main weakness is redundancy — the Tips section and parts of the Workflow repeat content from dedicated sections — plus an unreferenced bundle file.
Suggestions
Remove or de-duplicate the "Tips" section: character limits, platform names, LinkedIn mentions, and scratchpad guidance are already covered in their dedicated sections above.
Reference references/posting-workflow.md from the body (e.g., in the Workflow or Common Actions section) so the bundle file is discoverable rather than orphaned.
Consolidate the social-set resolution logic that currently appears in both "Social Sets" and "Workflow" into one place, and tighten the verbose "DO NOT" list under API-key handling.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient and actionable, but the "Tips" section duplicates content already covered in dedicated sections (character limits, platform names, LinkedIn mentions, scratchpad), the "Workflow" repeats the social-set resolution logic from "Social Sets", and the API-key "DO NOT" list is padded. This is more than minor trimming, so it sits below 4. | 3 / 5 |
Actionability | Fully executable throughout: copy-paste bash commands with specific flags, a "Common Actions" table mapping user requests to exact commands, and concrete worked examples (e.g., multi-platform draft→update flow, LinkedIn mention resolver) covering the common cases. | 5 / 5 |
Workflow Clarity | Clear numbered workflow with real validation checkpoints — check default social set before proceeding, stop-and-wait on API-key errors (a genuine feedback loop), and "always confirm before publishing" for the irreversible publish action. Not a 5 because the multi-platform update flow lacks an explicit verify step and some checkpoints are implied rather than checked. | 4 / 5 |
Progressive Disclosure | Well-organized sections with a clear "Detailed references" pointer to one-level-deep files (commands.md, examples.md), both verified to exist. Held below 5 because references/posting-workflow.md is a bundle file that is never signaled from the body, and several inlined sections (LinkedIn Mentions, Draft Scratchpad, Tips) could live in references. | 4 / 5 |
Total | 16 / 20 Passed |