loops
Skill1 starsChanged 6 months agoMITView on GitHub
Show a unified view of Claude Code cron/loop state — currently active cron jobs, currently paused loops (from /loop-pause), and recent loop history (last starts/pauses/resumes/stops). Use this to check what's running or recently ran.
12 other projects use a version of this.
Adopted by
Most recently taken up by
- sophonfinance-wq/finance-automation-portfoliotheir own version, first seen Nov 1, 2026
- anlmalabs/skillstheir own version, first seen Oct 25, 2026
- 5dive-ai/skillstheir own version, first seen Oct 5, 2026
- xmeir-dev/skillstheir own version, first seen Oct 4, 2026
- vivary-dev/vivarytheir own version, first seen Sep 27, 2026
- michielhdoteth/awesome-ai-agent-toolstheir own version, first seen Aug 24, 2026
Used with
Projects with it also use code-review.
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.
GoogleSkillcode-review
Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.
Also in 3 projects that use this
Other versions12 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 12
- jwangkun/loops★ 123same name
- michielhdoteth/awesome-ai-agent-tools★ 62same name
- sophonfinance-wq/finance-automation-portfolio★ 16same name
- 0-CYBERDYNE-SYSTEMS-0/FFT_nano★ 4same name
- vivary-dev/vivary-cli★ 4same name
- weselben/RooForge★ 4same name
- 5dive-ai/skills★ 2same name
- miketromba/skills★ 2same name
- vivary-dev/vivary★ 1same name
- anlmalabs/skills★ 0same name
2 more not listed
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 repository16 other files it gives its agents.
- audit-unused-depSkill
- checkpointSkill
- double-checkSkill
- file-adrSkill
- fleetSkill
- fmt-sweepSkill
- forge-mirror-scaffoldSkill
- forgeSkill
- gemini-pullSkill
- loop-from-taskSkill
- loop-healthSkill
- loop-onSkill
- loopSkill
- regression-guardSkill
- restoreSkill
- workspace-testsSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 38
If active + paused + history are ALL empty: "No loops active, paused, or in history yet.
- Very specific: line 53
Not wired into the binary (destructive ops kept out of the auto-callable path).
- Distinctive: line 63
Don't modify state files. This skill is strictly read-only.
- Distinctive: line 64
Don't call CronCreate / CronDelete here — those belong to /loop-resume / /loop-pause.
“Common” is measured: kept by at least 6 in 10 of the 10 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
/loops — list active + paused + recent loop activity
Thin wrapper around claude-loop list. Binary owns file reads +
JSON shaping. Agent does the CronList API call.
Steps
- Active jobs — call
CronList, render the output. Paused + recent history — invoke the binary:
claude-loop listStdout is JSON with
paused(array of paused-job records) +history_tail(last 20 lines ofloop-history.jsonl).Render compactly:
Active (N): <id> · <cadence_human> · <prompt first 60 chars>... Paused (M): · cron=<expr> · paused at <ISO>: <prompt first 60 chars>... (run /loop-resume to restore) Recent history (latest first): <ISO> <event> <id> <prompt first 40 chars>...If active + paused + history are ALL empty: "No loops active, paused, or in history yet. Use /loop to schedule one."
Optional argument: /loops history [N]
For just the history tail:
claude-loop history -n 50Default N = 20.
Optional argument: /loops clear-history
Not wired into the binary (destructive ops kept out of the
auto-callable path). Suggest rm ~/.claude/loop-history.jsonl if
the user really wants to truncate.
Net visible tool calls per /loops
2 total: CronList + Bash(claude-loop list).
Don't
- Don't modify state files. This skill is strictly read-only.
- Don't call CronCreate / CronDelete here — those belong to /loop-resume / /loop-pause.
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.