CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

66

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/officecli/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 highly actionable, well-structured CLI reference with executable examples throughout and a clear layering strategy. It is somewhat verbose in places and monolithic—large reference tables and some explanatory prose could be split into separate files or trimmed.

Suggestions

Move the large per-format element-type tables (the dense add/set tables for pptx/docx/xlsx) into separate reference files referenced one level deep, reducing SKILL.md to an overview.

Tighten verbose prose sections (batch atomicity, Resident Mode) to terse guidance; the core facts are buried under explanation Claude can infer.

Add explicit validate→fix→revalidate feedback-loop sequences for destructive and batch operations rather than relying on a general 'verify after modifications' note.

DimensionReasoningScore

Conciseness

Mostly efficient reference prose with terse command blocks, but a few padded sections (the batch atomicity paragraph, Resident Mode explanation) could be tightened, and the large inlined element-type tables are dense.

3 / 5

Actionability

Extensive copy-paste-ready bash commands with concrete flags, paths, and worked examples across all three formats and L1/L2/L3 layers.

5 / 5

Workflow Clarity

Clear L1→L2→L3 strategy and a pitfall table, with validation present (validate, view issues) and batch rollback described; explicit validate→fix→retry feedback loops are only weakly sequenced rather than fully checkpointed.

4 / 5

Progressive Disclosure

Well-organized section headers, but the body is a large monolithic reference with no bundle files; content like the huge element-type tables that could live in separate reference files is inlined.

3 / 5

Total

15

/

20

Passed

Description

87%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 description: concrete actions, explicit 'Use when' trigger guidance, and a clearly scoped niche around Office documents and the officecli tool. Minor room to add natural synonyms (Word/Excel/PowerPoint) as triggers.

DimensionReasoningScore

Specificity

Lists several specific concrete actions ('Create, analyze, proofread, and modify') plus formats and tool, with only minor coverage gaps versus the comprehensive anchor.

4 / 5

Completeness

Explicitly answers both what (the four verbs + formats + tool) and when ('Use when the user wants to create, inspect, check formatting, find issues, add charts, or modify Office documents') with concrete triggers.

5 / 5

Trigger Term Quality

Good natural keywords ('create, inspect, check formatting, find issues, add charts, modify Office documents') but misses common synonyms like 'Word/Excel/PowerPoint' as trigger phrases.

4 / 5

Distinctiveness Conflict Risk

Scoped to Office formats via a named CLI with specific triggers, giving a clear niche and minimal overlap with other skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
iOfficeAI/OfficeCLI
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.