BF mailchimp-to-ghost
Sync Mailchimp newsletter posts to a Ghost blog. Fetches newsletter content from RSS, converts HTML to clean markdown with horizontal rules, uploads images to Ghost, and publishes as Lexical-format posts with proper formatting.
Sync Mailchimp newsletter posts to a Ghost blog.
As a process F 46/100 · Will not run — References files that are not bundled: ../ghst/SKILL.md, url
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- 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 · 0
✓ No critical or high findings
Files scanned: 5. 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") - warning
missing-refreference to a missing file: ../ghst/SKILL.md - warning
missing-refreference to a missing file: url - note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "caption"
Process rating: all ten parameters 46/100
- 0Tools and files. 2 referenced file(s) missing: ../ghst/SKILL.md, url
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 13 mutating operations with no state check
- 40Consistency. Frontmatter name (mailchimp-to-ghost) differs from the folder (mailchimp-to-ghost-skill)
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 56 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Execution cost. Instruction body is 1797 tokens
- low 10 top-level sections: this looks like several domains in one skill
- high The skill tells the model to perform an irreversible action with no human approval
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 227: enough signal without eating the budget
- +4Structure: 26 headings
- +3Step-by-step instructions: 56 items
- +4Has examples (11 code blocks)
- +3All 2 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.