BC BlogBurst - Virtual CMO Agent
Your AI Chief Marketing Officer. Autonomous agent that runs your entire marketing — auto-posts to Twitter/X, Bluesky, Telegram, Discord, auto-engages with your audience (replies, likes, follows), runs SEO/GEO audits, tracks competitors, scans communities for opportunities, learns what works, and continuously optimizes. 50+ countries, 1000+ posts published. Free tier available.
Your AI Chief Marketing Officer.
As a process C 50/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
The same skill appears in 1 more place: openclaw-master-skills
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 · 4
✓ No critical or high findings
Medium and low: 4
-
low Dangerous commands
cmd-shell-rcSKILL.md:28Writes to a shell startup file (documentation of a security skill)echo 'export BLOGBURST_API_KEY="your-key"' >> ~/.zshrc && source ~/.zshrc
security skill
A further 3 matches are quotations in this security skill's documentation and are not counted as findings.
Files scanned: 3. 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) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 50/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 10 mutating operations with no state check
- 40Consistency. Frontmatter name (BlogBurst - Virtual CMO Agent) differs from the folder (blogburst-3-1-2)
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 60Failures and branches. 2 branches
- 70Execution cost. Instruction body is 4487 tokens
- 100Steps. 57 steps
- low 19 top-level sections: this looks like several domains in one skill
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
- -5TODO / placeholder text left in the skill
- +1No license
- +2Single-language instructions
- +3Description length 379: enough signal without eating the budget
- +4Structure: 28 headings
- +3Step-by-step instructions: 57 items
- +4Has examples (21 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 61.