officecli

Create, analyze, proofread, and modify Office documents (.docx, .xlsx, .pptx) using the officecli CLI tool. Use when the user wants to create, inspect, check formatting, find issues, add charts, or modify Office documents.

Quality

96%

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

92%

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

The body is an exceptionally action-dense, executable CLI reference with clear layered workflow and validation guidance. Its main weakness is progressive disclosure: much of the exhaustive per-format element reference is kept inline rather than offloaded to separate files.

Suggestions

Move the large per-format element-type tables (pptx/docx/xlsx) into separate reference files under ./references/ and link to them from a concise summary in the body, reducing the inline monolithic bulk.

Consider splitting the detailed sub-topics (pivot tables, marks pipeline, raw XML) into one-level-deep reference files with clear "See X.md" signals, mirroring the load_skill routing pattern already used for specialized skills.

Add a brief top-of-file table of contents or navigation map so the dense ~400-line reference is easier to scan and selectively load.

Dimension	Reasoning	Score
Conciseness	The body is dense and reference-driven (commands, flags, property tables) with no padding about what Office formats or basic concepts are; e.g. "Single binary, no dependencies, no Office installation needed" and "Paths are 1-based (XPath convention)" assume Claude's competence, matching the lean/efficient anchor.	3 / 3
Actionability	Examples are fully executable and copy-paste ready, e.g. `officecli add report.docx /body --type paragraph --prop text="Executive Summary"` and a complete pivot-table invocation, satisfying the highest anchor for concrete executable guidance.	3 / 3
Workflow Clarity	A clear L1(read)→L2(DOM edit)→L3(raw XML) sequence is given with explicit validation ("verify with `validate` and/or `view issues`") and error-recovery feedback (batch stops on first error / `--force`; "run help instead of guessing"), matching the anchor for clear sequencing with validation checkpoints.	3 / 3
Progressive Disclosure	Section organization is good and the `officecli load_skill` routing table signals one-level-deep specialized skills, but the bulk of reference content (the large pptx/docx/xlsx element-type tables) is inline in a ~400-line monolithic file rather than split into separate reference files, fitting the "content that should be separate is inline" anchor.	2 / 3
	Total	11 / 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.

The description is concrete, action-oriented, and explicitly covers both capability and trigger conditions with natural user vocabulary. It is a strong, distinctive skill description with no notable weaknesses.

Dimension	Reasoning	Score
Specificity	"Create, analyze, proofread, and modify Office documents (.docx, .xlsx, .pptx)" plus "create, inspect, check formatting, find issues, add charts, or modify" lists multiple specific concrete actions, matching the highest anchor; it is not the level below since the action set is comprehensive rather than partial.	3 / 3
Completeness	It states what the skill does (Create/analyze/proofread/modify Office documents via officecli) and an explicit "Use when the user wants to create, inspect, check formatting, find issues, add charts, or modify Office documents" clause, clearly answering both what and when.	3 / 3
Trigger Term Quality	Triggers like "create", "inspect", "check formatting", "find issues", "add charts", and "modify Office documents" are natural terms a user would say, giving good coverage; it exceeds the level-2 anchor which expects missing common variations.	3 / 3
Distinctiveness Conflict Risk	Scoping to "Office documents (.docx, .xlsx, .pptx) using the officecli CLI tool" with distinct triggers (check formatting, find issues, add charts) carves a clear niche unlikely to trigger for unrelated skills.	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/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.