CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-creator

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or iterate on skill quality. Triggers: "create a skill", "make a new skill", "build a skill for", "write a skill that", "skill for doing X", "I want a skill to", "new skill", "design a skill", "scaffold a skill", "improve this skill", "optimize this skill", "this skill isn't working well", "evaluate this skill", "score this skill", "how good is this skill", "run evals on", "benchmark this skill", "test this skill's quality", "skill quality", "skill performance". Also triggers when a user describes a repeatable workflow they want to automate, says "I keep doing X manually", "can you remember how to do X", or "turn this into a skill".

75

Quality

92%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 well-structured, multi-step skill with clear routing, validation checkpoints, and excellent progressive disclosure via six real reference files. Minor conciseness and actionability gaps come from illustrative scorecard tables and some process-level guidance.

Suggestions

Trim the illustrative scorecard tables in Steps 6b and 7c (example scores and 'Top 3 Improvements' placeholders) since they restate the same guidance as the checklist and rubric references.

Make the detection-flow guidance more copy-paste-ready by including a concrete composite command example (e.g., 'command -v tool || echo "not found"') rather than only listing detection questions and decisions.

Consolidate the Step 5 checklist with the Step 7 scorecard so validation criteria appear in one place, reducing token cost.

DimensionReasoningScore

Conciseness

The body is mostly efficient—decision tables and reference pointers avoid over-explaining basics—but the illustrative scorecard tables in Steps 6-7 and the duplicated checklist content add some padding that could be trimmed.

4 / 5

Actionability

Provides concrete commands ('command -v tool', 'tool auth status'), specific defaults tables, decision tables, and skill_manage action examples, but some steps remain high-level process guidance rather than fully copy-paste-ready instruction.

4 / 5

Workflow Clarity

A clear 8-step sequence with upfront mode routing, pass/fail gates, an explicit validation checklist in Step 5, and a 'fix before delivery' feedback loop, all well sequenced.

5 / 5

Progressive Disclosure

SKILL.md is an overview pointing to six one-level-deep reference files, all signaled with backtick paths and summarized in a closing Reference Files section; all referenced files exist.

5 / 5

Total

18

/

20

Passed

Description

100%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 strong, comprehensive description that clearly states capabilities, provides an exhaustive and natural trigger list with sideways entry points, and stays in third-person voice. Distinctiveness is high given the specific domain.

DimensionReasoningScore

Specificity

Lists multiple concrete actions—'Create new skills, modify and improve existing skills, and measure skill performance'—plus eval, benchmarking with variance analysis, and quality iteration, giving comprehensive coverage rather than vague abstraction.

5 / 5

Completeness

Explicitly answers both what (create/modify/measure skills) and when via a clear 'Use when users want...' clause plus 'Also triggers when...', with concrete trigger phrases throughout.

5 / 5

Trigger Term Quality

Includes 20+ natural user phrases ('create a skill', 'make a new skill', 'build a skill for', 'scaffold a skill', 'improve this skill') plus synonyms and sideways entry points like 'I keep doing X manually' and 'turn this into a skill'.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (the skill lifecycle) with highly specific triggers; third-person voice and domain-unique phrasing minimize overlap with general coding skills.

5 / 5

Total

20

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
himself65/finance-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.