CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

60

Quality

70%

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

Quality

Content

75%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 body is a tight, well-structured workflow with a concrete template and verification step, assuming Claude's competence throughout. Its main weakness is the absence of an explicit failure-recovery feedback loop around the conformance test.

Suggestions

Add an explicit feedback loop after phase 6: if the conformance test fails, review the errors, fix the SKILL.md/manifest/resolver, and re-run until it passes.

Show the exact manifest.json entry shape (a small JSON snippet) so the manifest-update step is unambiguous.

Consider extracting the SKILL.md template into a references file so the Phases section stays scannable, with a one-level-deep pointer to it.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no padding about what skills or MECE are — with only minor redundancy where the Anti-Patterns restate the MECE overlap point.

4 / 5

Actionability

Provides a concrete copy-paste SKILL.md template and a specific verification command (`bun test test/skills-conformance.test.ts`) plus named target files, with a minor gap in not showing the exact manifest.json entry shape to add.

4 / 5

Workflow Clarity

Six phases are clearly sequenced with a verification checkpoint in phase 6, but there is no explicit feedback loop (test fails → review errors → fix → re-run) for this mutating skill.

4 / 5

Progressive Disclosure

Self-contained with no bundle files and well-organized into Contract, Phases, Output Format, and Anti-Patterns sections; the sizable inline template is the kind of content that could optionally live in a reference, but inline placement is defensible.

4 / 5

Total

16

/

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 clearly states what the skill does with several concrete actions, but omits any explicit 'when to use it' guidance, which limits its completeness and trigger clarity. Trigger terms are natural but could be broadened with synonyms.

Suggestions

Add an explicit 'Use when...' clause naming the trigger situations (e.g., 'Use when the user asks to create a new skill, extend skill coverage, or conform a skill to the GBrain standard').

Include running the conformance test as a stated action so the description reflects the full workflow.

Broaden trigger coverage with synonyms like 'build a skill' or 'set up a skill' alongside 'create' and 'new'.

DimensionReasoningScore

Specificity

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' — with only a minor gap (the conformance test step from the body is not surfaced in the description).

4 / 5

Completeness

The 'what' is clear and detailed, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

'Create new skills' maps naturally to the 'create a skill' / 'new skill' trigger phrases users would say, though synonyms like 'build' or 'make a skill' are absent.

4 / 5

Distinctiveness Conflict Risk

The 'GBrain conformance standard' framing carves a distinct skill-creation niche, though the 'improve this skill' trigger carries minor overlap risk with general improvement skills.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
garrytan/gbrain
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.