Ops Triage

What it does

When your agent uses it

• Asks to sentry issues

Example prompts

• “sentry issues”
• “triage github”
• “/ops-triage”

Requirements

• A credential in SENTRY_AUTH_TOKEN
• A credential in LINEAR_API_KEY
• Pre-approved tools (allowed-tools): Bash, Read, Grep, Glob, Skill, Agent, AskUserQuestion, TeamCreate, SendMessage, TaskCreate, TaskUpdate, TaskList, WebFetch, WebSearch, LSP, mcp__plugin_sentry_sentry__search_issues, mcp__plugin_sentry_sentry__get_sentry_resource, mcp__linear__list_issues, mcp__linear__update_issue, mcp__linear__get_issue, mcp__linear__list_teams

Workflow steps

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

1. 1Gather issues in parallel
2. 2Cross-reference against code
3. 3Confirm and resolve fixed issues
4. 4Present triage board

What it can do on your machine

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

• Tool permissions

  Pre-approves these tools, so the agent can use them without asking each time:

  • Bash
  • Read
  • Grep
  • Glob
  • Skill
  • Agent
  • AskUserQuestion
  • TeamCreate
  • SendMessage
  • TaskCreate

  …and 11 more on the same allowed-tools line.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Shell commands in SKILL.md call:

  • gh
  • curl
  • jq
  • git

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

• Network

  Hosts in commands or code, which the agent is likely to contact:

  • sentry.io
  • api.linear.app

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

• Credentials

  Names these keys or tokens, usually read from environment variables:

  • SENTRY_AUTH_TOKEN
  • CLAIM_KEY
  • LINEAR_API_KEY
  • GITHUB_TOKEN

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

Context cost

Ops Triage loads about 2.7k tokens when it runs. Until then it costs about 28 tokens; SKILL.md has 796 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~28

When it runs · the whole SKILL.md, loaded when a task matches

~2.7k

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

• NotePre-approves every shell command (allowed-tools: Bash)SKILL.md

  allowed-tools: Bash, Read, Grep, Glob, Skill, Agent, AskUserQuestion, TeamCreate, SendMessage, TaskCreate, TaskUpda

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 Lifecycle-Innovations-Limited/claude-ops at commit ee9c784, republished under its MIT licence (© Lifecycle-Innovations-Limited). 796 words, ~2,680 tokens.

name

ops-triage

description

OPS on-demand: This skill should be used when the user asks to "sentry issues", "triage github", or…

allowed-tools

Bash, Read, Grep, Glob, Skill, Agent, AskUserQuestion, TeamCreate, SendMessage, TaskCreate, TaskUpdate, TaskList, WebFetch, WebSearch, LSP, mcp__plugin_sentry_sentry__search_issues, mcp__plugin_sentry_sentry__get_sentry_resource, mcp__linear__list_issues, mcp__linear__update_issue, mcp__linear__get_issue, mcp__linear__list_teams

argument-hint

[project-alias|sentry|linear|github|all]

effort

high

maxTurns

40

TeamCreate("triage-fixers")
Agent(team_name="triage-fixers", name="fix-[issue-id]", subagent_type="ops:triage-agent", ...)

gh issue list --state open --json number,title,body,labels,assignees,createdAt,url --limit 50 2>/dev/null

REGISTRY="${CLAUDE_PLUGIN_ROOT}/scripts/registry.json"
[ -f "$REGISTRY" ] || REGISTRY="${CLAUDE_PLUGIN_ROOT}/scripts/registry.example.json"
for repo in $(jq -r '.projects[] | select(.gsd == true) | .repos[]' "$REGISTRY" 2>/dev/null); do
  echo "=== $repo ==="
  gh issue list --repo "$repo" --state open --json number,title,labels,createdAt --limit 20 2>/dev/null
done

Found N issues confirmed fixed and deployed:

  [Sentry] [title] — fix in [commit], deployed [time ago]
  [Linear] [title] — fix in [commit], deployed [time ago]
  [GitHub] #[N] [title] — referenced in merged PR #[M]

  [Resolve all N]  [Review each one]  [Skip — don't auto-resolve]

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 OPS ► TRIAGE — [date]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

AUTO-RESOLVED (already fixed)
 ✓ [Sentry] [title] — fix in [commit]
 ✓ [Linear] [title] — closed
 ✓ [GitHub] #[N] [title] — closed

ACTIVE ISSUES (needs work)
 CRITICAL  [source] [title] [age] [assigned?]
 HIGH      [source] [title] [age] [assigned?]
 MEDIUM    [source] [title] [age] [assigned?]

──────────────────────────────────────────────────────

  [Dispatch agent for [top critical issue]]
  [Dispatch agent for [second issue]]
  [Assign issue to sprint (Linear)]
  [More...]

  [Bulk-assign all HIGH to current sprint]
  [Done]

CLAIM_KEY="sentry:issue:<short_id>"   # adjust per issue type
ledger query --claim-key "$CLAIM_KEY" --since=-PT24H

# Claim when opening a triage pass on an issue
ledger write \
  --claim-key "$CLAIM_KEY" \
  --kind "fix" \
  --status "in_progress" \
  --title "Triage: <issue title>" \
  --ttl-sec 7200

# Resolve after fix dispatched or issue escalated
ledger write \
  --claim-key "$CLAIM_KEY" \
  --kind "fix" \
  --status "done" \
  --title "Triage: <issue title>" \
  --context "fix dispatched|escalated|snoozed: <reason>"

© Lifecycle-Innovations-Limited, 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 claude-ops/skills/ops-triage of Lifecycle-Innovations-Limited/claude-ops.

Open the folder on GitHubat commit ee9c784