CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

excel-automation

Creates formatted Excel reports with openpyxl, parses complex xlsm financial models with stdlib zipfile+xml when openpyxl fails, and controls Excel windows on macOS via AppleScript. Reconstructs images or scans of paper forms as editable XLSX files with printable layouts.

Quality

78%

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 ./daymade-docs/excel-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 dense, highly actionable reference with executable commands, verified AppleScript patterns, and real error-recovery checkpoints. Its weaknesses are redundancy — inlined code and color tables that duplicate existing bundle files — and a slightly buried formatting reference.

Suggestions

Trim the inlined get_sheet_path/extract_cells/fix_defined_names code to key excerpts (e.g., namespace constants and the rId resolution trick) and defer the rest to scripts/parse_complex_excel.py, which already contains the full templates.

Replace the duplicated color-convention table with a pointer to references/formatting-reference.md, keeping only the paper-form exception inline.

Promote references/formatting-reference.md from a bare 'See' line at the bottom to a clearly labeled link (like the printable-forms link) so both references are equally discoverable.

DimensionReasoningScore

Conciseness

The body is mostly tables and runnable code with little conceptual padding, but it duplicates material that already lives in the bundle: ~100 lines of get_sheet_path/extract_cells/fix_defined_names are inlined even though "Full template script: See scripts/parse_complex_excel.py", and the color-convention table overlaps references/formatting-reference.md. This matches the score-3 anchor (mostly efficient but some content could be tightened/trimmed) rather than 4, where only minor over-explanation remains.

3 / 5

Actionability

Everything is copy-paste executable: `uv run --with openpyxl scripts/create_formatted_excel.py output.xlsx`, three parse_complex_excel.py usage variants, complete Python functions with namespace constants, and verified AppleScript commands wrapped in `timeout 5` with exit-code 124 handling. This matches the score-5 anchor (fully executable, covers the common cases) — no gaps down to 4's 'minor gaps' level.

5 / 5

Workflow Clarity

Tool selection is a clear decision tree with explicit complexity signals, and the flow includes real checkpoints — "Always run `file <path>` first", the osascript timeout with `if [ $? -eq 124 ]` error recovery, and `sleep 1` timing between UI steps. It fits the score-4 anchor (clear sequence, most checkpoints present) rather than 5, since the parsing/fixing path lacks an explicit validate-output step after repackaging; the destructive/batch cap does not apply because fix_defined_names writes a new file rather than overwriting the source.

4 / 5

Progressive Disclosure

Structure is good: all four bundle files referenced in the body (references/printable-forms.md, references/formatting-reference.md, scripts/create_formatted_excel.py, scripts/parse_complex_excel.py) exist and are exactly one level deep with no nested references. It sits at the score-4 anchor rather than 5 because formatting-reference.md is only a bare "See" line buried under Important Notes rather than a clearly signaled link, and the inlined parsing functions duplicate the referenced script.

4 / 5

Total

16

/

20

Passed

Description

71%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 highly specific, tool-anchored description that clearly communicates what the skill does across four distinct capabilities. Its main weakness is the absence of any explicit 'Use when...' trigger guidance, which caps completeness and leaves invocation conditions implicit.

Suggestions

Add an explicit trigger clause such as "Use when working with Excel files, .xlsm financial models, spreadsheets, or scans of paper forms that need editable cells." to raise completeness.

Include natural synonyms and extensions users say — "spreadsheet", ".xlsx", ".xlsm" — to broaden trigger term coverage.

Consider naming the conditional parsing path more as a user-facing scenario (e.g., "when openpyxl fails on investment-bank workbooks") so it reads as a trigger rather than an internal fallback.

DimensionReasoningScore

Specificity

The description lists four concrete actions each paired with a specific tool: "Creates formatted Excel reports with openpyxl", "parses complex xlsm financial models with stdlib zipfile+xml when openpyxl fails", "controls Excel windows on macOS via AppleScript", and "Reconstructs images or scans of paper forms as editable XLSX files with printable layouts". This matches the score-5 anchor (multiple specific concrete actions, comprehensive coverage) and exceeds the score-4 anchor, which allows minor gaps in coverage.

5 / 5

Completeness

The "what" is clearly and fully answered (four named capabilities), but there is no "Use when..." clause or equivalent explicit trigger guidance; the only conditional phrase, "when openpyxl fails", describes an internal fallback rather than when to invoke the skill. Per the rubric guideline, a missing 'Use when...' clause caps completeness at 3 (clear 'what', 'when' missing).

3 / 5

Trigger Term Quality

Strong natural keywords users would actually say: "Excel", "xlsm", "XLSX", "financial models", "paper forms", "scans", "macOS", plus tool names openpyxl and AppleScript. It falls just short of the score-5 anchor because common synonyms like "spreadsheet" and the explicit ".xlsx" extension phrase are missing, matching the score-4 anchor (good keyword coverage; a few natural terms missing).

4 / 5

Distinctiveness Conflict Risk

The combination of xlsm financial-model parsing via stdlib zipfile+xml, macOS AppleScript window control, and paper-form reconstruction gives the skill a clear niche with distinct triggers, matching the score-4 anchor (mostly distinct; minor overlap risk with closely related generic Excel or document skills).

4 / 5

Total

16

/

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

daymade/claude-code-skills

Path

daymade-docs/excel-automation/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.