AC text-post-and-microblog
The master craft of the standalone text post / microblog (LinkedIn, X/Twitter, Threads, Bluesky, Facebook text posts). Use when someone wants to write a text post, a LinkedIn post, a short written update, a microblog, or fix a post that flopped / reads as a wall of text / has a weak opening line. A text post has nowhere to hide -- the words are everything, and the first ~140-210 characters (the 'see more' fold) are most of the job. Uses the LINES framework. Reads brand-profile + voice-builder + hook-writer first; pulls the 'what' from the content-angle skills. The agent writes the post; the human approves; WoopSocial publishes to supported platforms, routing specifics to linkedin-post-writer / threads-post / thread-writer. NEVER fabricates a stat/story/metric or uses engagement-bait; avoids AI-slop over-formatting. No native multi-post threads; Reddit/Mastodon are advisory-only. Distinct from caption-writer, thread-writer, and the content-angle skills (WHAT vs this HOW).
The master craft of the standalone text post / microblog (LinkedIn, X/Twitter, Threads, Bluesky, Facebook text posts).
As a process C 62/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- 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
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 62/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 4 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 55Failures and branches. 1 branches
- 100Tools and files. No external tools needed
- 100Steps. 10 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1703 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low No test case covers injection arriving through data
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)
- +3Description length 985: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +4Structure: 9 headings
- +3Step-by-step instructions: 10 items
- +4Reference files are cited in the instructions (4 of 4)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.