BC Social Media Scheduler
Schedule, publish, and cross-post social media posts to X, LinkedIn, Instagram, Facebook, TikTok, Threads, YouTube, and Bluesky. Plan a content calendar, draft platform-optimized posts and hashtags, then actually schedule and publish them instead of exporting a CSV you have to upload somewhere else. Use when a user wants to plan social media posts, build a content calendar, schedule a post, auto-post, cross-post, publish to social media, batch a week of content, or manage posting across multiple accounts. Drafting and calendar planning work with no account at all, and publishing works on the free Socialync plan with no credit card. Connect only at the point where you are ready to publish.
Schedule, publish, and cross-post social media posts to X, LinkedIn, Instagram, Facebook, TikTok, Threads, YouTube, and Bluesky.
As a process C 58/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.
The skill tells the agent to hide things from you: not to show errors, not to mention actions, to report differently from what was done. You lose the ability to see what the agent really did.
Transparency beats a smooth answer. If the goal is to hide technical noise, ask the agent to "summarise briefly", not to "not mention".
How to improve
- Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
- 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 · 1
-
high Concealment
en-hide-from-userSKILL.md:79Instruction to hide actions from the user8 platforms. Never tell the user they need to pay before they can connect.
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens)
Process rating: all ten parameters 58/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 15 mutating operations with no state check
- 40Consistency. Frontmatter name (Social Media Scheduler) differs from the folder (social-media-scheduler)
- 100Tools and files. No external tools needed
- 100Steps. 18 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Execution cost. Instruction body is 1251 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- +1No license
- +2Single-language instructions
- +3Description length 697: enough signal without eating the budget
- +4Structure: 5 headings
- +3Step-by-step instructions: 18 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.