What crew has right now — worktrees, running dev servers with their check verdict and URLs, recorded failures — in one readable summary. Use when the user asks what is running, what they have checked out, whether the servers are up, or "crew status".
3 stars
0 votes
0 copies
1 view
Added October 5, 2026
developmentgo
Works with
cli
Security analysis
A100/100
Scanned October 5, 2026
$npx -y skills add FurlanLuka/crew --skill status --agent claude-code
Installs into .claude/skills of the current project.
Are you the author of Status?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/furlanluka-status)
---
name: status
description: >
What crew has right now — worktrees, running dev servers with their check verdict and URLs,
recorded failures — in one readable summary. Use when the user asks what is running, what
they have checked out, whether the servers are up, or "crew status".
user-invocable: true
---
Run `crew ls worktrees <workspace> --json` and `crew dev status $ARGUMENTS --json` — the
argument is a workspace or `ws/wt`; `ls worktrees` takes only the workspace half; both bare
when none. For every worktree marked `installing`, `crew setup status <ref>` — the runners'
table, which project is at which step. For every worktree with servers running, also `crew
dev check <ref>` (bare — one look; `--wait` only right after a start you made).
Summarize readably: runners still going first (per project: step and how long), then
recorded issues (`checkout failed`, `install failed`, `server died`, `server not listening`,
`N issues` — with the `crew fix <ref> --print` / `crew verify <ref> <project>` line), then
each worktree with its running servers, their check verdict and clickable URLs, then the
ones with nothing running. Refs as `ws/wt`. Do not guess; if a command fails, show the
error.
