statusline-creator

Builds a Claude Code statusline from scratch or extends an existing one. A statusline is a live status bar that runs a shell script after every Claude response and displays data — security scans, git status, API quotas, build state — directly in the session. Use this skill when the user says "create a statusline", "make a statusline for X", "add X to my statusline", "show Y in the status bar", "build a statusline plugin", or "I want live data in my Claude session". Trigger even if the user just describes wanting live feedback during a Claude session without naming "statusline" explicitly. The skill drives from idea to a working, installed, tested statusline without requiring the user to direct every step.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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, highly actionable skill body with a clear multi-step workflow, explicit validation checkpoints, and clean progressive disclosure to real reference and asset files. The only weakness is moderate duplication between the Troubleshooting section and earlier examples/steps.

Suggestions

Consolidate the Troubleshooting section: the 'stuck on scanning' and stale-lock entries repeat Example 3 and Step 6 content — link or merge to remove the duplication.

Trim the repeated state descriptions (scanning/no supported files/auth error) that appear in Step 2, Step 3, Step 6, and Troubleshooting into a single canonical reference.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and assumes Claude's competence (no explaining of bash/jq/git basics), but the Troubleshooting section duplicates content already covered in Example 3 and Step 6 (stale lock, stuck-on-scanning), which could be trimmed.	4 / 5
Actionability	Fully executable, copy-paste-ready guidance throughout — benchmarking with `time`, jq settings updates, cache-seeding test commands, ANSI code constants, chmod, and the install.sh template — covering the common cases concretely.	5 / 5
Workflow Clarity	Seven clearly sequenced steps each ending in an explicit "Done when:" validation checkpoint, with Step 6 providing a full state-by-state test checklist and feedback loops for error recovery; validation is present for the settings-modifying operations so the destructive-operation cap does not apply.	5 / 5
Progressive Disclosure	Clear overview body with well-signaled, one-level-deep references to real bundle files — `references/protocol.md`, `references/implementation-patterns.md`, `assets/install.sh.template`, `assets/README.md.template` (all verified present) — with content appropriately split across files.	5 / 5
	Total	19 / 20 Passed

Description

95%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, third-person description that clearly states what the skill does and when to use it, with comprehensive natural trigger phrases and a distinct niche. The only minor gap is that the concrete actions are lifecycle-level (build/extend/install/test) rather than finely granular.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete lifecycle actions — "Builds a Claude Code statusline from scratch or extends an existing one" and "drives from idea to a working, installed, tested statusline" — plus example data sources, but the verbs stay somewhat high-level rather than enumerating granular operations.	4 / 5
Completeness	Explicitly answers both what (builds/extends a live status bar that runs a shell script after every Claude response) and when ("Use this skill when the user says..." with concrete trigger phrases, plus triggering on described desire for live feedback).	5 / 5
Trigger Term Quality	Comprehensive natural trigger phrases including synonyms and variations — "create a statusline", "make a statusline for X", "add X to my statusline", "show Y in the status bar", "build a statusline plugin", "I want live data", and "live feedback during a Claude session".	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Claude Code statusline) with distinct, specific triggers and minimal overlap risk with other skills.	5 / 5
	Total	19 / 20 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: lirantal/statusline-creator-skill
Path: skills/statusline-creator/SKILL.md
Commit: 46e15c0

Reviewed: 4 days 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.