officecli-xlsx

Use this skill any time a .xlsx file is involved -- as input, output, or both. This includes: creating spreadsheets, financial models, dashboards, or trackers; reading, parsing, or extracting data from any .xlsx file; editing, modifying, or updating existing workbooks; working with formulas, charts, pivot tables, or templates; importing CSV/TSV data into Excel format. Trigger whenever the user mentions 'spreadsheet', 'workbook', 'Excel', 'financial model', 'tracker', 'dashboard', or references a .xlsx/.csv filename.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Quality

Content

77%

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

A highly actionable, well-sequenced skill with strong workflow and validation guidance. Its main weaknesses are token-efficiency (cross-section repetition in a long single file) and the absence of progressive disclosure into separate reference files.

Suggestions

Consolidate the repeated traps (placeholder tokens, chart-anchor immutability, cross-sheet '!' mangling, font.color/fill ambiguity) into a single authoritative Known Issues entry and cross-reference it instead of restating each 2–3 times.

Move the large reference-style material — the Known Issues & Pitfalls backlog and the financial-model color-coding/number-format standards — into separate bundle files under references/ and link to them from SKILL.md to improve progressive disclosure.

Tighten the Requirements/Visual-delivery and QA sections, which overlap on the same ### and placeholder-token checks, into one canonical checklist.

Dimension	Reasoning	Score
Conciseness	The body assumes Claude's competence (no 'what is a spreadsheet' filler), but at ~480 lines it restates several critical traps multiple times across sections — placeholder tokens, chart-anchor immutability, the cross-sheet '!' mangling, and the font.color/fill ambiguity each appear 2–3 times — so it lands at 'mostly efficient but could be tightened' rather than 'every token earns its place'.	2 / 3
Actionability	Fully copy-paste-ready throughout: a complete Quick Start recipe, a full Python+batch CSV import recipe, exact numFmt strings, and concrete shell-quoted set/get/batch commands — matching the 'fully executable, copy-paste ready' anchor.	3 / 3
Workflow Clarity	The 6-step Common Workflow plus the QA 'Minimum cycle before done' provide an explicit sequence with validation checkpoints and a clear validate→fix→rerun feedback loop, reinforced by a formula-verification checklist.	3 / 3
Progressive Disclosure	No bundle files exist and the skill is a single ~480-line document; well-sectioned, but content that could live in separate references (the Known Issues backlog, financial-model color standards, chart details) is inline, matching 'some structure… content that should be separate is inline'; the under-50-line exception does not apply.	2 / 3
	Total	10 / 12 Passed

Description

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.

An excellent description: it is specific, lists natural trigger terms, explicitly answers both what and when, and occupies a clear niche unlikely to conflict with other skills. No changes needed.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions — 'creating spreadsheets, financial models, dashboards, or trackers; reading, parsing, or extracting data…; editing, modifying, or updating existing workbooks; working with formulas, charts, pivot tables, or templates; importing CSV/TSV' — matching the 'multiple specific concrete actions' anchor; the 'Use this skill' imperative is consistent with the rubric's own good examples, so no voice penalty applies.	3 / 3
Completeness	Clearly answers both 'what' (creating/reading/editing/importing) and 'when' via explicit trigger clauses ('Use this skill any time a .xlsx file is involved', 'Trigger whenever the user mentions…'), matching the anchor-3 example.	3 / 3
Trigger Term Quality	An explicit trigger list covers natural user terms — "'spreadsheet', 'workbook', 'Excel', 'financial model', 'tracker', 'dashboard', or references a .xlsx/.csv filename" — giving good coverage of phrases users would actually say.	3 / 3
Distinctiveness Conflict Risk	Tightly scoped to .xlsx/Excel artifacts with distinct, file-format-specific triggers, making it unlikely to fire for an unrelated skill.	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: Team-Commonly/commonly
Path: backend/commonly-bundled-skills/officecli/skills/officecli-xlsx/SKILL.md
Commit: 69b6005

Reviewed: about 18 hours 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.