Menu
Use for an Engram daily triage loop that safely collects and classifies CI, issue, PR, commit, and chat signals into report-only handoff state with bounded scope, no auto-fix, and loop-run-log updates.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use for an Engram dependency triage loop that watches advisories and lockfiles, proposes patch-only updates, rejects major upgrades without approval, and records reproducible verification commands.
Use for an Engram CI sweeper triage loop that groups CI failures, classifies root causes, caps attempts, and proposes bounded minimal-fix candidates only after budget, denylist, and verifier gates.
Use for an Engram PR babysitter triage loop that monitors PR aging, CI blocks, reviewer threads, and lightweight action proposals with isolated-worktree fix candidates and human escalation for risky changes.
Use when designing, implementing, auditing, hardening, or operating agent loops in this repository, including Claude Code/Grok Build/Codex style `/loop` workflows, explicit `/goal` runs, Git worktree orchestration, MCP and memory automation, sub-agent execution, STATE.md handoffs, cost controls, maker/checker verification, and the Engram security gate (full `sensors.sh` + AgentShield scan + `just ci`). Loops default to L1 report-only; autonomous execution against Engram requires a reviewed ADR per the harness security contract.
Weekly or manual security triage loop that executes AgentShield with a hard iteration cap and records the result in a repository state file.
Run structured consensus with Engram's `memory_council` tool and `CouncilSkill` SDK wrappers for architecture, design, policy, security, reliability, performance, ADR, or tradeoff decisions. Use when the user asks for consensus, council review, multi-agent-style review, decision rationale, option comparison, or mentions `llm-council`, `memory_council`, or `CouncilSkill`. Do not use for simple lookup, single-answer retrieval, or execution-only coding tasks after a decision is already made.
| name | loop-triage |
| description | Use for an Engram daily triage loop that safely collects and classifies CI, issue, PR, commit, and chat signals into report-only handoff state with bounded scope, no auto-fix, and loop-run-log updates. |
Use this skill for repeatable L1 signal collection and safe report-only handoff.
Pair it with skills/loop-engineering/SKILL.md for the global loop guardrails.
Collect only the signals needed for the requested cadence:
STATE.md and loop-run-log.md.Append a concise update to the loop state file, normally under
docs/loops/<loop-name>/STATE.md for repository-wide Engram loops:
## High Priority
- Item:
Why now:
Suggested next action:
Effort estimate:
## Watch List
## Noise / Ignore
## State Updates
Append one summary line to loop-run-log.md with timestamp, result, evidence,
and next action.
Use this shape when dispatching the loop:
Run loop triage. Update STATE.md with High Priority, Watch List, Noise, and
State Updates. Update run timestamp and append loop-run-log.md. If action is
clear, low-risk, and a single-file bugfix candidate, escalate to minimal-fix
only in L2.
Mark the run complete only when STATE.md and loop-run-log.md are updated,
the evidence source is named, and any human-required item is escalated clearly.