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

92%

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

85%Weight 40%Scale 1-5

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

A strong, highly actionable reference: executable commands, explicit validation/feedback workflows, and disciplined QA that respects destructive/batch operations. Its main weakness is progressive disclosure — everything lives in one large file with no reference/scripts bundle split, despite clear internal sectioning.

Suggestions

Split the lengthy 'Known Issues & Pitfalls' and per-element pitfall tables into a references/ file (e.g. PITFALLS.md) and link from the body, so SKILL.md stays a navigable overview.

Move the full CSV/bulk-import Python recipe and the financial-model color/number-format standards into references/ files referenced once from their sections, reducing repeated inline detail.

Consolidate the cross-sheet `!` / placeholder-token / cache-warning guidance that currently recurs across Shell Discipline, Common Workflow, QA, and Known Issues into a single canonical section to trim duplication.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and assumes Claude's competence (it explicitly says 'teaches what good xlsx looks like, not every command flag' and defers to help), but the body is long with some repeated guidance (e.g. token/placeholder warnings and cross-sheet `!` rules restated across sections), keeping it just below the lean anchor 5.	4 / 5
Actionability	Fully executable, copy-paste-ready commands throughout (Quick Start, named ranges via heredoc, validation, chart data forms) with specific examples covering common cases and exact prop shapes — matching the anchor 5 example.	5 / 5
Workflow Clarity	The six-step Common Workflow is explicitly sequenced with validation checkpoints (run `get` after structural ops, re-touch downstream formulas, eyeball cachedValue), and the QA section is a feedback loop (fix -> rerun full cycle), matching the anchor 5 example for a destructive/batch skill with validation.	5 / 5
Progressive Disclosure	The body is a single monolithic file with no bundle files (no references/, scripts/, assets/) and no external file references; it has good in-file section structure but content that could live in separate files (the long Known Issues / pitfall tables) is inlined, placing it at the 'some structure but could be better organized' anchor 3 rather than a split-file anchor 4-5.	3 / 5
	Total	17 / 20 Passed

Description

100%Weight 40%Scale 1-5

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 exemplary: it explicitly states both what the skill does (comprehensive concrete actions) and when to trigger it (named keywords and file extensions), in tight third-person scope. It hits every anchor-5 example pattern without padding.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions across the xlsx domain — 'creating spreadsheets, financial models, dashboards, or trackers; reading, parsing, or extracting data... editing, modifying... formulas, charts, pivot tables, or templates; importing CSV/TSV' — comprehensive coverage of the anchor 5 example.	5 / 5
Completeness	Clearly answers 'what' (the enumerated create/read/edit/import actions) and 'when' (the explicit 'Trigger whenever the user mentions...' clause with concrete trigger phrases), matching the anchor 5 example.	5 / 5
Trigger Term Quality	Explicit trigger list 'spreadsheet', 'workbook', 'Excel', 'financial model', 'tracker', 'dashboard' plus file extensions '.xlsx/.csv filename' provides comprehensive natural-term coverage with synonyms and extensions, matching the anchor 5 example.	5 / 5
Distinctiveness Conflict Risk	Scoped tightly to .xlsx/Excel artifacts with a clear niche and distinct trigger terms (workbook, pivot table, financial model), giving minimal conflict risk with non-spreadsheet skills, matching the anchor 5 example.	5 / 5
	Total	20 / 20 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: e701dba

Reviewed: 1 day 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.