statusline-generator

daymade/claude-code-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/daymade/claude-code-skills --skill statusline-generator
0 commentsdiscussion
summary

This skill provides tools and guidance for creating and customizing Claude Code statuslines. It generates multi-line statuslines optimized for portrait screens, integrates with ccusage for session/daily cost tracking, displays git branch status, and supports color customization.

skill.md

Statusline Generator

Overview

This skill provides tools and guidance for creating and customizing Claude Code statuslines. It generates multi-line statuslines optimized for portrait screens, integrates with ccusage for session/daily cost tracking, displays git branch status, and supports color customization.

When to Use This Skill

This skill activates for:

  • Statusline configuration requests for Claude Code
  • Cost information display (session/daily costs)
  • Multi-line layouts for portrait or narrow screens
  • Statusline color or format customization
  • Statusline display or cost tracking issues
  • Git status or path shortening features

Quick Start

Basic Installation

Install the default multi-line statusline:

  1. Run the installation script:

    bash scripts/install_statusline.sh
    
  2. Restart Claude Code to see the statusline

The default statusline displays:

  • Line 1: username (model) [session_cost/daily_cost]
  • Line 2: current_path
  • Line 3: [git:branch*+]

Manual Installation

Alternatively, manually install by:

  1. Copy scripts/generate_statusline.sh to ~/.claude/statusline.sh
  2. Make it executable: chmod +x ~/.claude/statusline.sh
  3. Update ~/.claude/settings.json:
    {
      "statusLine": {
        "type": "command",
        "command": "bash /home/username/.claude/statusline.sh",
        "padding": 0
      }
    }
    

Statusline Features

Multi-Line Layout

The statusline uses a 3-line layout optimized for portrait screens:

username (Sonnet 4.5 [1M]) [$0.26/$25.93]
~/workspace/java/ready-together-svc
[git:feature/branch-name*+]

Benefits:

  • Shorter lines fit narrow screens
  • Clear visual separation of information types
  • No horizontal scrolling needed

Cost Tracking Integration

Cost tracking via ccusage:

  • Session Cost: Current conversation cost
  • Daily Cost: Total cost for today
  • Format: [$session/$daily] in magenta
  • Caching: 2-minute cache to avoid performance impact
  • Background Fetch: First run loads costs asynchronously

Requirements: ccusage must be installed and in PATH. See references/ccusage_integration.md for installation and troubleshooting.

Model Name Shortening

Model names are automatically shortened:

  • "Sonnet 4.5 (with 1M token context)""Sonnet 4.5 [1M]"
  • "Opus 4.1 (with 500K token context)""Opus 4.1 [500K]"

This saves horizontal space while preserving key information.

Git Status Indicators

Git branch status shows:

  • Yellow: Clean branch (no changes)
  • Red: Dirty branch (uncommitted changes)
  • Indicators:
    • * - Modified or staged files
    • + - Untracked files
    • Example: [git:main*+] - Modified files and untracked files

Path Shortening

Paths are shortened:

  • Home directory replaced with ~
  • Example: /home/username/workspace/project~/workspace/project

Color Scheme

Default colors optimized for visibility:

  • Username: Bright Green (\033[01;32m)
  • Model: Bright Cyan (\033[01;36m)
  • Costs: Bright Magenta (\033[01;35m)
  • Path: Bright White (\033[01;37m)
  • Git (clean): Bright Yellow (\033[01;33m)
  • Git (dirty): Bright Red (\033[01;31m)

Customization

Changing Colors

Customize colors by editing ~/.claude/statusline.sh and modifying the ANSI color codes in the final printf statement. See references/color_codes.md for available colors.

Example: Change username to blue

# Find this line:
printf '\033[01;32m%s\033[00m \033[01;36m(%s)\033[00m%s\n\033[01;37m%s\033[00m\n%s' \

# Change \033[01;32m (green) to \033[01;34m (blue):
printf '\033[01;34m%s\033[00m \033[01;36m(%s)\033[00m%s\n\033[01;37m%s\033[00m\n%s' \

Single-Line Layout

Convert to single-line layout by modifying the final printf:

# Replace:
printf '\033[01;32m%s\033[00m \033[01;36m(%s)\033[00m%s\n\033[01;37m%s\033[00m\n%s' \
    "$username" "$model" "$cost_info" "$short_path" "$git_info"

# With:
printf '\033[01;32m%s\033[00m \033[01;36m(%s)\033[00m:\033[01;37m%s\033[00m%s%s' \
    "$username" "$model" "$short_path" "$git_info" "$cost_info"

Disabling Cost Tracking

If ccusage is unavailable or not desired:

  1. Comment out the cost section in the script (lines ~47-73)
  2. Remove %s for $cost_info from the final printf

See references/ccusage_integration.md for details.

Adding Custom Elements

Add custom information (e.g., hostname, time):

# Add variable before final printf:
hostname=$(hostname -s)
current_time=$(date +%H:%M)

# Update printf to include new elements:
printf '\033[01;32m%s@%s\033[00m \033[01;36m(%s)\033[00m%s [%s]\n...' \
    "$username" "$hostname" "$model" "$cost_info" "$current_time" ...

Troubleshooting

Costs Not Showing

Check:

  1. Is ccusage installed? Run which ccusage
  2. Test ccusage manually: ccusage session --json --offline -o desc
  3. Wait 5-10 seconds after first display (background fetch)
  4. Check cache: ls -lh /tmp/claude_cost_cache_*.txt

Solution: See references/ccusage_integration.md for detailed troubleshooting.

Colors Hard to Read

Solution: Adjust colors for your terminal background using references/color_codes.md. Bright colors (01;3X) are generally more visible than regular (00;3X).

Statusline Not Updating

Check:

  1. Verify settings.json points to correct script path
  2. Ensure script is executable: chmod +x ~/.claude/statusline.sh
  3. Restart Claude Code

Git Status Not Showing

Check:

  1. Are you in a git repository?
  2. Test git commands: git branch --show-current
  3. Check git permissions in the directory

Resources

scripts/generate_statusline.sh

Main statusline script with all features (multi-line, ccusage, git, colors). Copy this to ~/.claude/statusline.sh for use.

scripts/install_statusline.sh

Automated installation script that copies the statusline script and updates settings.json.

references/color_codes.md

Complete ANSI color code reference for customizing statusline colors. Load when users request color customization.

references/ccusage_integration.md

Detailed explanation of ccusage integration, caching strategy, JSON structure, and troubleshooting. Load when users experience cost tracking issues or want to understand how it works.

how to use statusline-generator

How to use statusline-generator on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add statusline-generator
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/daymade/claude-code-skills --skill statusline-generator

The skills CLI fetches statusline-generator from GitHub repository daymade/claude-code-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/statusline-generator

Reload or restart Cursor to activate statusline-generator. Access the skill through slash commands (e.g., /statusline-generator) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.741 reviews
  • Ganesh Mohane· Dec 24, 2024

    statusline-generator has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Kaira Verma· Dec 24, 2024

    statusline-generator reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Sophia Liu· Nov 27, 2024

    statusline-generator fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Aisha Perez· Nov 23, 2024

    Registry listing for statusline-generator matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Sakshi Patil· Nov 15, 2024

    Solid pick for teams standardizing on skills: statusline-generator is focused, and the summary matches what you get after install.

  • Jin Gupta· Nov 15, 2024

    statusline-generator is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • William Verma· Oct 18, 2024

    Registry listing for statusline-generator matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Aisha Choi· Oct 14, 2024

    statusline-generator fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Chaitanya Patil· Oct 6, 2024

    We added statusline-generator from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Jin Desai· Oct 6, 2024

    Useful defaults in statusline-generator — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

showing 1-10 of 41

1 / 5