BC breakreach
Schedule, publish and manage social media posts with Breakreach on Instagram, TikTok, X, LinkedIn, YouTube, Facebook, Threads, Pinterest, Bluesky, Reddit, Telegram, Discord, Slack, Mastodon, WordPress, Ghost, Dev.to, Hashnode and Tumblr, through its MCP server, REST API or CLI. Use when the user wants to post or schedule something on social media, cross-post to several networks, pick the next free posting slot, upload media for a post, check what is scheduled or why a post failed, read or answer comments and DMs, set up an Instagram comment-to-DM, or look at post analytics.
Schedule, publish and manage social media posts with Breakreach on Instagram, TikTok, X, LinkedIn, YouTube, Facebook, Threads, Pinterest, Bluesky, Reddit…
As a process C 61/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice
How to improve
- 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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Exfiltration
net-credential-usereferences/rest-and-cli.md:41Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)curl -s https://api.breakreach.com/v1/media/upload -H "Authorization: Bearer $BREAKREACH_API_KEY" -F file=@photo.jpg
vendor-host -
low Exfiltration
net-credential-useSKILL.md:20Credential used in a network call (verify the destination is the intended service) (quoted — discussed, not commanded)3. **The REST API** with `curl` or the SDKs (`npm install breakreach`, `pip install breakreach`), with `Authorization: Bearer $BREAKREACH_API_KEY`. Same reference file.
quoted
Files scanned: 3. 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 61/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 22 mutating operations with no state check
- 60Tools and files. Uses tools (bash, web, python, node) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Steps. 26 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2316 tokens
- 100Progress reporting. Reports progress
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 580: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 26 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.