AB Vincent - Twitter / X.com for agents
Twitter/X.com data access for agents. Use this skill when users want to search tweets, look up user profiles, or retrieve recent tweets. Pay-per-call via Vincent credit system. Triggers on "search tweets", "twitter", "X.com", "look up user", "tweet search", "twitter profile", "recent tweets".
As a process B 73/100 · Nearly there — weak spots: inputs and preconditions, consistency
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 · 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
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "source"
Process rating: all ten parameters 73/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 40Consistency. Frontmatter name (Vincent - Twitter / X.com for agents) differs from the folder (vincent-twitter)
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 85Steps. 21 steps, 1 vague phrases
- 100Tools and files. Tools declared in frontmatter
- 100Failures and branches. 5 branches, has a failure section
- 100Execution cost. Instruction body is 2254 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 10 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
- +4Description does not say when NOT to use the skill (false activations)
- +2Single-language instructions
- +5Description quotes 6 example trigger phrases
- +3Description length 293: enough signal without eating the budget
- +4Structure: 22 headings
- +3Step-by-step instructions: 21 items
- +3Output format is stated explicitly
- +4Has examples (13 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 86.