CtrlK
BlogDocsLog inGet started
Tessl Logo

create-skill

Use when creating a new skill, writing a skill from scratch, or converting a process into a reusable skill — enforces TDD, empirical validation, and quality monitoring

80

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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 tight, well-sequenced TDD workflow with concrete commands, explicit validation gates, and clear error-recovery loops. It respects Claude's intelligence while providing copy-paste-ready guidance.

DimensionReasoningScore

Conciseness

Lean imperative prose that assumes Claude's competence; it never explains what skills or agents are, and each line (gates, rationalization table, step constraints) earns its tokens.

3 / 3

Actionability

Concrete, executable guidance throughout — named commands (tessl review run, tessl whoami, determinize-skill), exact thresholds (>=85%, --threshold 85), and specific file paths rather than vague direction.

3 / 3

Workflow Clarity

A Mermaid flowchart plus numbered steps with explicit validation checkpoints (RED baseline -> GREEN verify -> REFACTOR loop -> quality gates table) provide clear sequencing and feedback loops for error recovery.

3 / 3

Progressive Disclosure

A single self-contained SKILL.md with no bundle files, well-organized into sections (Process, Step Details, Quality Gates, Rationalizations, Common Mistakes) and no nested references, satisfying the well-organized-structure anchor.

3 / 3

Total

12

/

12

Passed

Description

100%

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 is concise, uses third person, and clearly states both capabilities and explicit trigger conditions. It is specific, distinctive, and free of vague fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "creating a new skill, writing a skill from scratch, or converting a process into a reusable skill — enforces TDD, empirical validation, and quality monitoring" — matching the anchor for naming several specific actions.

3 / 3

Completeness

Explicitly answers both what it does and when to use it via the "Use when..." trigger clause plus the concrete capabilities, satisfying the top anchor.

3 / 3

Trigger Term Quality

Natural user phrasing is well covered ("create a new skill", "writing a skill", "convert a process into a reusable skill"), terms a user would actually say, not jargon.

3 / 3

Distinctiveness Conflict Risk

The skill-creation/TDD/empirical-validation niche is distinct and unlikely to trigger for unrelated skills, matching the clear-niche anchor.

3 / 3

Total

12

/

12

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
AndreJorgeLopes/proof-of-skill
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.