SKILLEMALL.ai

AC xlsx

Comprehensive spreadsheet creation, editing, and analysis with support for formulas, formatting, data analysis, and visualization. When Claude needs to work with spreadsheets (.xlsx, .xlsm, .csv, .tsv, etc) for: (1) Creating new spreadsheets with formulas and formatting, (2) Reading or analyzing data, (3) Modify existing spreadsheets while preserving formulas, (4) Data analysis and visualization in spreadsheets, or (5) Recalculating formulas

modbender/skill-library-mcp Agent Skills author: modbender MIT 3 files body ≈ 2 595 tokens Open the sourcegithub.com analyzed 34 h ago

Comprehensive spreadsheet creation, editing, and analysis with support for formulas, formatting, data analysis, and visualization.

As a process C 54/100 · Has gaps — weak spots: result and completion, when it triggers, running it twice

GeneratorExcelData and analyticstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
94/100
safety, quality, tests
Safety 60%
100
Quality 40%
85
Run on models
none yet
Process rating
C
54/100
Has gaps
Result and completion w 14
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

How to improve

    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: 3. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 54/100

    • 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. 4 mutating operations with no state check
    • 55Failures and branches. 1 branches
    • 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 85Steps. 72 steps, 3 vague phrases
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2595 tokens
    • low 12 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

    • +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 445: enough signal without eating the budget
    • +4Structure: 36 headings
    • +3Step-by-step instructions: 72 items
    • +4Has examples (9 code blocks)
    • +1License stated

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.