CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

creating-mods

Creates and edits trusted local Letta Code mods, including tools, slash commands, local-only model providers, lifecycle/turn events, scoped conversation helpers, panels, and capability-gated behavior. Use when asked to make a mod, add an agent-callable tool, add a slash command, add a local provider/model adapter, transform turns, react to app events, or add lightweight mod UI outside the dedicated /statusline flow.

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

92%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-structured overview skill: executable core patterns, a validated 9-step workflow with review and recovery, and clean one-level reference navigation with all bundle files present. The main improvement opportunity is removing repetition — the capability-guarding rule, the project-mods prohibition, and the reference list each appear twice.

Suggestions

State the guard-on-every-dependent-capability rule once (the capabilities section) and reference it from the checklist instead of repeating it in the intro and twice in the checklist.

Collapse the duplicate reference listings: keep the References table with its "Load when" conditions and have Workflow step 4 point to it rather than re-enumerating all eight recipe files.

DimensionReasoningScore

Conciseness

The body is dense with decision tables, rules, and code rather than explanations of known concepts, but the guard-on-every-capability rule is stated three times (intro, capabilities section, checklist), "Do not create project mods" appears twice, and the reference list is duplicated between Workflow step 4 and the References table. This is trimmable redundancy rather than meaningful over-explanation, matching anchor 4.

4 / 5

Actionability

Provides an executable activate/disposer skeleton, exact capability flags, concrete scoped API calls (ctx.conversation.getHistory/fork), the diagnostics call signature, exact file paths, and copy-paste recovery commands ("/reload", "letta --no-mods", "LETTA_DISABLE_MODS=1 letta"). The elided register() arguments are deliberate delegation to per-recipe references, not a gap, so the common case is fully covered.

5 / 5

Workflow Clarity

The 9-step workflow is clearly sequenced with an explicit review step enumerating concrete checks (valid names, descriptions present, object schemas, capability guards, scoped APIs, cleanup), a recovery path for broken startup, and a pre-flight checklist for complex mods — matching the anchor-5 pattern of validation steps, feedback loops, and checklists.

5 / 5

Progressive Disclosure

All nine referenced files (tools, commands, providers, events, permissions, ui, plan-mode, analysis-mode, architecture) exist, are one level deep, and are navigated by two "Load when" tables keyed to user intent; reference files only cross-link siblings rather than nesting. Inline content (core shape, capabilities, scoped API) is appropriately overview-level.

5 / 5

Total

19

/

20

Passed

Description

92%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 description: concrete capability enumeration, explicit third-person "Use when" triggers, and a clear niche with an explicit statusline exclusion. The only gap is that a few capabilities the skill handles (permission overlays, status values, editing existing mods) lack corresponding trigger phrases.

Suggestions

Add a trigger phrase for permission overlays (e.g., "enforce a tool allow/ask/deny policy") and for status values, since the body covers both but the Use-when clause does not.

Include an update path in the triggers (e.g., "or update an existing mod") since the description says it edits mods but the Use-when clause only covers creation-style asks.

DimensionReasoningScore

Specificity

Enumerates concrete capability types — "tools, slash commands, local-only model providers, lifecycle/turn events, scoped conversation helpers, panels, and capability-gated behavior" — giving comprehensive, specific coverage of the mod surface rather than vague claims.

5 / 5

Completeness

Explicitly answers "what" (creates and edits mods with an enumerated capability list) and "when" ("Use when asked to make a mod, add an agent-callable tool, ..." with concrete trigger phrases), exactly matching the anchor-5 pattern.

5 / 5

Trigger Term Quality

Natural trigger phrases like "make a mod", "add an agent-callable tool", "add a slash command", and "transform turns" are present, but permission overlays, status values, and updating an existing mod — all covered by the skill body — have no trigger phrase. This is good-but-not-comprehensive keyword coverage, matching anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

"Trusted local Letta Code mods" carves out a clear niche, and "outside the dedicated /statusline flow" explicitly disambiguates from the statusline skill, leaving minimal conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

letta-ai/letta-code

Path

src/skills/builtin/creating-mods/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.