CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a dense, highly actionable command reference with copy-paste examples for all three Office formats, a clear layered editing strategy, and well-structured delegation to the CLI's own help system and sub-skills. Its weaknesses are modest: some bulk enumerations duplicate help-system content, and validation guidance exists but lacks an explicit fix-and-retry loop.

DimensionReasoningScore

Conciseness

The body is a dense, command-first reference with no explanations of concepts Claude already knows, but bulky enumerations (the per-format element-types tables, pivot/marks prop lists) duplicate content the skill itself says is available via `officecli help <format> <element>` and could be trimmed. Anchor 4's "efficient; minor instances ... that could be trimmed" fits better than anchor 5's every-token-earns-its-place.

4 / 5

Actionability

Nearly every section contains copy-paste-ready executable commands — Quick Start examples for all three formats, set/add/find/batch usage, clone and raw-set syntax — and the Common Pitfalls table pairs each mistake with the exact correct command, matching anchor 5's fully-executable, common-cases-covered standard.

5 / 5

Workflow Clarity

The L1 (read) → L2 (DOM edit) → L3 (raw XML) strategy with "prefer higher layers", the help-first rule, and post-edit verification ("After modifications, verify with `validate` and/or `view issues`") form a clear sequence with most checkpoints present. However there is no explicit validate → fix → re-validate feedback loop, so anchor 4 applies rather than anchor 5; validation steps are present, so the destructive/batch cap of 3 does not trigger.

4 / 5

Progressive Disclosure

No bundle files exist, but the skill practices disclosure through the tool itself: clearly signaled one-level-deep delegation to `officecli help` for full schemas and to `officecli load_skill` sub-skills with "When to use" routing tables and an explicit loading rule. This matches anchor 4's good structure with minor organization gaps — the large inline element-type tables arguably belong in the help system entirely.

4 / 5

Total

17

/

20

Passed

Description

88%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 explicitly and clearly covers both what the skill does and when to use it, with concrete action verbs, trigger phrases, and file extensions. Its main weakness is missing the natural synonyms users most often say (Word, Excel, PowerPoint, presentation, spreadsheet), which limits trigger-term coverage and slightly raises overlap risk with closely related document skills.

DimensionReasoningScore

Specificity

"Create, analyze, proofread, and modify Office documents (.docx, .xlsx, .pptx)" plus "inspect, check formatting, find issues, add charts" lists multiple concrete actions with explicit file extensions, comprehensively covering the tool's domain. Anchor 4's "minor gaps in coverage" does not apply since both the what- and when-clauses enumerate the full action set.

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, matching the anchor-5 pattern exactly.

5 / 5

Trigger Term Quality

Extensions (.docx, .xlsx, .pptx) and natural phrases like "check formatting", "find issues", "add charts" are present, but the most common user synonyms — "Word", "Excel", "PowerPoint", "presentation", "spreadsheet", "deck" — are all missing, which is more than the "a few natural terms missing" of anchor 4 but short of anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The officecli-scoped, extension-pinned trigger set gives a clear niche with minimal conflict against unrelated skills, but claiming the entire Office tri-format domain directly overlaps closely related single-format document skills (e.g. dedicated docx/pptx/xlsx skills), matching anchor 4's "minor overlap risk with closely related skills" rather than anchor 5's minimal risk.

4 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

Team-Commonly/commonly

Path

backend/commonly-bundled-skills/officecli/SKILL.md

Reviewed

Table of Contents

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.