CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

creating-skills

Guide for creating effective skills. Use when creating a new skill or updating an existing one that extends Letta Code's capabilities with specialized knowledge, workflows, or tool integrations, whether a user asks for it or a reusable workflow is worth capturing.

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 ./src/skills/builtin/creating-skills/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 delivers a well-sequenced, highly actionable skill-creation workflow with real validation checkpoints and properly structured one-level-deep references. Its main weakness is token efficiency: overlapping sections and analogies add length without adding guidance.

Suggestions

Merge the 'Anatomy of a Skill' directory tree with the per-directory subsections and consolidate the progressive-disclosure guidance that currently appears in both the dedicated section and Step 4.

Cut illustrative analogies (e.g., the narrow-bridge/open-field metaphor) and other explanations of what the agent already knows.

Either reference scripts/validate-skill.ts in the body (e.g., as a pre-packaging validation step) or remove it, and consider moving the commit-message convention section to a reference file to shorten the body.

DimensionReasoningScore

Conciseness

The body is mostly efficient but includes repetition (the directory tree in 'Anatomy of a Skill' restates the per-directory sections; progressive-disclosure guidance appears in both the 'Progressive Disclosure' section and Step 4 guidelines) and padded analogies like "a narrow bridge with cliffs needs specific guardrails". Not level 4 because several sections could be merged or trimmed without losing information.

3 / 5

Actionability

Fully executable commands are provided for initialization and packaging (npx tsx <SKILL_DIR>/scripts/init-skill.ts ...), with <SKILL_DIR> resolution explained, plus a concrete YAML frontmatter example, worked analysis examples (editing-pdfs, building-frontend-apps, querying-bigquery), and a copy-paste commit message template. Matches the anchor for copy-paste ready commands covering the common cases.

5 / 5

Workflow Clarity

The six-step creation process is explicitly ordered ("Follow these steps in order, skipping only if...") with per-step skip conditions, and validation is built in: the packaging script auto-validates with a fix-and-rerun loop, scripts "must be tested by actually running them", and the iterate step closes the feedback loop. Matches the anchor for clear sequence with explicit validation and error recovery.

5 / 5

Progressive Disclosure

References are one level deep, clearly signaled from the body ("See references/workflows.md for sequential workflows..."), and both files exist with content matching their stated purpose. Not level 5 because scripts/validate-skill.ts is bundled but never referenced in the body, and the 388-line body nears its own 500-line limit with content (e.g., the full commit-message convention) that could move to a reference file.

4 / 5

Total

17

/

20

Passed

Description

65%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 has an explicit and well-constructed 'Use when' trigger clause covering creation and updates, but the capability statement is generic. It reads as a domain label rather than a summary of what the skill provides.

Suggestions

Replace the generic "Guide for creating effective skills" with the concrete capabilities the skill provides, e.g., "Provides principles, an init script, and a packaging workflow for building skills..."

Add natural trigger keywords users would actually say, such as "SKILL.md", "make a skill", or "package a skill".

State what the guidance covers (design principles, progressive disclosure, bundled scripts) so the 'what' half is as strong as the 'when' half.

DimensionReasoningScore

Specificity

The only stated action is the generic "Guide for creating effective skills"; the extension clause ("extends Letta Code's capabilities with specialized knowledge, workflows, or tool integrations") describes skills in general, not what this skill concretely provides (e.g., init script, packaging, design guidance). This matches the anchor 'Names the domain but actions are minimal or generic' rather than level 3, which requires 1-2 concrete listed actions.

2 / 5

Completeness

Both halves are present: a what ("Guide for creating effective skills") and an explicit when ("Use when creating a new skill or updating an existing one..."). Not level 5 because the 'what' is thin — it never states what guidance or capabilities the skill actually delivers.

4 / 5

Trigger Term Quality

"creating a new skill", "updating an existing one", "workflows", and "tool integrations" are natural phrases a user would say. Not level 5 because common variations like "SKILL.md", "make/author a skill", or "package a skill" are missing.

4 / 5

Distinctiveness Conflict Risk

The skill-creation niche has distinct triggers and minimal conflict risk. Not level 5 because phrases like "specialized knowledge, workflows, or tool integrations" are broad and could weakly overlap with general workflow/documentation skills.

4 / 5

Total

14

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

relative_links

Relative link issues: 6 missing

Warning

referenced_paths_exist

Referenced path issues: 12 missing

Warning

Total

14

/

16

Passed

Repository

letta-ai/letta-code

Path

src/skills/builtin/creating-skills/SKILL.md

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.