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, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

60

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/sdlc/skills/skill-creator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a comprehensive, well-structured skill for creating and iterating on skills, with strong actionability through concrete commands, JSON schemas, and clear workflow sequencing. Its main weakness is verbosity — conversational asides, repeated emphasis of the core loop (stated 3 times), tone-setting paragraphs, and explanations of concepts Claude already knows inflate the token cost significantly. The workflow is well-designed with good validation checkpoints but the skill would benefit from aggressive trimming to respect its own 500-line recommendation.

Suggestions

Remove conversational padding ('Cool? Cool.', the plumber/grandparent paragraph, 'This task is pretty important...billions a year') and the repeated restatements of the core loop — state it once clearly at the top.

Move the Claude.ai-specific and Cowork-specific sections into separate reference files (e.g., references/claude-ai-adaptation.md, references/cowork-adaptation.md) to reduce SKILL.md length and follow the skill's own progressive disclosure guidance.

Cut explanations of concepts Claude already knows (e.g., what JSON fields are, how subagents work conceptually) and trust Claude's intelligence per the skill's own writing advice.

DimensionReasoningScore

Conciseness

The skill is significantly verbose, with extensive conversational asides ('Cool? Cool.'), repeated emphasis blocks restating the core loop multiple times, lengthy explanations of concepts Claude already understands (what JSON is, how subagents work), and casual padding throughout. The tone-setting paragraphs about plumbers and grandparents, while charming, consume tokens without adding actionable value.

2 / 5

Actionability

The skill provides concrete commands (python -m scripts.aggregate_benchmark, generate_review.py invocations), specific JSON schemas, exact file structures, and executable bash snippets. Minor gaps exist — some steps like 'grade inline' are vague, and the grading process could use more concrete examples — but overall the guidance is highly actionable and copy-paste ready.

4 / 5

Workflow Clarity

The multi-step workflow is clearly sequenced (capture intent → write skill → run tests → grade → aggregate → launch viewer → read feedback → iterate), with explicit validation checkpoints (user review via viewer, assertion grading, benchmark analysis). Minor gaps: the transition between 'Step 2: draft assertions' and 'Step 3: capture timing' could be clearer about concurrency, and error recovery paths are mostly implicit rather than explicit.

4 / 5

Progressive Disclosure

The skill references external files appropriately (agents/grader.md, agents/comparator.md, agents/analyzer.md, references/schemas.md) with clear guidance on when to read them. The three-level loading system is well-explained. However, the SKILL.md itself is very long (well over 500 lines by its own recommendation), and some sections like the Claude.ai and Cowork adaptations could potentially be split into separate reference files. Without bundle files provided, it's hard to fully verify reference accuracy.

4 / 5

Total

14

/

20

Passed

Description

83%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.

This is a strong description that clearly communicates both what the skill does and when to use it, with an explicit 'Use when...' clause covering multiple trigger scenarios. The specificity is good with several concrete actions listed, though it could benefit from a few more natural trigger terms and synonyms. Overall, it would perform well in a multi-skill selection scenario.

DimensionReasoningScore

Specificity

Lists several specific actions: create skills, modify/improve existing skills, measure performance, run evals, benchmark with variance analysis, optimize descriptions for triggering accuracy. Minor gaps exist—e.g., it doesn't specify what 'skills' are or mention file formats—but the actions are concrete and varied.

4 / 5

Completeness

Clearly answers both 'what' (create, modify, improve, measure skill performance) and 'when' with an explicit 'Use when...' clause listing concrete trigger scenarios: creating from scratch, editing, optimizing, running evals, benchmarking with variance analysis, and optimizing descriptions.

5 / 5

Trigger Term Quality

Includes good natural keywords like 'create a skill', 'edit', 'optimize', 'evals', 'benchmark', 'skill performance', 'triggering accuracy', and 'description'. Missing some synonyms users might say like 'write a skill', 'test a skill', 'skill.md', 'tune', or 'prompt engineering'.

4 / 5

Distinctiveness Conflict Risk

The focus on 'skills' as a specific concept (skill creation, skill evals, skill description optimization) is fairly distinctive. Minor overlap risk exists with general coding/editing skills or evaluation-related skills, but the repeated use of 'skill' as a domain-specific term helps differentiate it.

4 / 5

Total

17

/

20

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (507 lines); consider splitting into references/ and linking

Warning

Total

10

/

11

Passed

Repository
whimzyLive/nightshift-ai
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.