CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

xlsx-official

Unless otherwise stated by the user or existing template

Quality

47%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/xlsx-official/SKILL.md

The canonical home for this skill is xlsx-official in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

70%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 a strong, actionable reference for xlsx work: executable code for pandas and openpyxl, a mandatory recalculate-then-verify workflow with a genuine fix-and-retry feedback loop, and checklists for common pitfalls. Its weaknesses are verbosity (novice-level padding and quadruple-repeated error lists) and a monolithic structure that inlines financial-modeling standards and references a recalc.py script that is missing from the bundle.

Suggestions

Consolidate the four overlapping error lists (#REF!, #DIV/0!, #VALUE!, #NAME?) into the single 'Interpreting recalc.py Output' section, and cut the df.head()/info()/describe() and 'Hello World' snippets that teach what Claude already knows.

Split the financial-modeling output standards (color coding, number formatting, source documentation) into a separate references/ file (e.g. financial-modeling-standards.md) linked from a short overview, and actually bundle recalc.py under scripts/ so the mandatory workflow step is executable.

Reconcile the two top-level sections ('Requirements for Outputs' and 'XLSX creation, editing, and analysis') into one coherent document, since their duplicated guidance (zero formula errors, verification steps) currently competes for the reader's attention.

DimensionReasoningScore

Conciseness

Mostly efficient, but it includes novice-level padding ('pandas which provides powerful data manipulation capabilities', df.head()/info()/describe() basics, sheet['A1'] = 'Hello') and repeats the same Excel-error list (#REF!, #DIV/0!, #VALUE!, #NAME?) roughly four times across the 'Zero Formula Errors', 'Common Workflow', 'Common Pitfalls', and recalc-output sections. This exceeds the 'minor instances' bar for a 4.

3 / 5

Actionability

Concrete, executable guidance throughout: runnable pandas/openpyxl snippets, the exact command 'python recalc.py output.xlsx 30', and the JSON output schema with error locations. Not a 5 because the mandatory recalc.py is invoked as 'the provided recalc.py script' yet is not present in any scripts/ directory, leaving a core step not self-contained.

4 / 5

Workflow Clarity

The 'Common Workflow' gives a clear 1–6 sequence with an explicit mandatory recalculation checkpoint and a feedback loop ('Fix the identified errors and recalculate again'), plus a 'Formula Verification Checklist' of quick checks and pitfalls. Validation for batch spreadsheet edits is explicitly present, so no cap applies.

5 / 5

Progressive Disclosure

Header-based structure makes the file navigable, but two heterogeneous domains (financial-modeling output standards vs. xlsx tooling how-tos) are inlined in one ~290-line file, and the only referenced path, recalc.py, does not exist in the bundle. Content that clearly belongs in a separate reference file is inline and the script reference is not clearly signaled as a bundle file, which fits the 'some structure but could be better organized' anchor.

3 / 5

Total

15

/

20

Passed

Description

0%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 field is critically broken: it contains only a conditional clause ("Unless otherwise stated by the user or existing template") with no capability statement, no triggers, and no domain. It appears a fragment of the body's formatting guidance was accidentally placed in the frontmatter. This guarantees the skill will never be selected by description-based triggering.

Suggestions

Rewrite the description to state the skill's capabilities in third person, e.g.: 'Create, edit, and analyze .xlsx files with openpyxl and pandas, apply financial-modeling formatting standards (color coding, number formats), and recalculate formulas with LibreOffice.'

Add an explicit 'Use when...' clause covering natural triggers: 'Use when the user asks to create, edit, read, or analyze Excel files, spreadsheets, or .xlsx data, or needs financial-model formatting conventions.'

Move the stray 'Unless otherwise stated by the user or existing template' qualifier into the body where it is already duplicated, and keep the frontmatter description self-contained.

DimensionReasoningScore

Specificity

The description is a conditional fragment ("Unless otherwise stated by the user or existing template") that names no domain and no concrete actions. A score of 2 would require at least naming a domain, which this does not do.

1 / 5

Completeness

Neither 'what does this do' nor 'when to use it' is present; the fragment answers neither question. It reads as a stray sentence that belongs inside the body's color-coding section (duplicated verbatim at line 24).

1 / 5

Trigger Term Quality

There are no natural keywords whatsoever — no 'Excel', 'xlsx', 'spreadsheet', or any phrase a user would say when needing this skill. It is not even generic jargon, just a dangling qualifier.

1 / 5

Distinctiveness Conflict Risk

Entirely generic and content-free, it would conflict with virtually any skill. It provides no basis for distinguishing this skill from any other.

1 / 5

Total

4

/

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

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills/skills/xlsx-official/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.