BF x-poster
Post to X (Twitter) using the OpenTweet API. Create tweets, schedule posts, publish threads, write and schedule long-form X Articles from markdown, upload media, run an evergreen queue, search inspiration tweets, repurpose them with AI, run AI-qualified DM outreach campaigns with human-approved sending, and read engagement-weighted analytics, all autonomously.
As a process F 51/100 · Will not run — References files that are not bundled: 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 SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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: 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") - warning
body-longSKILL.md body ≈ 7765 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: url - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 51/100
- 0Tools and files. 1 referenced file(s) missing: url
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 106 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 40Consistency. Frontmatter name (x-poster) differs from the folder (opentweet-x-poster)
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 7765 tokens
- 100Steps. 117 steps
- 100Failures and branches. 5 branches, has a failure section
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 15 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (4 tags): a typed call is more reliable
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 362: enough signal without eating the budget
- +4Structure: 68 headings
- +3Step-by-step instructions: 117 items
- +4Has examples (47 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 55.