Tessl • The management layer for AI agent skills

SkillPublic

skill-creator

Create new skills following the GBrain conformance standard. Generates SKILL.md with frontmatter, Contract, Phases, Output Format, and Anti-Patterns. Checks MECE against existing skills. Updates manifest and resolver.

Quality

80%

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 ./skills/skill-creator/SKILL.md

Quality

Content

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

The content is a strong, self-contained skill: lean, well-sequenced, with an explicit verification step and error-recovery guidance. The only notable gaps are the unspecified formats for manifest.json and RESOLVER.md entries and a template that could live in a separate reference file.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient: terse numbered phases, a copy-paste template, and failure guidance with no explanations of concepts Claude already knows. Every section (Contract, Phases, Output Format, When it fails, Anti-Patterns) earns its place, matching anchor 5.	5 / 5
Actionability	The skill provides a complete copy-paste SKILL.md template and concrete commands ('bun test test/skills-conformance.test.ts'), which is mostly executable guidance. It is not anchor 5 because the manifest.json and RESOLVER.md update steps never show what a valid entry or routing row looks like, leaving a minor gap.	4 / 5
Workflow Clarity	Six phases are clearly sequenced with an explicit validation phase ('Verify. Run bun test test/skills-conformance.test.ts') and feedback loops for error recovery in 'When it fails' (test fails → add missing section → re-run; unreachable → add RESOLVER row → re-run). This matches anchor 5's explicit validation and recovery loops.	5 / 5
Progressive Disclosure	The body is well-organized into clear sections with no external bundle files (references/, scripts/, assets/ are absent), and the inline 36-line template is arguably appropriate. It is not anchor 5 because at roughly 77 lines it exceeds the under-50-line simple-skill exception, and the template could be split into a separate reference file to keep SKILL.md a leaner overview.	4 / 5
	Total	18 / 20 Passed

Description

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

The description is specific and action-oriented with a clear niche, but omits any 'when to use' guidance, which caps its completeness. It also leans on project-internal jargon (MECE, GBrain, resolver) that a user would not naturally say when triggering the skill.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to create a new skill or add a capability not covered by an existing skill', to raise completeness above 3.

Briefly unpack or replace internal jargon ('MECE', 'GBrain conformance standard', 'resolver') with plain-language equivalents so trigger matching does not depend on project terminology.

Include natural trigger variations such as 'add a skill', 'make a skill', or 'skill template' alongside 'create new skills' for broader keyword coverage.

Dimension	Reasoning	Score
Specificity	The description lists several concrete actions ('Generates SKILL.md with frontmatter, Contract, Phases, Output Format, and Anti-Patterns. Checks MECE against existing skills. Updates manifest and resolver.') but not comprehensive coverage. It falls short of anchor 5 because unexplained jargon ('GBrain conformance standard', 'MECE', 'resolver') leaves minor gaps and the conformance-test step is not mentioned.	4 / 5
Completeness	The 'what' is clearly and concretely answered, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not 2 because the 'what' is specific and multi-part, and not 4 because 'when' is entirely absent rather than merely imprecise.	3 / 5
Trigger Term Quality	'Create new skills' is a natural phrase a user would say when needing this skill, giving good keyword coverage. It is not anchor 5 because common variations like 'add a skill', 'make a skill', or 'skill template' are missing.	4 / 5
Distinctiveness Conflict Risk	Skill authoring for the GBrain conformance standard is a clear niche with distinct triggers, giving minimal conflict risk with most skills. It is not 5 because the domain of 'improve/create skills' could overlap with a closely related skill-editing or skill-improvement skill.	4 / 5
	Total	15 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 2 suspicious	Warning

	Total	14 / 16 Passed

Repository: garrytan/gbrain
Path: skills/skill-creator/SKILL.md
Revision: c3e8fd2

Reviewed: 25 days ago

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.

skill-creator

Table of Contents

Is this your skill?