CtrlK
BlogDocsLog inGet started
Tessl Logo

xlsx-official

Unless otherwise stated by the user or existing template

32

Quality

28%

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-claude/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

56%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 highly actionable and has a clear, validated recalc workflow, but it is verbose with redundant and elementary explanations and is structured as a single 290-line file that references a script not present in the bundle.

Suggestions

Trim the elementary pandas/openpyxl tutorials (df.head/info/describe, basic load_workbook) to assume Claude's competence, and consolidate the three recalc.py descriptions into one section.

Provide the referenced recalc.py in a scripts/ bundle directory (or inline its contents), since the workflow depends on a file that does not currently exist.

Move the detailed financial-modeling color/number/formula standards and the recalc.py JSON output schema into separate reference files linked from the overview, leaving SKILL.md as a concise entry point.

DimensionReasoningScore

Conciseness

The ~290-line body teaches concepts Claude already knows (pandas df.head/info/describe, basic openpyxl load_workbook, what #REF!/#DIV/0! errors are) and repeats the recalc.py instructions across three separate sections, making it noticeably padded.

2 / 5

Actionability

Concrete executable code (pandas read/write, openpyxl create/edit), explicit commands (`python recalc.py output.xlsx 30`), and exact RGB values and format strings make the guidance mostly copy-paste ready; the gap is that the referenced recalc.py is not present in any bundle.

4 / 5

Workflow Clarity

The numbered Common Workflow includes a mandatory recalculation step and a verify-and-fix feedback loop ("Fix the identified errors and recalculate again"), plus a Formula Verification Checklist, but the workflow is scattered across three redundant recalc sections rather than one canonical sequence.

4 / 5

Progressive Disclosure

No bundle files exist yet the body references recalc.py as if provided, and the large monolith inlines distinct domains (financial-modeling standards, general Excel ops, recalc output schema) that have section headers but no file-level separation.

3 / 5

Total

13

/

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 contains a sentence fragment copied from the body's color-coding section rather than an actual skill description. It fails every dimension because it conveys no capability, domain, or trigger.

Suggestions

Replace the description with a third-person capability statement, e.g. "Creates, edits, and analyzes .xlsx files using pandas and openpyxl, with formula recalculation via LibreOffice and financial-modeling formatting standards."

Add an explicit trigger clause: "Use when the user asks to create, edit, read, or analyze Excel spreadsheets or .xlsx files, or to build financial models."

Include natural synonyms and the file extension (.xlsx, Excel, spreadsheet, workbook) so the skill triggers on the phrases users actually say.

DimensionReasoningScore

Specificity

The description is "Unless otherwise stated by the user or existing template", which names no domain and no concrete actions — it is a stray conditional clause, not a capability statement.

1 / 5

Completeness

Neither "what does this do" nor "when should Claude use it" is answered; the text is a qualifier with no subject and no trigger clause.

1 / 5

Trigger Term Quality

No skill-relevant keywords (Excel, spreadsheet, .xlsx, formulas) appear; only the generic words "user" and "template" are present, none of which a user would say to invoke this skill.

1 / 5

Distinctiveness Conflict Risk

With no domain signal at all, the description cannot be distinguished from any other skill and carries maximal conflict risk.

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.

Validation15 / 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
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.