CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

xlsx

Inspect, edit, validate, and preview existing Excel workbooks and supported ranges.

Quality

72%

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/bundled-skills/xlsx/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 compact, well-organized instruction-only body with concrete tool routing and an explicit workflow, but it stops short of fully actionable guidance (no invocation details or operation examples) and lacks an error-recovery feedback loop for its hash-protected batch edits.

Suggestions

Add a feedback loop to the Workflow for failures, e.g., 'If the expectedSha256 check or formula validation fails, re-inspect the workbook, correct the operation batch, and re-apply.'

Include one or two concrete operation-batch examples or the office_edit invocation pattern (parameters, expectedSha256 usage) so the edit step is executable rather than descriptive.

Drop the 'Purpose' section that duplicates the frontmatter description verbatim and define what 'supported ranges' means, to tighten token efficiency and actionability.

DimensionReasoningScore

Conciseness

The body is lean, assumes competence, and explains no background concepts, but the 'Purpose' section repeats the description verbatim and 'supported ranges' is vague filler, which are minor tokens that could be trimmed, keeping it just below the 'every token earns its place' anchor.

4 / 5

Actionability

Concrete tool names (office_inspect, office_edit with expectedSha256) and a purpose-mapped routing table provide real guidance, but invocation syntax, the operation-batch format, and worked examples are missing, and 'Translate requested changes into the smallest structured operation batch' stays abstract, matching the 'some concrete guidance but incomplete' anchor.

3 / 5

Workflow Clarity

A clear 5-step sequence with explicit validation (step 5, completion gates, hash protection) is present, but this is a batch/document-manipulation workflow with no validate-fix-retry feedback loop (e.g., what to do when the expectedSha256 check or formula validation fails), which the rubric's feedback-loop rule caps at 3.

3 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references (no bundle files exist), and its well-organized sections (Tool routing, Workflow, Completion gates, Boundaries, Delivery) qualify for the simple-skill exception of scoring 5 on well-organized structure alone.

5 / 5

Total

15

/

20

Passed

Description

66%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 concise, third-person description that names a specific domain and four concrete capabilities, but it omits any 'Use when...' trigger guidance and common synonyms like 'spreadsheet' or '.xlsx', leaving completeness as the main weakness.

Suggestions

Append a trigger clause such as "Use when working with .xlsx files, spreadsheets, or Excel workbooks, or when the user mentions editing or validating spreadsheet data."

Add natural synonyms and the file extension ("spreadsheet", ".xlsx", "XLSX") to broaden trigger-term coverage.

Briefly hint at scope (e.g., sheets, formulas, validations, named ranges) to sharpen what 'inspect' covers and improve distinctiveness.

DimensionReasoningScore

Specificity

Lists four concrete actions ("Inspect, edit, validate, and preview") against the named Excel workbook domain, matching the 'several specific actions with minor gaps' anchor; it falls short of 5 because coverage is not comprehensive (no formulas/validations/macros scope, no file extension).

4 / 5

Completeness

The 'what' is clear (inspect, edit, validate, preview existing Excel workbooks) but there is no 'Use when...' clause or equivalent explicit trigger guidance, which the judging guidelines cap at 3; it is not 4 because the 'when' is entirely absent rather than just under-specified.

3 / 5

Trigger Term Quality

"Excel workbooks" plus the natural action verbs "edit", "validate", and "preview" give good keyword coverage akin to the 4-anchor example, but common variations like "spreadsheet" and ".xlsx" are missing, keeping it below 5.

4 / 5

Distinctiveness Conflict Risk

"Existing Excel workbooks and supported ranges" carves out a mostly distinct niche with only minor overlap risk against closely related skills (CSV or generic spreadsheet tools); it is not 5 because the description lacks explicit distinct trigger phrases.

4 / 5

Total

15

/

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

KunAgent/Kun

Path

resources/bundled-skills/xlsx/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.