BC x-trends
Fetches current top trending topics on X (Twitter) for any country using public aggregators.
Fetches current top trending topics on X (Twitter) for any country using public aggregators.
As a process C 52/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches
Proceduretype and topics are labelled automatically from the skill text
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
- 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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:79High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…NxY+fzEC…TMw+Dfs3…h4g==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:174High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…9co+7Zrb…CSH/zJvXw56gmHw==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:221High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…Eg5+wW0/QaZM…swK/w2MWU+Gw==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:277High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…uff+RtWa…OPA==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:289High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…CUH+OiuIgU++RB0+94Nl…dMw==",
detector
Files scanned: 4. 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")
Process rating: all ten parameters 52/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 85Steps. 4 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 186 tokens
- 100Running it twice. No mutating operations
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)
- +3Description length 92: 120–800 characters recommended
- +2Single-language instructions
- +4Structure: 5 headings
- +3Step-by-step instructions: 4 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.