CB posthero
Schedule and publish social media posts across LinkedIn, Twitter/X, Instagram, Facebook, YouTube, TikTok, Threads, and Bluesky using the PostHero API. Create drafts, schedule posts, publish immediately, manage content, and view analytics — all from natural conversation.
As a process B 65/100 · Nearly there — weak spots: result and completion, inputs and preconditions, running it twice
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".
If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 5
✓ No critical or high findings
Medium and low: 5
-
medium Exfiltration
net-credential-useSKILL.md:92Credential used in a network call (verify the destination is the intended service)curl -H "Authorization: Bearer $POSTHERO_API_KEY" \
-
medium Exfiltration
net-credential-useSKILL.md:286Credential used in a network call (verify the destination is the intended service)curl -H "Authorization: Bearer $POSTHERO_API_KEY" \
-
medium Exfiltration
net-credential-useSKILL.md:341Credential used in a network call (verify the destination is the intended service)curl -H "Authorization: Bearer $POSTHERO_API_KEY" \
-
medium Exfiltration
net-credential-useSKILL.md:448Credential used in a network call (verify the destination is the intended service)curl -H "Authorization: Bearer $POSTHERO_API_KEY" \
-
medium Exfiltration
net-credential-useSKILL.md:468Credential used in a network call (verify the destination is the intended service)curl -H "Authorization: Bearer $POSTHERO_API_KEY" \
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "title" - note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "keywords"
Process rating: all ten parameters 65/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 33 mutating operations with no state check
- 70When it triggers. States when to use, but not when not to
- 70Execution cost. Instruction body is 4163 tokens
- 100Tools and files. No external tools needed
- 100Steps. 30 steps
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
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)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +3Description length 270: enough signal without eating the budget
- +4Structure: 22 headings
- +3Step-by-step instructions: 30 items
- +4Has examples (24 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.