BF xlsx
Create, read, edit Excel spreadsheets (.xlsx, .xlsm, .csv). Supports formulas, formatting, charts, pivot tables, and data analysis with pandas.
As a process F 34/100 · Will not run — weak spots: steps, result and completion, when it triggers
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 · 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")
Process rating: all ten parameters 34/100
- 0Steps. Prose only: no discrete steps
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (xlsx) differs from the folder (xlsx-skill)
- 50Failures and branches. 0 branches, has a failure section
- 70Execution cost. Instruction body is 4111 tokens
- 100Tools and files. No external tools needed
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)
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +3Description length 143: enough signal without eating the budget
- +4Structure: 34 headings
- +4Has examples (24 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.
External checks
ClawHub: suspicious
The skills are mostly coherent developer-maintenance helpers, but one review helper defaults to launching a nested agent with full local access and can pass diffs to fallback review tools.
LLM: suspicious (medium) · VirusTotal: · 29 May 2026