xlsx

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.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

77%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with executable code, a clear numbered workflow, and an explicit validate/fix/recalculate feedback loop. It is let down mainly by conciseness (repetition and beginner-level explanations) and only partial progressive disclosure.

Suggestions

Remove or condense the elementary pandas/openpyxl explanations (e.g. df.head()/df.info() commentary) and de-duplicate the recalc instructions so the script is documented once.

Move the detailed financial-model color/number-formatting rules into a separate references file (e.g. FORMATTING.md) linked from a short overview, improving progressive disclosure.

Note the office shared-module dependency (scripts/office -> ../../_shared/office) explicitly so the referenced bundle structure is discoverable rather than implicit.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable snippets and a terse code-style guideline, but it includes some content Claude already knows (basic pandas read/write, openpyxl cell assignment) and repeats the recalc instructions across multiple sections, so it could be tightened.	2 / 3
Actionability	Provides fully executable, copy-paste-ready code for pandas and openpyxl, concrete commands ("python scripts/recalc.py output.xlsx"), and a worked JSON-output schema, matching the highest anchor for executable guidance.	3 / 3
Workflow Clarity	The Common Workflow is a clearly numbered sequence with an explicit mandatory recalculation step and a feedback loop — "Fix the identified errors and recalculate again" — backed by a Formula Verification Checklist, satisfying the top anchor for validation checkpoints.	3 / 3
Progressive Disclosure	The body is a single moderately long file with clear section headers and references the real bundled scripts/recalc.py, but the office bundle dependency is not surfaced as a navigable reference, no separate reference files exist, and detailed formatting/color rules are inlined rather than split out, so structure is good but not maximally decomposed.	2 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, trigger-rich, and explicit about both what it does and when to use it, with strong negative-boundary scoping. It is somewhat verbose, but every clause is concrete rather than fluffy.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file", "create a new spreadsheet from scratch", "convert between tabular file formats", "cleaning or restructuring messy tabular data files" — matching the highest anchor that requires listing multiple specific concrete actions.	3 / 3
Completeness	Clearly answers both what (the enumerated spreadsheet operations) and when ("Use this skill any time a spreadsheet file is the primary input or output", "Trigger especially when the user references a spreadsheet file by name or path") with explicit triggers plus negative-boundary exclusions.	3 / 3
Trigger Term Quality	Covers natural terms a user would say — "spreadsheet file", ".xlsx", ".xlsm", ".csv", ".tsv", "the xlsx in my downloads", "messy tabular data" — giving broad coverage of common variations, matching the top anchor.	3 / 3
Distinctiveness Conflict Risk	Carves a clear niche (spreadsheet files as primary deliverable) and explicitly excludes adjacent domains ("Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration"), making conflict with other skills unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: nextlevelbuilder/goclaw
Path: skills/xlsx/SKILL.md
Commit: e71d6a5

Reviewed: 10 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

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.