skill-builder

Helps you scaffold new Tessl skills with best practices and proper structure

Quality

33%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./examples/skill-builder/SKILL.md

Quality

Content

35%Scale 1-3

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

This skill provides a reasonable high-level workflow for creating Tessl skills but lacks the concrete, executable guidance needed for actionability. It describes what to generate without showing actual templates, schemas, or examples. The process is clear but would benefit from validation steps and concrete output examples.

Suggestions

Add concrete templates for SKILL.md and tile.json with actual YAML/JSON examples that can be copy-pasted and modified

Include a complete example of generated output (not just 'see this skill') showing a sample skill with all three output files

Add validation checkpoints: 'Verify the generated SKILL.md has required frontmatter fields' with specific checks

Provide a JSON schema or concrete structure for the eval scenarios rather than just describing what they should test

Dimension	Reasoning	Score
Conciseness	The skill is reasonably efficient but includes some unnecessary explanation (e.g., 'This skill helps you create new Tessl skills' is redundant with the description). The process steps could be more compact.	2 / 3
Actionability	The skill describes what to do abstractly ('Generate a properly formatted skill file') but provides no concrete code, templates, or executable examples. The 'Example Output' section just says 'See this skill itself' which is circular and unhelpful.	1 / 3
Workflow Clarity	Steps are clearly numbered and sequenced, but there are no validation checkpoints or feedback loops. No guidance on what to do if generated output is invalid or if user answers are unclear.	2 / 3
Progressive Disclosure	Content is reasonably organized with clear sections, but everything is inline. References to output files (tile.json, scenarios.json) mention formats but don't link to templates or examples that could be in separate files.	2 / 3
	Total	7 / 12 Passed

Description

32%Scale 1-3

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 identifies a specific domain (Tessl skills) but is too brief and lacks explicit trigger guidance. It uses second person voice ('Helps you') which violates the third-person requirement, and the vague phrases 'best practices and proper structure' don't convey concrete capabilities.

Suggestions

Add a 'Use when...' clause with trigger terms like 'create skill', 'new skill', 'skill template', 'generate skill file', or 'skill.md'

Rewrite in third person voice: 'Scaffolds new Tessl skills...' instead of 'Helps you scaffold...'

Specify concrete actions: what files are created, what structure is generated, what best practices are applied (e.g., 'Creates skill.md files with YAML frontmatter, description fields, and instruction sections')

Dimension	Reasoning	Score
Specificity	Names the domain ('Tessl skills') and one action ('scaffold'), but lacks comprehensive detail about what scaffolding entails or what 'best practices and proper structure' specifically means.	2 / 3
Completeness	Describes what it does (scaffolds skills) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Contains relevant keywords like 'scaffold', 'Tessl skills', and 'structure', but misses common variations users might say like 'create skill', 'new skill', 'skill template', or 'generate skill'.	2 / 3
Distinctiveness Conflict Risk	'Tessl skills' is fairly specific and unlikely to conflict with generic scaffolding tools, but without explicit triggers it could still overlap with general code generation or template skills.	2 / 3
	Total	7 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: ekipo-user/agent-onboarding
Path: examples/skill-builder/SKILL.md
Commit: 9d0fa00

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.