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

84%

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

76%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 dense, highly actionable CLI reference that assumes competence and delegates detail to the tool's own help system. Its main weaknesses are batch/destructive workflows missing integrated validation feedback loops and some bulky reference tables that could live in separate files.

Suggestions

Add an explicit validate→fix→retry feedback loop to the batch and raw-set (L3) sections, e.g. 'After batch, run officecli validate <file>; on failure fix inputs and re-run with --force', so destructive/batch workflows clear the workflow_clarity cap.

Move the large per-format element-type tables (pptx/docx/xlsx rows) into bundled reference files (e.g. references/element-types.md) and link to them, improving progressive disclosure and conciseness while keeping the overview lean.

Trim the Notes section's repeated 'when unsure, run help' guidance into a single consolidated checkpoint to reduce token redundancy.

Dimension	Reasoning	Score
Conciseness	Lean, competent prose with no beginner-concept padding and tight command/examples throughout, but the large inline element-type and property tables (e.g. the pptx/docx/xlsx type rows) could be trimmed or delegated, keeping it just short of 'every token earns its place'.	4 / 5
Actionability	Abundant copy-paste-ready, fully executable CLI commands with real flags and per-format examples spanning creation, find/replace, pivot tables, raw XML, and batch — covering the common cases concretely.	5 / 5
Workflow Clarity	The L1→L2→L3 strategy gives a clear sequence and a general 'verify with validate and/or view issues' note exists, but destructive/batch workflows (remove, raw-set replace, batch --force) lack integrated validate-then-fix feedback loops, so the batch/destructive cap at 3 applies.	3 / 5
Progressive Disclosure	Well-sectioned overview that delegates deep schemas to 'officecli help <fmt> <element>' and specialized domains to 'load_skill', both clearly and repeatedly signaled; no bundle files exist, and the main gap is bulk reference tables inlined rather than split out.	4 / 5
	Total	16 / 20 Passed

Description

92%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.

A strong, third-person description that cleanly states both capability and trigger conditions with concrete verbs and file extensions. The only gap is the absence of common product-name synonyms (Word/Excel/PowerPoint) among the trigger terms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Create, analyze, proofread, and modify') across three named formats via a named tool, matching the comprehensive-coverage anchor; not a 4 because no meaningful action gaps remain in the 'what'.	5 / 5
Completeness	Explicitly answers both what ('Create, analyze, proofread, and modify Office documents... using the officecli CLI tool') and when ('Use when the user wants to create, inspect, check formatting, find issues, add charts, or modify Office documents') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural trigger phrases ('create, inspect, check formatting, find issues, add charts, or modify') plus extensions (.docx/.xlsx/.pptx), but missing common product-name synonyms (Word/Excel/PowerPoint), so it stops just short of fully comprehensive.	4 / 5
Distinctiveness Conflict Risk	Tied to a specific named CLI ('officecli') and three exact formats, giving a clear niche with minimal overlap risk; the tool-specific framing distinguishes it from generic document skills.	5 / 5
	Total	19 / 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/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.