stop
Skill0 starsChanged 4 months agoMITView on GitHub
Stop the locally running Claude Code Time Tracker dashboard. Shuts down the background Next.js dev server that /time-tracker:launch started and cleans up its PID file. Run when the user types /time-tracker:stop, or says "stop the time tracker", "shut down the dashboard", "kill the time tracker server", "close the dashboard".
8 other projects use a version of this.
Adopted by
Most recently taken up by
- leinardi/adversarial-review-looptheir own version, first seen Nov 8, 2026
- adventurewave-labs/apsl-coretheir own version, first seen Oct 20, 2026
- heikki-laitala/stick-aroundtheir own version, first seen Oct 9, 2026
- jankocian/cc-voice-controltheir own version, first seen Jun 24, 2026
- gstredny/ClaudeCodeWorkflowtheir own version, first seen May 6, 2026
- tjg37/ironclawtheir own version, first seen Apr 26, 2026
Used with
Projects with it also use status.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AnthropicSkillstatus
Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.
Also in 3 projects that use this
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- kennethleungty/claude-music★ 23same name
- leinardi/adversarial-review-loop★ 2same name
- gstredny/ClaudeCodeWorkflow★ 1same name
- heikki-laitala/stick-around★ 1same name
- tjg37/ironclaw★ 1same name
- adventurewave-labs/apsl-core★ 0same name
- jankocian/cc-voice-control★ 0same name
- Jonely235/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- deploy-vercelSkill
- launchSkill
- scoreSkill
- setupSkill
- snapshotSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Stop the background dev server started by /time-tracker:launch.
- Distinctive: line 14
Stop via the PID file: if present:
- Distinctive: line 28
Fallback / sanity check: If there was no PID file (or a stale one), find any dev server still serving this app and stop it.
- Very specific: line 34
Prefer the narrowest match you can - if pgrep -af "next dev" shows other projects' servers, only target the one whose cwd is $APP_DIR …
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Stop - shut down the dashboard
Stop the background dev server started by /time-tracker:launch.
How to run
- Locate the install.
APP_DIR="${CCTI_APP_DIR:-$HOME/.claude-time-tracker}". - Stop via the PID file if present:
if [ -f "$APP_DIR/.dev-server.pid" ]; then PID=$(cat "$APP_DIR/.dev-server.pid") # Kill the process group so the Node child (next-server) goes too. kill "$PID" 2>/dev/null && sleep 1 kill -9 "$PID" 2>/dev/null rm -f "$APP_DIR/.dev-server.pid" echo "stopped pid $PID" else echo "no pid file" fi - Fallback / sanity check. If there was no PID file (or a stale one), find any dev server
still serving this app and stop it. Match on the app directory to avoid killing unrelated
Node processes:
Prefer the narrowest match you can - ifpkill -f "next dev" 2>/dev/null || truepgrep -af "next dev"shows other projects' servers, only target the one whose cwd is$APP_DIRrather than killing them all. - Report whether a server was stopped or nothing was running. Remind the user they can
start it again anytime with
/time-tracker:launch.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

