CtrlK
BlogDocsLog inGet started
Tessl Logo

statusline-generator

Configures and customizes Claude Code statuslines with multi-line layouts, cost tracking via ccusage, git status indicators, and customizable colors. Activates for statusline setup, installation, configuration, customization, color changes, cost display, git status integration, or troubleshooting statusline issues.

Install with Tessl CLI

npx tessl i github:fernandezbaptiste/claude-code-skills --skill statusline-generator
What are skills?

94

Does it follow best practices?

Validation for skill structure

SKILL.md
Review
Evals

Discovery

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a well-crafted skill description that excels across all dimensions. It provides specific capabilities, includes natural trigger terms users would actually say, explicitly states both what it does and when to use it, and occupies a clear niche that won't conflict with other skills. The use of third person voice and the 'Activates for' clause demonstrate best practices.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'multi-line layouts, cost tracking via ccusage, git status indicators, and customizable colors' - these are concrete, actionable capabilities.

3 / 3

Completeness

Clearly answers both what ('Configures and customizes Claude Code statuslines with multi-line layouts, cost tracking...') AND when ('Activates for statusline setup, installation, configuration...'). The 'Activates for' clause serves as explicit trigger guidance.

3 / 3

Trigger Term Quality

Excellent coverage of natural terms: 'statusline setup, installation, configuration, customization, color changes, cost display, git status integration, troubleshooting' - these are terms users would naturally use when seeking this functionality.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with specific niche: 'Claude Code statuslines' combined with specific features like 'ccusage' and 'git status indicators' creates a clear, unique domain unlikely to conflict with other skills.

3 / 3

Total

12

/

12

Passed

Implementation

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-structured skill with excellent actionability and clear workflows. The main weakness is some verbosity in explanatory sections that could be trimmed - Claude doesn't need explanations of why multi-line layouts are beneficial or what path shortening means. The progressive disclosure and reference structure are exemplary.

Suggestions

Remove the 'Benefits' subsection under Multi-Line Layout - Claude can infer these advantages

Trim the 'When to Use This Skill' section as this duplicates frontmatter activation triggers

Condense feature descriptions (e.g., 'Paths are shortened: Home directory replaced with ~' can just show the example)

DimensionReasoningScore

Conciseness

The content is mostly efficient but includes some unnecessary explanation like the 'Benefits' section explaining why multi-line layouts are good, and verbose descriptions of features Claude could infer. The overview section restates what's already clear from the skill description.

2 / 3

Actionability

Provides fully executable bash commands, complete code examples for customization, and copy-paste ready snippets. The installation steps, color modification examples, and troubleshooting commands are all concrete and actionable.

3 / 3

Workflow Clarity

Clear numbered sequences for installation (both automated and manual), explicit validation steps in troubleshooting (check commands like 'which ccusage', 'ls -lh'), and logical progression from quick start to customization to troubleshooting.

3 / 3

Progressive Disclosure

Well-structured with quick start upfront, detailed features in middle sections, and clear one-level-deep references to external files (color_codes.md, ccusage_integration.md). Navigation is clear with descriptive section headers.

3 / 3

Total

11

/

12

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

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.