CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

customizing-statusline

Creates, edits, and migrates Letta Code statusline mods. Use when handling the /statusline command or continuing work started by /statusline.

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 well-structured, token-efficient overview that routes API details, examples, and migration guidance to real, clearly-labeled one-level-deep reference files, with a concrete sequenced workflow and specific product constraints. The main gaps are the absence of an inline minimal code example and an explicit post-edit validation step.

DimensionReasoningScore

Conciseness

The body is lean and imperative ("Do not shell, fetch, await, or read files inside render") with a compact 4-line precedence model; every section conveys product-specific facts Claude would not know (order: 0, ownership model, `row`/`columns` helpers) rather than general concepts. Nothing is padded or over-explained, matching the level-5 anchor.

5 / 5

Actionability

Guidance is concrete throughout — exact file path, specific API names (`row`/`columns`, `chalk`, `panel.update()`, `letta.capabilities.ui.panels`, disposer calling `panel.close()`), and explicit routing to `references/examples.md` for patterns — matching level 4's "mostly executable guidance with minor gaps". Not level 5 because no copy-paste code example appears in the body itself; the executable examples are deferred to the reference file.

4 / 5

Workflow Clarity

The 9-step workflow is clearly sequenced with conditional branches (read-and-preserve if the file exists, synthesize if not) and a closing report step ("Summarize the absolute file path changed and tell the user to run `/reload`"), matching level 4. Not level 5 because there is no explicit validation checkpoint that the edited mod loads or renders correctly.

4 / 5

Progressive Disclosure

The body is a concise overview and all three bundle files (`references/api.md`, `references/examples.md`, `references/migration.md`) exist, are referenced exactly one level deep, are conditionally routed in the workflow, and are listed with one-line descriptions in "Useful references" — matching the level-5 anchor of a clear overview with well-signaled one-level-deep references.

5 / 5

Total

18

/

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.

The description is a strong example: it pairs three concrete capability verbs with an explicit, trigger-phrase-rich 'Use when' clause scoped to a well-defined niche. The only improvements would be adding synonyms like "status line" or "shell prompt" for broader trigger coverage and slightly fuller action enumeration.

DimensionReasoningScore

Specificity

"Creates, edits, and migrates" lists three concrete actions on a specific object, matching the level-4 anchor of several specific actions with minor coverage gaps (e.g., shell-prompt/PS1 matching is only implied by the generic "migrates"). Not level 5 because coverage of statusline-related tasks is not comprehensive, and not level 3 because three distinct concrete actions are named rather than 1-2.

4 / 5

Completeness

"Creates, edits, and migrates Letta Code statusline mods" clearly states what the skill does, and "Use when handling the /statusline command or continuing work started by /statusline" gives an explicit when-clause with concrete trigger phrases, matching the level-5 anchor exactly.

5 / 5

Trigger Term Quality

"statusline mods" and "/statusline command" cover the primary natural triggers in both slash-command and prose forms, matching level 4's "good keyword coverage; a few natural terms missing". Not level 5 because common synonyms like "status line" (two words), "prompt", or "PS1" are absent.

4 / 5

Distinctiveness Conflict Risk

"Letta Code statusline mods" and the "/statusline" command form a clear niche with distinct, unambiguous triggers and minimal conflict risk with other skills, matching the level-5 anchor.

5 / 5

Total

18

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

letta-ai/letta-code

Path

src/skills/builtin/customizing-statusline/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.