cleanup
Skill1 starsChanged 55 days agoMITView on GitHub
Nettoyage intelligent du VPS/projets — analyse disque, fermeture des sessions de travail détachées (protège la connexion + l'infra), purge sûre (cache Docker/APT/journal, résidu /tmp, caches Bun/npm/go), purge des artefacts de build rebuildables (target/ Rust, node_modules, .next) avec garde-fou anti-session-active, et audit de cohérence de la documentation des projets.
71 other projects use a version of this.
Adopted by
Most recently taken up by
- udecode/better-convextheir own version, first seen Nov 9, 2026
- fynnhaupt/skillstheir own version, first seen Nov 8, 2026
- VforVal/lumberjacktheir own version, first seen Nov 8, 2026
- LeonardiFranco/skillstheir own version, first seen Nov 8, 2026
- frnkgns/Overgeared-Skillstheir own version, first seen Nov 8, 2026
- Integralist/agent-skillstheir own version, first seen Nov 6, 2026
Used with
Projects with it also use chips, react-query-best-practices and 10 more.
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.
udecodeSkillchips
Run the project's suggested-task ledger, the chips. /chips alone brings this session's open tasks up to date: it applies what the ledger helper says, settles stale and split tasks, cards what can start and reports the board, and /chips all also takes the ship-list tasks and the ones no live session owns, and merges duplicate tasks across the board. Use for /chips, /chips offer, start or drop, \"what chips are open\", \"suggest a task for X\", \"update the chips\", \"clean up the chips\", \"which chips are stale\", \"is this chip still worth doing\", \"merge duplicate chips\", at the last hand-back of a run that offered a task, and whenever pstack would file a tracked issue, a follow-up, a reflect Backlog item or an out-of-band PR.
Also in 3 projects that use this
bibektimilsina00Skillreact-query-best-practices
Audit and fix React Query usage in apps/web — enforce query key factories, signal forwarding, staleTime, and proper mutation patterns. Use when reviewing or fixing server-state code.
Also in 3 projects that use this
- bibektimilsina00Skill
you-might-not-need-a-callback
Analyze and fix useCallback anti-patterns in your code
Also in 3 projects that use this
Scylla23Skillredo
Re-run the last routed task one model tier up (haiku → sonnet → opus → fable). User-invoked escalation when the previous result missed. Pass --dry-run to preview without running.
Also in 3 projects that use this
Aetheria-Labs1Skillplan-page
Plan one storefront page from strategy through final copy, section order, proof, offers, template direction, responsive layout, and production asset requirements. Stops at an approved execution-ready specification.
Also in 3 projects that use this
SocialKit-APISkillvideo-transcripts
Extract transcripts from social videos through SocialKit across YouTube, TikTok, Instagram, Facebook, X/Twitter, LinkedIn, and direct video file URLs. Use when the user asks to transcribe, get captions or subtitles, pull the spoken text, or read what a video says, including one video or many at once. Returns full text plus timestamped segments. Not for posting, private accounts, or unrelated website scraping.
Also in 3 projects that use this
- +3 more from bibektimilsina00
Other versions71 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 71
- simstudioai/sim★ 30ksame name
- pipecat-ai/pipecat★ 17ksame name
- udecode/plate★ 17ksame name
- civitai/civitai★ 7.3ksame name
- mampfes/hacs_waste_collection_schedule★ 2.3ksame name
- trycompai/comp★ 2.1ksame name
- udecode/dotai★ 1.2ksame name
- LedgerHQ/ledger-live★ 627same name
- ericboy0224/learn-docker-and-k8s★ 472same name
- udecode/better-convex★ 452same name
61 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 repository45 other files it gives its agents.
- ad-creativeSkill
- agent-ecosystem-watchSkill
- ai-logic-osSkill
- album-masteringSkill
- alexandriaSkill
- alignment-osSkill
- analyzing-financial-statementsSkill
- applying-brand-guidelinesSkill
- blueprint-osSkill
- brainstorm-osSkill
- builder-osSkill
- changelog-adoptSkill
- cold-emailSkill
- content-strategySkill
- creating-financial-modelsSkill
- design-osSkill
- diagramSkill
- duoSkill
- execution-osSkill
- growth-engineSkill
- habit-tracker-osSkill
- higgsfield-generateSkill
- higgsfield-soul-idSkill
- identity-shift-osSkill
- intuitive-osSkill
- journal-osSkill
- launch-strategySkill
- marketing-strategistSkill
- market-research-osSkill
- market-researchSkill
- mindset-osSkill
- monitorSkill
- nuclear-cleanupSkill
- omg-auditsSkill
- pixelragSkill
- product-marketing-contextSkill
- project-tidySkill
- ramflushSkill
- secrets-vaultSkill
- seductive-osSkill
- social-contentSkill
- staxSkill
- stepper-osSkill
- storyteller-osSkill
- watchSkill
The file
Files
Cleanup — ménage VPS Agentik
Objectif : libérer de l'espace et garder une doc cohérente, sans jamais casser un travail en cours ni supprimer du contenu produit ou du canon projet.
Règle d'or — JAMAIS de suppression sans deux conditions
- Machine au repos : lancer
scripts/idle-check.sh. S'il renvoieBUSY:…→ STOP, lister le travail actif, ne rien supprimer. - Validation utilisateur : pour tout ce qui touche
~/Station, les caches d'un user, ou de la doc → présenter la liste (chemins + tailles + raison) et attendre l'accord. Les étapes "auto-sûres" (cache Docker/APT/journal) peuvent se faire sans valider chaque item, mais toujours après le garde-fou repos.
RÈGLE ABSOLUE — jamais de kill sur claude / rmux (opérateur, 2026-08-11)
Pendant un cleanup, ne JAMAIS kill un process claude ni un daemon ou une
session rmux vivante — même détachée, même vieille, même à 0% CPU. "Détaché" ≠
"mort" : une session détachée porte des agents en plein travail, un claude à
faible CPU attend souvent une réponse API entre deux turns, et tuer le daemon
rmux tue TOUTES les sessions d'un coup. Incident fondateur : le 2026-08-11 un
cleanup RAM a tué des claude actifs pris pour idle, y compris sa propre
session. Fermer une session est un geste de l'opérateur (omega kill
<name>, rmux kill-server), jamais du cleanup — même avec un go générique
« clean up ». La récupération de RAM se limite à : workers de modèles idle
(TTS/STT), dev servers oubliés, stacks Docker prouvées idle (avec accord),
caches. close-sessions.sh porte ce garde-fou en dur et refuse tout pid
claude/rmux.
Périmètre INTOUCHABLE (ne jamais supprimer)
- Tout
~/Station/**sauf des artefacts de build explicitement rebuildables (target/,.next/,dist/) — et encore, seulement avec accord. - Docs canon :
vision/**, fichiers*PRD*,*feature*,*step*,Vision/,OMEGA.md,CLAUDE.md,AGENTS.md,README*,CHANGELOG,LICENSE,SECURITY.md,~/.omega/rules/**, les fiches projet. - Tout dossier avec beaucoup de
.md(>20) = probablement du contenu produit (cours, blog, data), PAS de la doc → protéger par défaut, demander. - Sessions / sockets actifs :
claude-*,rmux-*,tmux-*,rx-socketna-*,cloudflared, la worktree d'un build en cours.
Déroulé
- Fermeture des tunnels/mosh détachés (si demandé) :
scripts/close-sessions.shferme les tunnels cloudflared + serveurs mosh détachés devibe/lab— et RIEN d'autre : claude et rmux sont hors périmètre par la Règle absolue ci-dessus (le script refuse ces pids en dur). Protège toujours la connexion courante (root) et l'infra (omega-mc, bots, daemons sécurité, tailscale, sshd). Tester d'abord avec--dry. - Garde-fou :
scripts/idle-check.sh. Si occupé → rapport + stop. - Analyse :
scripts/analyze.sh→ df, top du/home/tmp/var,docker system df. - Purge auto-sûre :
scripts/safe-clean.sh→docker builder prune,apt-get clean,journalctl --vacuum-size=100M. (rien de Station, rien de doc.) - Résidu /tmp :
scripts/tmp-residue.sh list→ présenter candidats (dirs de build/repro/audit, exclut tout ce qui est ouvert/actif). Après accord :tmp-residue.sh purge. - Caches user rebuildables :
scripts/clean-caches.sh→ purge~/Linux/cache(Bun, go-build, npm_cacache/_npx, node-gyp, playwright) pourvibe/lab. Ne touche ni config, ni data/state, ni Station. - Artefacts de build dans Station (sur demande) :
scripts/clean-builds.sh [base]→ purgetarget/Rust (à côté d'unCargo.toml),node_modules,.next. Rebuildables mais coût : prochain build/installrecompile. Garde-fou anti-build + re-testeomega --version(preuve non-régression). NE touche pas au code source ni aux binaires installés. - Audit doc :
scripts/doc-audit.sh <projet>→ classe en PROTECTED / SCRATCH / REVIEW. Présenter la liste SCRATCH pour validation ; ne jamais auto-supprimer. Proposer ensuite la création dePROGRESS.md(recap canon) + complétion deRULES.md/fiche par projet.
Notes
- Les images Docker et les volumes par-agent ne sont PAS du déchet par défaut (peuvent être réutilisés par OmegaOS) → ne pas purger sans confirmation ciblée.
- Toujours afficher l'espace AVANT/APRÈS.
- Si un doute → ne pas supprimer, demander.
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.