New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Loop Triage Report

by cobusgreyling in cobusgreyling/loop-engineering

Turns CI failures, open issues, recent commits and chat threads into a prioritized markdown report that an automation loop can act on without inventing architecture work.

MITAuto-check passedDevOps & Cloud

Install Loop Triage Report

skills CLI
$ npx skills add cobusgreyling/loop-engineering --skill loop-triage -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install cobusgreyling/loop-engineering loop-triage --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/cobusgreyling/loop-engineering.git skills-src && mkdir -p .claude/skills && cp -r skills-src/starters/minimal-loop-opencode/skills/loop-triage .claude/skills/loop-triage && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
loop-triage
GitHub stars
11k
Token cost
~500 tokens
SKILL.md length
256 words
Files
1
Skills in repo
21
Repo updated
First seen
Licence
MIT

At a glance

Turns CI failures, open issues, recent commits and chat threads into a prioritized markdown report that an automation loop can act on without inventing architecture work.

  • Works in 4 steps: High-Priority Items (act on these) → Watch Items (monitor, do not act yet) → Noise / Ignore → …
  • Summarizing recent CI failures, issues and commits for an automation loop
  • SKILL.md covers Inputs (the loop will provide…, Output Format, Rules and Example Invocation (in an…
  • Calls opencode

What it does

Given recent CI and test failures, open tickets, commits from the last day or two, any chat threads the loop can see, and its current state file, the skill produces a four-section report: high-priority items worth acting on today, each with a one-line description, why it matters, a suggested next action such as drafting a minimal fix in an isolated worktree, and a rough effort estimate; lower-urgency watch items in the same format; a short list of things looked at and judged not worth action; and state updates, facts the loop should remember for its next run.

The rules keep the report tight: be brutally concise, put something in high priority only if a reasonable engineer would want to know about it today, default to watch or noise when in doubt rather than inventing work, never propose an architectural overhaul during triage since this skill is for signal rather than invention, and respect the project's existing skills and conventions as given in context. An example invocation shows it called from an opencode loop with instructions to append high-priority items to a state file without touching code.

When your agent uses it

  • Summarizing recent CI failures, issues and commits for an automation loop
  • Deciding what a loop should act on today versus just watch
  • Writing structured state updates for the next loop run
  • Filtering signal from noise before a loop drafts a fix

Example prompts

  • “Call loop-triage and append high-priority items to STATE.md.”
  • “Triage the last 24 hours of CI failures and open issues into a report.”
  • “What should today's loop run act on versus just watch?”

Requirements

  • Access to recent CI results, issues, commits and the loop's current state file

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. High-Priority Items (act on these)
  2. Watch Items (monitor, do not act yet)
  3. Noise / Ignore
  4. State Updates

What it can do on your machine

Read from SKILL.md and the folder at commit 87c5e9c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • opencode

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Loop Triage Report loads about 500 tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 256 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~53
When it runs · the whole SKILL.md, loaded when a task matches
~500

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from cobusgreyling/loop-engineering at commit 87c5e9c, republished under its MIT licence (© cobusgreyling). 256 words, ~500 tokens.

Download SKILL.mdSave it as .claude/skills/loop-triage/SKILL.md (or your agent's skills folder).
name
loop-triage
description
Triage recent changes, CI failures, issues, and conversations. Produces a concise, actionable findings report suitable for a loop to consume. Writes structured output to a state file or issue tracker.
user_invocable
true

Loop Triage Skill

You are an expert engineering triage agent. Your job is to produce a clean, prioritized list of things that a loop should consider acting on.

Inputs (the loop will provide these)

  • Recent CI / test failures (last 24h)
  • Open issues / tickets assigned to the team
  • Recent commits on main (last 24-48h)
  • Any chat threads the loop has visibility into
  • The current state file (what the loop already knows about)

Output Format

Produce a markdown report with these sections:

1. High-Priority Items (act on these)
  • Clear, one-line description
  • Why it matters (impact, risk, or customer pain)
  • Suggested next action for the loop (for example, "draft minimal fix in isolated worktree")
  • Rough effort estimate
2. Watch Items (monitor, do not act yet)
  • Same format but lower urgency
3. Noise / Ignore
  • Brief list of things the loop looked at and decided were not worth action
4. State Updates
  • Any facts the loop should remember for the next run (for example, "PR #1234 now has 2 approvals")

Rules

  • Be brutally concise. The loop and the human reading the state will thank you.
  • Only put something in "High-Priority" if a reasonable engineer would want to know about it today.
  • When in doubt, put it in Watch or Noise rather than creating work.
  • Never propose architectural overhauls during triage — this skill is for signal, not invention.
  • Respect the project's existing skills and conventions (they will be provided in context).

Example Invocation (in an opencode loop)

bash
opencode run "Call loop-triage and append high-priority items to STATE.md. Do not edit code."

The triage skill should be the "eyes" of the loop. Keep it focused and honest.

© cobusgreyling, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in starters/minimal-loop-opencode/skills/loop-triage of cobusgreyling/loop-engineering.

Open the folder on GitHubat commit 87c5e9c

Compare with similar skills

Loop Triage Report next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Loop Triage Report compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Loop Triage Report this skillcobusgreyling/loop-engineering11k—~500Automated safety check: PassMIT
Google Cloud Filestore Autoscalegoogle/skills21k—~3.2kAutomated safety check: PassApache-2.0
A2ui Issue Triagea2ui-project/a2ui17k—~1.5kAutomated safety check: PassApache-2.0
Kubernetes Network Root Cause Analysiskubeshark/kubeshark12k—~5.3kAutomated safety check: PassApache-2.0
UModel Root Cause Analysisalibaba/UnifiedModel412—~1.9kAutomated safety check: PassCustom licence
GitHub Workflow AutomationFNOSP/FlyNarwhal4958 repos~5.4kAutomated safety check: PassAGPL-3.0

Similar skills

  • Google Cloud Filestore Autoscale

    google/skills

    Official

    Inspects Filestore capacity and utilization on Google Cloud, evaluates storage scaling rules, and performs capacity autoscaling (scale UP for low free space or scale DOWN for cost optimization).

    21k GitHub stars~3.2k tokensUpdated today
    DevOps & CloudAuto-check passed

  • A2ui Issue Triage

    a2ui-project/a2ui

    Automates the triage of GitHub issues in the A2UI repository.

    17k GitHub stars~1.5k tokensUpdated today
    DevelopmentAuto-check passed

  • Kubernetes Network Root Cause Analysis

    kubeshark/kubeshark

    Investigates past Kubernetes incidents from Kubeshark traffic snapshots: takes captures, dissects API calls, extracts PCAPs and compares traffic over time.

    12k GitHub stars~5.3k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

  • UModel Root Cause Analysis

    alibaba/UnifiedModel

    Investigates a service incident to its root cause by querying a UModel object graph alongside metrics, logs, topology and recent deployments.

    412 GitHub stars~1.9k tokensUpdated 15 days ago
    DevOps & CloudAuto-check passed

  • GitHub Workflow Automation

    FNOSP/FlyNarwhal

    Automate GitHub workflows with AI assistance. An agent skill from FNOSP/FlyNarwhal.

    495 GitHub starsUsed in 8 repos~5.4k tokens
    DevOps & CloudAuto-check passed

  • Learnings

    kortix-ai/suna

    The project's episodic memory: a timestamped ledger of rules paid for with real outages and near-misses, one entry per incident.

    20k GitHub stars~1.1k tokensUpdated today
    DevOps & CloudAuto-check passed

More from cobusgreyling/loop-engineering

All 21 skills in this repo

  • Install Loop Engineering

    cobusgreyling/loop-engineering

    Installs Loop Engineering into a project through the single @cobusgreyling/loop CLI, scaffolding a report-only loop and a readiness score.

    11k GitHub starsUsed in 1 repo~648 tokens
    Auto-check passed

  • Loop Constraints Enforcer

    cobusgreyling/loop-engineering

    Loads a project's loop-constraints.md before any other action and blocks pushes, edits or merges that violate the rules it defines.

    11k GitHub starsUsed in 1 repo~475 tokens
    Auto-check: notes

  • Release Notes Drafter

    cobusgreyling/loop-engineering

    Turns a structured list of changes from changelog-scan into a categorized, user-facing release notes draft file, and never publishes anything.

    11k GitHub stars~555 tokensUpdated today
    Auto-check passed

  • Issue Triage Loop

    cobusgreyling/loop-engineering

    Scans open GitHub issues and discussions, flags duplicates, scores priority and proposes labels into issue-triage-state.md without ever labeling or closing.

    11k GitHub stars~522 tokensUpdated today
    Auto-check passed

  • Loop Token Budget Guard

    cobusgreyling/loop-engineering

    Check token budget and run-log spend before and after a loop run. Enforces early exit when over budget or when there is no actionable work.

    11k GitHub starsUsed in 1 repo~376 tokens
    Auto-check passed

  • PR Review Triage

    cobusgreyling/loop-engineering

    Tracks open pull requests and records CI state, staleness, merge conflicts and unanswered review comments in a state file, then lists the top three actions for a human.

    11k GitHub stars~480 tokensUpdated today
    Auto-check passed

Categories

Questions about Loop Triage Report

What does Loop Triage Report do?

Turns CI failures, open issues, recent commits and chat threads into a prioritized markdown report that an automation loop can act on without inventing architecture work. Given recent CI and test failures, open tickets, commits from the last day or two, any chat threads the loop can see, and its current state file, the skill produces a four-section report: high-priority items worth acting on today, each with a one-line description, why it matters, a suggested next action such as drafting a minimal fix in an isolated worktree, and a rough effort estimate; lower-urgency watch items in the same format; a short list of things looked at and judged not worth action; and state updates, facts the loop should remember for its next run.

When should I use Loop Triage Report?

Loop Triage Report fits situations like: summarizing recent CI failures, issues and commits for an automation loop; deciding what a loop should act on today versus just watch; writing structured state updates for the next loop run; filtering signal from noise before a loop drafts a fix.

How do I install Loop Triage Report in Claude Code?

Run `npx skills add cobusgreyling/loop-engineering --skill loop-triage -a claude-code`. Or copy the skill folder (starters/minimal-loop-opencode/skills/loop-triage in cobusgreyling/loop-engineering) into .claude/skills/loop-triage in your project. Claude Code loads it when a task matches its description.

How do I install Loop Triage Report in Codex?

Run `npx skills add cobusgreyling/loop-engineering --skill loop-triage -a codex`. Or copy the skill folder (starters/minimal-loop-opencode/skills/loop-triage in cobusgreyling/loop-engineering) into .agents/skills/loop-triage in your project. Codex loads it when a task matches its description.

Can I use Loop Triage Report in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cobusgreyling/loop-engineering --skill loop-triage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/loop-triage, .gemini/skills/loop-triage, .github/skills/loop-triage and .opencode/skills/loop-triage in your project.

What does Loop Triage Report need to run?

Going by SKILL.md and its folder, Loop Triage Report needs the command-line tools its instructions call (opencode). Our summary lists: Access to recent CI results, issues, commits and the loop's current state file.

Does Loop Triage Report access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Loop Triage Report safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Loop Triage Report use?

Loop Triage Report is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Loop Triage Report use?

About 500 tokens (SKILL.md is roughly 2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Loop Triage Report?

Skills that share tags, products or a category with Loop Triage Report: Google Cloud Filestore Autoscale (google/skills, 21k stars), A2ui Issue Triage (a2ui-project/a2ui, 17k stars), Kubernetes Network Root Cause Analysis (kubeshark/kubeshark, 12k stars) and UModel Root Cause Analysis (alibaba/UnifiedModel, 412 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Loop Triage Report?

cobusgreyling (a GitHub user) maintains it in cobusgreyling/loop-engineering, which has 11,440 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 8, 2026.

Source: cobusgreyling/loop-engineering on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.