Orchestrate iterative visual style searches with branch prompts, decision graphs, feedback loops, and final direction selection.
日本語の概要は準備中です。原文の説明を表示しています。
Process tails that hold memory for nothing: finds them and, on the owner's word, kills them. Use on "slow", "swap", "low memory", "kill the tails", "clean up memory", "ram doctor", and after closing heavy apps.
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
The snapshot only reads; step 4 kills, and only on the owner's word.
"13 of 16 GB used" and the swap size do not show load: macOS keeps memory busy with cache and compression, and swap does not shrink until a reboot. Memory is short when any of these holds:
sysctl kern.memorystatus_vm_pressure_level is 4 or stays at 2 for long (threshold: on Apple silicon 2 appears under ordinary compression); memory_pressure | tail -1 shows less than 25–30% free;Swapouts in vm_stat grow between two readings a minute apart;No signs: clean only on a direct request. Measure a process by top -o mem or footprint; ps understates the compressed part.
Snapshot. From the skill root:
bash scripts/tails-macos.sh # local
ssh -o BatchMode=yes -o ConnectTimeout=8 <alias> 'bash -s' < scripts/tails-<os>.sh # remote
Keep the script's summary as the "before" and take the top of top -o mem: the table omits launchd services (on Linux, .service units), system processes, Claude.app and children of active sessions, and one live job (a local whisper run, 9 GB) can outweigh all the tails. Done when you hold the table, the summary and the top of top.
Decide. The "Action" column sets what to do with a class (the script prints the Russian labels shown):
| Class | What it is | Action |
|---|---|---|
claude-сессия (claude session) | Claude Code CLI, bundled with Desktop or standalone | kill if a tail |
хвост закрытого приложения (closed-app tail) | processes of X.app with PPID 1 while X is not running, and everything under them | kill |
сирота (orphan) | a worker with PPID 1: omp/bun, Chrome for Testing, npx/MCP, grok/codex; duplicates marked | kill |
dev-сервер (dev server) | http.server, vite, npm run dev without a parent, older than a day | ask |
зомби (zombie) | STAT Z older than a minute | its parent reaps it: name the parent |
The script does not know session activity: match the id from the row against list_sessions. A tail is a session with lastActivityAt older than 12 h, not isRunning, with no work going on. Id "не найдена" (not found) and sessions on a remote machine (list_sessions does not know them): ask. Done when every row has an action and every claude row has a verdict: tail, live or ask.
Show. The table to the owner: row, action, what dies with it. Before killing a claude process, name its dev servers and ports from the "dies with it" column. "Kill" and "clean up" go straight to step 4; "slow" and "swap" wait for the word. Done when the owner sees the table and the word is received or not needed.
Kill. Only rows that passed step 2, in bash with an array, with a check and a follow-up KILL:
# bash -c: in zsh `kill $pids` with a string silently kills nothing
bash -c 'pids=(111 222 333); kill -TERM "${pids[@]}"; sleep 4
for p in "${pids[@]}"; do kill -0 "$p" 2>/dev/null && kill -KILL "$p"; done'
& inside a session outlives it as an orphan: check the port with lsof -iTCP:<port> -sTCP:LISTEN.Done when no pid from the array answers kill -0 and the ports of killed dev servers are free.
Verify. Run the script again. Report to the owner: pressure and the candidates' RSS before and after; swap does not shrink until a reboot, so it is not the measure. A killed claude session stays in the app's list and comes back on the next message. Killing the CLI does not free the memory of Desktop's renderer and main processes: that needs an app restart, on the owner's word, after checking it will not interrupt needed work, with another reading. Done when the run shows no killed candidates and "before" and "after" are named.
isRunning claude sessions;まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
Orchestrate iterative visual style searches with branch prompts, decision graphs, feedback loops, and final direction selection.
日本語の概要は準備中です。原文の説明を表示しています。
Audits the agent rules in the current folder (AGENTS.md, nested AGENTS.md files) and the skill descriptions the agent sees at start, then reports what to cut, move or rewrite and edits only after the user says yes. Use on «аудит правил», «проверь AGENTS.md», «почему агент не слушается правил», «проверь скиллы».
日本語の概要は準備中です。原文の説明を表示しています。
Робот агента Personal Corp. Агент делает себе голову робота из набора деталей, хранит её в штабе в stack/avatars.json и кладёт в штаб страницу avatar/robot.html, где робот стоит за партой своего штаба и вокруг видны отделы, без сервера и интернета. На уроке по ссылке входа с экрана урока робот входит в живой класс и горит маячком, пока агент работает. Триггеры /avatar, /avatar <ссылка входа>, сделай себе аватар, покажи своего робота, приди на урок.
日本語の概要は準備中です。原文の説明を表示しています。
Use when choosing between engines or models for an agent pipeline and the answer must come from measurement on your own data, not from marketing pages: speech recognition for meeting recordings, the model that turns a transcript into notes, the critic model that checks it. Runs every variant in an isolated container, measures time, cost per hour of input (USD and RUB, with price source and date) and quality (WER/CER and course terms for ASR; code checks plus a judge of a different model for LLM steps), writes results.json/csv and one static analytics page. Triggers on "бенчмарк", "сравни движки", "сколько стоит час записи", "какую модель взять для пайплайна", "benchmark the pipeline", "compare ASR engines".
日本語の概要は準備中です。原文の説明を表示しています。
Use when user asks for Claude Code usage stats, weekly analytics, project activity summary, or wants to see what projects were worked on. Triggers on "аналитика", "статистика claude", "cc stats", "weekly report", "что делал"
日本語の概要は準備中です。原文の説明を表示しています。
Use when needing strategic project analysis from multiple independent expert perspectives. Triggers on business decisions, growth strategy, product direction, competitive analysis, or any situation where diverse C-level opinions reduce blind spots
日本語の概要は準備中です。原文の説明を表示しています。