Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
90
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that thoroughly covers capabilities, trigger conditions, and exclusion boundaries. It uses natural language trigger terms alongside specific file extensions, provides concrete examples of user phrasing, and clearly delineates when NOT to trigger — all of which make it highly effective for skill selection. The only minor note is the use of second person ('Use this skill') in the opening, but the rest is well-structured and actionable.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: open, read, edit, fix, add columns, compute formulas, format, chart, clean messy data, create new spreadsheets, convert between tabular file formats. Very comprehensive. | 3 / 3 |
Completeness | Clearly answers both 'what' (open, read, edit, create, convert spreadsheet files with specific sub-tasks) and 'when' (explicit trigger guidance including 'Trigger especially when the user references a spreadsheet file by name or path' and detailed use-when clauses). Also includes explicit negative triggers (Do NOT trigger for Word docs, HTML reports, etc.). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: .xlsx, .xlsm, .csv, .tsv, 'spreadsheet', 'the xlsx in my downloads', 'columns', 'formulas', 'formatting', 'charting', 'cleaning messy data'. Includes file extensions and casual phrasing examples. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with explicit boundary-setting: specifies exact file formats (.xlsx, .xlsm, .csv, .tsv), requires deliverable to be a spreadsheet file, and explicitly excludes Word documents, HTML reports, standalone Python scripts, database pipelines, and Google Sheets API integrations. This makes it very unlikely to conflict with adjacent skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, highly actionable skill with clear workflows and good validation loops for spreadsheet operations. Its main weakness is length — the financial modeling standards and formula verification sections are thorough but could be split into referenced files for better progressive disclosure. The content is mostly efficient but has some redundancy (recalc.py usage explained in multiple places) and a few sections that could be tightened.
Suggestions
Extract the 'Financial models' section (color coding, number formatting, formula construction rules, documentation requirements) into a separate FINANCIAL_MODELS.md reference file to reduce the main skill's token footprint
Consolidate the multiple mentions of scripts/recalc.py into a single authoritative section, referencing it from other places rather than re-explaining usage
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some unnecessary explanation (e.g., explaining what pandas does, the 'WRONG vs CORRECT' section is somewhat verbose with 6 examples when 2 would suffice). The financial model section is detailed and domain-specific enough to justify its length, but some sections like 'Best Practices' repeat information already covered (e.g., recalc.py mentioned multiple times). | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready code examples throughout — openpyxl creation/editing, pandas reading/writing, bash commands for recalculation, and specific formula patterns. The recalc.py JSON output format is documented concretely, and the wrong vs. correct formula examples are directly actionable. | 3 / 3 |
Workflow Clarity | The common workflow is clearly sequenced (choose tool → create/load → modify → save → recalculate → verify/fix errors) with an explicit validation feedback loop: recalculate, check for errors, fix, and recalculate again. The formula verification checklist adds additional validation checkpoints. The mandatory recalculation step is clearly called out. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers, but it's a long monolithic document (~200+ lines) that could benefit from splitting detailed sections (financial model standards, formula verification checklist) into separate reference files. References to scripts/recalc.py and scripts/office/soffice.py are present but no bundle files were provided to verify them. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
b27906e
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.