What does this skill do, and when should you use it?
Loop Triage is a skill from the loop-engineering repository that triages recent changes, CI failures, issues, and conversations. It produces a concise, prioritized Markdown report that a loop can consume, and writes structured output to a state file or Linear board. The skill follows strict rules: it only surfaces items that a reasonable engineer would want to know about today, places everything else in watch or ignore, and never proposes architectural overhauls. It is designed for any Agent Skills client, located at skills/loop-triage/SKILL.md.
The skill takes inputs provided by the loop: recent CI/test failures (last 24h), open issues/Linear tickets assigned to the team, recent commits on main (last 24–48h), Slack/chat threads the loop has visibility into, and the current state file. It analyzes these and generates a Markdown report with four sections: High-Priority Items (with impact, suggested action, and rough effort), Watch Items, Noise/Ignore, and State Updates (facts for the loop to remember for next run). Output is concise and actionable, written to a state file or Linear board.
- A developer wants a daily prioritized list of changes, CI failures, and issues for a loop to act on.
- A maintainer runs a daily loop that automatically identifies PRs or issues needing human attention instead of manual review.
- A team wants to track what the loop already knows via state updates and new signals in a machine-readable format.
- A project lead needs a quick overview of what requires immediate action without digging into details.
- Integrating triage as part of a larger loop workflow, such as the daily-triage pattern, running in L1 report mode.
How do you install this skill?
- The skill depends on external services (CI, Slack, Linear) that may be unreachable from mainland China, affecting usability.
- No explicit guidance on handling sensitive data; users should be cautious with credentials.
- Local filesystem
This skill is part of the loop-engineering repository, which is MIT-licensed. The skill file is at skills/loop-triage/. To install, clone the repository or copy the skills/loop-triage/ folder into your project's skills directory. There is no standalone package manager installation command provided.
tmp="$(mktemp -d)"
git clone --depth 1 https://github.com/cobusgreyling/loop-engineering.git "$tmp"
mkdir -p ~/.claude/skills
cp -R "$tmp/skills/loop-triage" ~/.claude/skills/
rm -rf "$tmp"Generated from the source repository and skill path; it copies only this skill's folder. If the author's install steps above differ, follow those first. To scope it to one project, replace ~/.claude/skills with that project's .claude/skills.
How do you use this skill?
In an Agent Skills client (e.g., Claude Code, Codex), place the skill folder in your project's skills directory. Then ask the loop to run it, providing the expected inputs as part of the loop context. Example trigger prompt:
/loop 1d Run loop-triage. Update STATE.md. No auto-fix in week one.
The skill will produce a Markdown report and write to a state file or Linear board as configured. Refer to the SKILL.md for output format details.
What are this skill's strengths and limitations?
- Provides structured, concise reports that loops can easily consume.
- Clear prioritization rules reduce noise and avoid creating unnecessary work.
- Includes state updates to maintain memory and context across loop runs.
- Tool-agnostic and applicable to a wide range of AI coding agents.
- Part of a broader loop engineering methodology with complementary patterns.
- Depends on external inputs (CI failures, issues, chat threads) that must be provided by the loop or user.
- No built-in test suite; output quality depends on the quality of provided inputs.
- Compatibility with untested platforms like ChatGPT is unknown; verified on Claude Code and Codex.
- Does not perform automatic fixes or actions; it only reports and suggests.
How does this skill compare with similar options?
Side by side with related skills; every score comes from the same FSRS standard.
| Skill | FS score | Stars | Last updated | License |
|---|---|---|---|---|
| Loop Triage Skill this page | 46 · Use with care | ★ 11k | 3d ago | MIT |
| Multica Squad Operations | 56 · Use with care | ★ 52k | 3d ago | NOASSERTION |
| OpenChamber Performance Engineering Skill | 62 · Recommended | ★ 11k | 3d ago | MIT |
| DeepChat Spec-Driven Development Skill | 58 · Recommended | ★ 6.4k | 3d ago | Apache-2.0 |
| Multica Mentioning & Delegation Skill | 58 · Recommended | ★ 52k | 3d ago | NOASSERTION |
How did FollowSkills review this skill?
The skill is primarily instructional with no external operations, so risk of permission abuse is low. However, it lacks explicit guidance on sensitive data handling, least privilege, user confirmation, and rollback, hence deduction.
Static review without execution limits the score; the skill has no built-in error handling or tests.
Inputs, outputs, and triggers are clear, but boundaries are not explicit, and no adaptation for Chinese users or mainland China networks.
Repository has MIT license and well-structured docs, but the skill itself lacks version info, changelog, and maintenance ownership.
Effectiveness cannot be verified statically; output format lacks concrete examples.
Evidence from README and CI, but no direct third-party execution evidence of this specific skill's functionality.
Open a dimension to read why it scored that way
Evidence confidence：Low — Mostly static review, author material or a limited demo; useful for discovery, not high-risk decisions.
See the full review method →