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.

2.91x

Quality

86%

Does it follow best practices?

Impact

99%

2.91x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

72%

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 strong actionability and good progressive disclosure. The main weaknesses are moderate verbosity (some sections explain things Claude doesn't need explained, like the benefits of multi-line layouts) and missing validation checkpoints in the installation workflow. The troubleshooting section is practical and well-organized.

Suggestions

Add a validation step after installation (e.g., 'Verify: restart Claude Code and confirm the 3-line statusline appears') to improve workflow clarity.

Trim the 'When to Use This Skill' section and the 'Benefits' list under Multi-Line Layout — these explain things Claude can infer and consume tokens without adding actionable value.

Move the full color scheme listing (all ANSI codes) to references/color_codes.md since it's already referenced there, keeping only 1-2 examples inline.

Dimension	Reasoning	Score
Conciseness	The skill includes some unnecessary explanation (e.g., 'Benefits' list for multi-line layout, 'When to Use This Skill' section that restates the description). The color scheme section listing all ANSI codes inline could be trimmed since it references color_codes.md. However, most content is reasonably efficient.	2 / 3
Actionability	Provides concrete, executable bash commands and code snippets throughout — installation steps, specific printf modifications for color changes and layout conversion, troubleshooting commands like `which ccusage` and `ls -lh /tmp/claude_cost_cache_*.txt`. Examples are copy-paste ready with real ANSI codes.	3 / 3
Workflow Clarity	Installation steps are clearly sequenced, but there are no validation checkpoints — no step to verify the statusline is working after installation, no verification that settings.json was correctly updated, and no feedback loop for the manual installation process. For a skill that modifies config files, validation steps would be important.	2 / 3
Progressive Disclosure	Excellent structure with a Quick Start section followed by detailed features, customization, and troubleshooting. References to external files (color_codes.md, ccusage_integration.md) are clearly signaled and one level deep. The Resources section at the end provides a clean directory of supporting files.	3 / 3
	Total	10 / 12 Passed

Description

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 strong description that clearly defines a narrow domain (Claude Code statusline configuration), lists specific capabilities, and provides explicit activation triggers. It uses proper third-person voice and covers both what the skill does and when it should be used. The trigger terms are natural and comprehensive.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: configuring multi-line layouts, cost tracking via ccusage, git status indicators, and customizable colors. These are detailed, actionable capabilities.	3 / 3
Completeness	Clearly answers both 'what' (configures statuslines with multi-line layouts, cost tracking, git status, colors) and 'when' with explicit triggers ('Activates for statusline setup, installation, configuration, customization, color changes, cost display, git status integration, or troubleshooting').	3 / 3
Trigger Term Quality	Includes strong natural trigger terms users would say: 'statusline', 'cost tracking', 'ccusage', 'git status', 'color changes', 'customization', 'troubleshooting statusline issues'. Good coverage of variations.	3 / 3
Distinctiveness Conflict Risk	Very specific niche — Claude Code statusline configuration is a narrow, well-defined domain. Terms like 'statusline', 'ccusage', and 'multi-line layouts' are highly distinctive and unlikely to conflict with other skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: fernandezbaptiste/claude-code-skills
Commit: 4f0eae8

Reviewed: 4 months ago

Table of Contents

Discovery Implementation Validation

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.