skill CX Codex

statusline — Claude Code skill: what it does, how to install

Q: How to install statusline in Claude Code?

Run `npx skills add dailydotdev/daily --skill statusline -a claude-code`. The file will be placed at `~/.claude/skills/statusline/SKILL.md`.

Q: What are the prerequisites for running statusline?

Your environment must have `node` present on the `PATH`. To opt out of anonymous impression metrics, export `DAILY_DEV_TELEMETRY=0`.

Cleans up duplicate daily.dev headlines and configures the terminal status line across different Claude Code releases.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓

npx skills add dailydotdev/daily --skill statusline -a claude-code

Open on GitHub

What statusline does

This skill fixes daily.dev headline rendering inside Claude Code. Since release 2.1.275, headlines appear through a built-in hooks module. Upgraded setups often show duplicate text because an earlier entry remains inside ~/.claude/settings.json. The assistant inspects that file and strips the outdated statusLine definition.

Older Claude Code builds lack hook support. For releases before 2.1.275, the skill configures a fallback command pointing to statusline.mjs. It resolves the plugin directory with a wildcard pattern so future updates do not break the path. Headlines refresh roughly every sixty seconds and support clickable terminal links.

Without node in your PATH, the status line script fails immediately. Users concerned with telemetry can turn off impression tracking by setting DAILY_DEV_TELEMETRY=0 in their environment.

What it helps with

fix duplicate daily.dev headline banners in Claude Code
remove legacy statusLine settings from settings.json
configure statusline fallback for Claude Code releases prior to 2.1.275
disable impression telemetry via DAILY_DEV_TELEMETRY=0

Example prompts for the agent

Fix my daily.dev statusline, the headline shows up twice
Remove the old statusLine config from Claude Code settings
Set up daily.dev headlines for an older Claude Code version

How to install statusline

1Skills CLI (Vercel)

npx skills add dailydotdev/daily --skill statusline -a claude-code

2Manually: put the files in place

~/.claude/skills/statusline/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/statusline/

1Skills CLI (Vercel)

npx skills add dailydotdev/daily --skill statusline -a codex

2Manually: put the files in place

.agents/skills/statusline/SKILL.md

For all projects use ~/.agents/skills/

1Skills CLI (Vercel)

npx skills add dailydotdev/daily --skill statusline -a cursor

2Manually: put the files in place

.cursor/skills/statusline/SKILL.md

Cursor also reads .agents/skills/ and .claude/skills/

1GitHub CLI

gh skill install dailydotdev/daily statusline

2Manually: put the files in place

.github/skills/statusline/SKILL.md

1Skills CLI (Vercel)

npx skills add dailydotdev/daily --skill statusline -a gemini-cli

2Platform CLI

gemini skills install https://github.com/dailydotdev/daily --path .claude-plugin/plugins/daily.dev/skills/statusline

Manually: put the files in place

.devin/skills/statusline/SKILL.md

The legacy .windsurf/skills/ path still works

Skills CLI (Vercel)

npx skills add dailydotdev/daily --skill statusline -a opencode

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about statusline

How to install statusline in Claude Code?

Run npx skills add dailydotdev/daily --skill statusline -a claude-code. The file will be placed at ~/.claude/skills/statusline/SKILL.md.

Why does the daily.dev headline appear twice?

Claude Code 2.1.275 or newer displays news using an internal hook. If ~/.claude/settings.json still retains the legacy statusLine command from older plugin versions, both render simultaneously.

What are the prerequisites for running statusline?

Your environment must have node present on the PATH. To opt out of anonymous impression metrics, export DAILY_DEV_TELEMETRY=0.

setup-matt-pocock-skills Matt Pocock This skill configures a repository for Matt Pocock's engineering skills by setting its issue tracker, triage labels, and domain docs layout. Run it before using the other skills. 1,052,851installs ask-matt Matt Pocock Routes you to the right Matt Pocock skill or flow for the task at hand. Use it when you need a starting point for a feature, prototype, incoming issue, or hard bug. 766,587installs to-tickets Matt Pocock Turns a plan, spec, or conversation into small end-to-end tickets with explicit blockers. Use it to agree on the work breakdown before tickets go to a tracker. 711,230installs writing-plans Jesse Vincent This skill turns requirements for a multi-step task into an implementation plan before code changes begin. It helps when another engineer needs exact files, interfaces, and checks. CX Codex 282,859installs caveman-review JuliusBrussee Turns code review comments into one line per finding: location, problem, fix. Useful when a diff or PR needs a fast pass without the filler. CX Codex +1 411,800installs caveman-compress JuliusBrussee Compresses CLAUDE.md, todo lists, and other prose files into a shorter format while retaining a readable backup. CX Codex +1 411,500installs

From the same set4

trends Pulls the day's tech headlines and the most-upvoted daily.dev posts into your agent chat. Handy when you want a quick read on what people are talking about. CX Codex +1 ★ 20,118repo stars daily.dev This skill gives an agent access to current developer content through the daily.dev API. Use it to find articles and manage feeds or bookmarks. CX Codex +1 ★ 20,118repo stars daily-dev-ask Gives your agent a search over developer articles ranked by community upvotes. Answers cite real sources instead of guessing. CX Codex +1 ★ 20,118repo stars