CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

office-transform

Extract or edit a selection from xlsx, docx, pdf, or pptx into a new file; the source is never modified.

Quality

73%

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

Fix and improve this skill with Tessl

tessl review fix ./resources/skills/office-transform/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 exceptionally actionable and rigorously validated workflow guide — every operation has executable commands, exact data shapes, and explicit verification with failure handling. Its main weakness is verbosity: several rationale passages run long and one note is duplicated across sections, and some deep detail could move to the existing references layer.

Suggestions

Trim or relocate the anchor-check containment and number-format asymmetry discussion (several long paragraphs in "Input: selection references") into a reference file, keeping only the decision rule in SKILL.md.

State the ST_Xstring / escaped read-back behavior once — it currently appears under both "Verify before reporting success" and "Limits".

DimensionReasoningScore

Conciseness

The body is dense with genuinely non-obvious domain knowledge, but several passages could be tightened — the multi-paragraph anchor-check containment asymmetry, the mtime tolerance rationale, and the ST_Xstring note explained twice (in "Verify" and again in "Limits"). This matches 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than anchor 4's 'minor instances'.

3 / 5

Actionability

Fully executable throughout: copy-paste `uv run --with openpyxl python scripts/office_extract.py ...` commands, exact anchor and edit JSON shapes, shell-quoting rules for paths with spaces and quotes, a dependency-to-output-format table, and a concrete verification one-liner — covering the common cases for every operation.

5 / 5

Workflow Clarity

Clear routing ("When to use which tool"), explicit validation checkpoints (freshness check, anchor check, expectText gate, staged-then-renamed output), and feedback loops (re-select on changed file, refuse and stop on mismatched anchor, reopen-and-verify before reporting success with failure handling) — the full validate-fix-retry pattern for document manipulation.

5 / 5

Progressive Disclosure

The SKILL.md is a well-organized operation overview with clearly signaled, one-level-deep references ("Read [references/docx-edit.md](references/docx-edit.md) before writing any python-docx edit"), and both referenced files exist in the bundle. Held at 4 rather than 5 because a substantial block of anchor-check and Limits detail is inlined in the overview where a reference file would keep the entry point leaner.

4 / 5

Total

17

/

20

Passed

Description

53%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 states a clear, specific capability with an excellent safety invariant, but it omits any 'when to use' trigger guidance and lacks the natural-language synonyms (Excel, Word, PowerPoint) users actually say. Adding a Use-when clause and product names would lift completeness and trigger quality substantially.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user wants a derived file — an extracted range, converted fragment, or edited copy — from an Excel, Word, PDF, or PowerPoint document."

Add natural synonyms users say alongside the extensions: Excel/spreadsheet, Word, PowerPoint/presentation, not just xlsx, docx, pptx.

Mention the generate operation (creating fresh decks, workbooks, or documents from extracted data), since it is a documented capability of the skill but invisible in the description.

DimensionReasoningScore

Specificity

Names two concrete actions ("Extract or edit a selection") across four formats plus the new-file invariant, but stops at 1-2 actions — operations like generating or converting files are absent, matching the '1-2 concrete actions, not comprehensive' anchor rather than the 'several specific actions' anchor.

3 / 5

Completeness

The 'what' is clear ("Extract or edit a selection ... into a new file; the source is never modified") but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

"xlsx, docx, pdf, or pptx" supplies the four file extensions users say, but every common synonym (Excel, Word, PowerPoint, spreadsheet, presentation) is missing — the 'missing common variations or synonyms' anchor fits better than anchor 4's 'a few natural terms missing'.

3 / 5

Distinctiveness Conflict Risk

The four named formats and the "source is never modified" clause carve a mostly distinct niche with only minor overlap risk against generic document-reading skills; not 5 because reading/summarizing these same formats could still pull in a sibling skill.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

CherryHQ/cherry-studio

Path

resources/skills/office-transform/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.