CC community-post-generator
Writes a post for one specific community (a subreddit, Show HN, Product Hunt, Indie Hackers, dev.to, Discord, Slack, Telegram) after checking its rules, with a Go/No-Go first. Use whenever someone wants to post, launch, or share in one, even when they pasted the rules or the post looks obvious. LinkedIn, X, or Facebook: that's content-repurposer.
Writes a post for one specific community (a subreddit, Show HN, Product Hunt, Indie Hackers, dev.to, Discord, Slack, Telegram) after checking its rules, with…
As a process C 62/100 · Has gaps — References files that are not bundled: references/brand-voice.md
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 12679 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: references/brand-voice.md
Process rating: all ten parameters 62/100
- 0Tools and files. 1 referenced file(s) missing: references/brand-voice.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 40Execution cost. Instruction body is 12679 tokens: crowds the task out of the window
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 83 steps
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 7 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (6 tags): a typed call is more reliable
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +3Description length 348: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 83 items
- +3Output format is stated explicitly
- +4Has examples (0 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.