process-triage
Process-triage provides diagnostic tools for identifying and safely managing runaway processes through the `pt` command wrapper. Use it when system processes consume excessive resources and you need structured analysis before termination, relying on `pt scan`, `pt deep-scan`, and `pt agent` subcommands to assess process behavior and recommend remediation steps that require explicit user approval before execution.
git clone --depth 1 https://github.com/boshu2/agentops /tmp/process-triage && cp -r /tmp/process-triage/images/gemini/skills/process-triage ~/.claude/skills/process-triageSKILL.md
# process-triage Use `pt` as the user-facing command and `pt help` for wrapper-aware help. Core workflows: - `pt scan --format json` - `pt deep-scan --format json` - `pt agent plan` - `pt agent explain` - `pt agent apply` Safety: - Never kill automatically without explicit user approval - Prefer `pt agent` over legacy `pt robot` - Use structured output for agent automation
Switch a caller-selected coding-agent Triggers: "switch account", "rotate coding-agent account".
Use when operating ACFS flywheel health checks, init, and agent loop tooling from ~/acfs/bin/acfs.
Use Agent Mail as an optional messaging and Triggers: "coordinate writers", "reserve files".
Operate explicit orchestrator, implementer Triggers: "agent-native factory", "role-shaped agent panes", "persistent workers".
Run AGY headlessly via scheduled ticks or `agy -p`, capture agentapi JSONL evidence, and validate automated AGY loops or event streams.
|-
Use an explicitly selected AGY runtime for Triggers: "agy", "antigravity", "AGY evidence".
|-