CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

excel-cli

Quick start for changing or checking an Excel workbook with the excelcli command. Use before your first excelcli call. Gives the usual open, change, check and save routine and the exact batch names for common actions, so you can skip most --help and list-actions lookups.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

96%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 an exemplar quick-start: lean, fully executable, and built around a clearly sequenced three-call routine with explicit validation checkpoints for a batch-operation tool. The only structural question is whether the large inline command table belongs in a reference file, which keeps progressive disclosure at 4.

DimensionReasoningScore

Conciseness

Every line is excelcli-specific operational knowledge (PATH fallback, batch mechanics, command names, overwrite policy) with zero explanation of concepts Claude already knows and no padding. Matches the "lean and efficient; every token earns its place" anchor; the reference table is dense information, not verbosity.

5 / 5

Actionability

Fully executable guidance: a copy-paste JSON batch example with real syntax (including Windows path escaping), a table of 30+ exact commands with exact case-sensitive camelCase argument names and formats (e.g. `"overwritePolicy":"allow"`, `sortColumns` example structure), plus the exact CLI flags (`--session <sessionId> --stop-on-error`, `--input <file>`). Nothing is pseudocode or vague.

5 / 5

Workflow Clarity

The three-call routine is explicitly sequenced with validation checkpoints throughout: check each entry's `success` (with the note that one failed entry does not undo the others), write-then-read-back in the same batch "so one result shows that the change worked", save only "after step 2's reads look right", and check `autoSaveOn`/`warning` before editing. This satisfies the batch-operation validation requirement and matches the explicit-validation-with-feedback anchor.

5 / 5

Progressive Disclosure

Two well-organized sections with a clearly signaled fallback ("Only run `<group> <action> --help` for actions that are not listed here") and no buried references. Not a 5: the body runs ~97 lines (above the sub-50-line simple-skill threshold) with a large inline command table that could plausibly live in a separate reference file, which is a minor organization gap rather than good placement.

4 / 5

Total

19

/

20

Passed

Description

62%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 clearly states what the skill provides and when to use it (before the first excelcli call), and its excelcli binding makes it reasonably distinct. Its main weaknesses are limited trigger-term coverage (no spreadsheet/.xlsx/pivot/chart synonyms), routine-level rather than capability-level specificity, and a second-person aside.

Suggestions

Add natural trigger terms and synonyms: spreadsheet, .xlsx, pivot table, chart, or formula — e.g. "Use when the user asks to edit, check, or analyze an Excel workbook (.xlsx) via excelcli".

Replace the generic "open, change, check and save routine" with a few concrete capabilities the CLI covers (write values and formulas, sort/filter ranges, pivot tables, charts, Power Query refresh) so specificity reaches the comprehensive anchor.

Remove the second-person clause ("so you can skip most --help and list-actions lookups") or restate it impersonally, e.g. "lets most --help and list-actions lookups be skipped".

DimensionReasoningScore

Specificity

The description names the domain ("changing or checking an Excel workbook with the excelcli command") and routine-level actions ("open, change, check and save routine", "exact batch names"), but the actions are generic operation verbs rather than specific capabilities (no pivot tables, charts, formatting, or Power Query are named), and it slips into second person ("so you can skip most --help and list-actions lookups"), which the rubric penalizes. Not a 4 because it lacks several distinct concrete actions; not a 2 because the domain and routine are clearly stated.

3 / 5

Completeness

Both parts are present: a clear what ("Gives the usual open, change, check and save routine and the exact batch names for common actions") and an explicit when ("Use before your first excelcli call"), so the missing-trigger cap at 3 does not apply. Not a 5 because the when-clause only covers the first-call scenario and gives no concrete user-side trigger phrases (e.g. "use when the user asks to edit an Excel file").

4 / 5

Trigger Term Quality

"Excel workbook" and "Excel" are the most natural user terms, but the description omits common variations and synonyms such as "spreadsheet", ".xlsx", "pivot table", "chart", or "formulas". Matches anchor 3 (some relevant keywords, missing common variations) rather than 4, where keyword coverage would be broad.

3 / 5

Distinctiveness Conflict Risk

The description is tightly bound to the specific "excelcli" command, giving it a clear niche with distinct triggers, but "changing or checking an Excel workbook" leaves minor overlap risk with other Excel/spreadsheet-manipulation skills. Fits anchor 4 rather than 5 because the capability wording is broad enough to collide with closely related skills.

4 / 5

Total

14

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

sbroenne/mcp-server-excel

Path

.github/plugins/excel-cli/skills/excel-cli/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.