demartinogiuseppe

Idle Intel — Development skill for Claude Code

Development community

Project health micro-briefings in Claude Code's wait state — vulns, outdated deps, unpushed commits, tech debt.

How to install Idle Intel

This entry records only its repository, not the path inside it, so there is no exact command to give. Open demartinogiuseppe/idle-intel and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Idle Intel does

Project health micro-briefings in Claude Code's wait state — vulns, outdated deps, unpushed commits, tech debt. Your status line, working for you.

Alternatives in Development

  • Ralph Loop — Autonomous coding loop — works through tasks, commits, repeats 14k ★
  • /intel — Fetch actionable intelligence for a target 1.8k ★
  • Tech Debt Issue — Alias for tech-debt issue 1.2k ★

README

idle-intel

![idle-intel in action: rotating project-health insights in Claude Code wait state](demo.gif)

**The status line is the most-watched line on a developer's screen while an AI agent thinks. Today it says "Thinking...". It could say something worth knowing.**

idle-intel replaces Claude Code's empty wait state with rotating micro-briefings about the project you're already working on:

◈ npm audit: 0 critical, 1 high severity vulns -> run `npm audit fix`
◈ git: 2 unpushed commits on this branch
◈ git: 1 stash sitting around -- still needed?
◈ 2 FIXME markers in the codebase -- oldest debts bite hardest

One line at a time, rotating every 12 seconds. Zero interruption, zero network beyond your own package manager, zero telemetry.

Why

Tools have appeared that fill the agent wait state with ads. This project is the opposite bet: **the wait state is valuable because it's empty** — the only moment a developer looks at the screen without acting. Filling it with generic content destroys it; filling it with one glanceable fact about *your own project* respects it. Vulnerabilities you haven't patched, commits you haven't pushed, debt you've stopped seeing.

What it detects

Collector Insights
npm known vulnerabilities (npm audit), major updates, pending minor/patch updates
pip outdated packages
git unpushed commits, forgotten stashes, branches untouched 30+ days
codebase TODO / FIXME counts, oversized node_modules

Each collector activates only if its manifest and tool are present, and fails silently otherwise. All facts are local. Nothing is uploaded anywhere.

Architecture

Two-speed design:

  • Fast path (statusline.sh, pure bash, ~20ms): reads one line from a cache, rotates by time. Runs on every status line refresh.
  • Slow path (collect.py, stdlib-only Python): scans the project and rewrites the cache atomically. Triggered in the background when the cache is older than 30 minutes.

The s