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

94%

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

88%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 high-quality, highly actionable CLI skill with strong workflow structure and explicit validation/feedback loops. Its only weakness is token efficiency: a few key warnings are repeated across sections and some reference-like material is inlined in a single large file.

Suggestions

Consolidate the repeated placeholder-token warning (currently restated in Requirements, Charts, and QA) into one canonical statement with cross-references to reduce redundancy.

Factor the 'Known Issues & Pitfalls' backlog and the financial-modeling color/number-format standards into separate reference files (e.g. KNOWN_ISSUES.md, FINANCIAL_STANDARDS.md) and link to them from SKILL.md to shrink the monolith.

Move the duplicated print-layout guidance (in both Requirements for Outputs and QA) into a single location and reference it once.

Dimension	Reasoning	Score
Conciseness	Dense with CLI-specific knowledge Claude does not already know (prop names, shell-quoting rules, cache re-touch quirks) and free of basic-concept filler, but a few critical failure modes are repeated across sections (placeholder tokens, cross-sheet '!' trap, print layout) — minor trimming possible.	4 / 5
Actionability	Copy-paste-ready commands throughout with exact flags, paths, and prop values; a fully working Quick Start example and concrete recipes (CSV batch import) cover the common cases.	5 / 5
Workflow Clarity	A 6-step Common Workflow plus a required QA section with a 7-step minimum cycle, explicit validation (validate, view issues, view html), feedback loops ('rerun the full cycle'), and a formula-verification checklist — exactly the validate→fix→retry pattern batch/destructive work needs.	5 / 5
Progressive Disclosure	Well-organized with clear section headers, tables, and code blocks making navigation easy, but the skill is a ~490-line monolith with no bundle/reference files; reference-like content (Known Issues backlog, financial-modeling standards) is inlined rather than split out.	4 / 5
	Total	18 / 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.

An exemplary description: concrete capabilities, explicit trigger guidance, comprehensive natural keywords, and a clearly distinct xlsx niche. It answers 'what' and 'when' with no padding.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'creating spreadsheets, financial models, dashboards, or trackers; reading, parsing, or extracting data... editing, modifying, or updating... formulas, charts, pivot tables... importing CSV/TSV' — giving comprehensive coverage rather than vague abstractions.	5 / 5
Completeness	Explicitly answers both: 'what' via 'This includes: creating... importing CSV/TSV' and 'when' via 'Trigger whenever the user mentions...' with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural terms including synonyms and extensions — 'spreadsheet', 'workbook', 'Excel', 'financial model', 'tracker', 'dashboard', and '.xlsx/.csv filename' — exactly the phrases a user would say.	5 / 5
Distinctiveness Conflict Risk	Clear xlsx-specific niche with distinct triggers (workbook, Excel, .xlsx); the CSV/TSV mention is scoped to importing INTO Excel format, so overlap risk is minimal.	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: iOfficeAI/OfficeCLI
Path: skills/officecli-xlsx/SKILL.md
Commit: 459b1a4

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.