CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-builder-generic

Universal guide for creating production-ready Claude Code skills for any project. Includes 6-step workflow (understand, plan, initialize, edit, package, iterate), progressive disclosure design, YAML frontmatter templates, validation scripts, reference organization patterns, and 10 community-proven innovations. Use when creating new Claude Code skills, converting documentation to skills, improving existing skills, or learning skill development best practices for any domain.

63

Quality

77%

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 ./.claude/skills/skill-builder-generic/SKILL.md

The canonical home for this skill is skill-builder-generic in fernandezbaptiste/Skrillz

SKILL.md
Quality
Evals
Security

Quality

Content

67%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-organized, actionable meta-skill with a clear sequenced workflow, concrete code, and strong progressive disclosure via real reference and script bundles. Its main weakness is conceptual padding in the opening philosophy sections that adds tokens without teaching Claude anything new.

Suggestions

Trim the 'Philosophy & Overview' section ('What Are Claude Code Skills?', 'Why Skills Matter', 'When to Create Skills') to a few lines or move it to a reference, since Claude already knows what skills are.

Move the detailed '4 Organizational Patterns' and '10 Community Innovations' sections into references/ and replace them with brief summaries plus links, reducing body length further.

Either create the referenced 'templates/' directory with the 5 promised template files or remove references to it in 'Next Steps' to avoid a broken bundle path.

DimensionReasoningScore

Conciseness

The body is mostly efficient with substantial actionable content, but opens with conceptual padding Claude already knows ('What Are Claude Code Skills?', 'Why Skills Matter', 'When to Create Skills') and the '10 Community Innovations' section is abstractly padded.

3 / 5

Actionability

Provides concrete, executable guidance (mkdir/heredoc bash, python script invocations, markdown SKILL.md templates, validation commands) with only minor placeholder gaps in template examples.

4 / 5

Workflow Clarity

The 6-step process (Understand → Plan → Initialize → Edit → Package & Validate → Iterate) is clearly sequenced with a validation checklist in Step 5 and a feedback loop in Step 6; minor checkpoint gaps keep it below 5.

4 / 5

Progressive Disclosure

Lean ~3,200-word body with 8 real, clearly-signaled one-level-deep references and 4 bundled scripts; minor gaps include long inlined sections (organizational patterns, community innovations) and a referenced 'templates/' directory that does not exist.

4 / 5

Total

15

/

20

Passed

Description

87%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, well-structured description that clearly states what the skill does, enumerates concrete features, and provides an explicit 'Use when' clause with natural trigger phrases. It is distinctive within the skill ecosystem.

DimensionReasoningScore

Specificity

Lists several specific concrete capabilities ('6-step workflow', 'progressive disclosure design', 'YAML frontmatter templates', 'validation scripts', 'reference organization patterns', '10 community-proven innovations') rather than vague language, with only minor gaps in coverage.

4 / 5

Completeness

Explicitly answers both 'what' (universal guide for creating production-ready skills with named features) and 'when' via a concrete 'Use when creating new Claude Code skills, converting documentation to skills, improving existing skills, or learning skill development best practices for any domain' clause.

5 / 5

Trigger Term Quality

Includes natural phrases a user would say ('creating new Claude Code skills', 'converting documentation to skills', 'improving existing skills', 'learning skill development best practices'); good keyword coverage though a few synonyms are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (meta-skill for building Claude Code skills) with distinct, specific triggers that are unlikely to conflict with domain skills.

5 / 5

Total

18

/

20

Passed

Validation

75%

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

Validation12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

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

Warning

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

relative_links

Relative link issues: 5 missing

Warning

referenced_paths_exist

Referenced path issues: 7 missing

Warning

Total

12

/

16

Passed

Repository
fernandezbaptiste/Skrillz
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.