Skip to content
mcp/skillhub

Agent Skill

GitHub Triage skill

github-triagetrailofbits/skillsplugins/github-triage/skills/github-triage/SKILL.md

Triages a repository's open GitHub issues and pull requests via the gh CLI. Optionally reviews and merges ready PRs — incrementally merging passing automated/bot PRs and maintainer-approved ones, and spawning review subagents for never-reviewed ones — then closes already-resolved issues with comments citing the resolving PR or commit, cross-links issues with their pending fix PRs, and assigns local-only priority and change-size estimates for everything outstanding. Use when triaging, grooming, or reviewing a repository's open issues and PRs.

7.7kCC-BY-SA-4.0

always on

112 tokname + description

once used

5,718 tokSKILL.md body

bundled files

36 KB

repo stars

7.7kGitHub

Install the GitHub Triage skill

Skills CLI (Claude Code, Codex, Cursor and others)

npx skills add https://github.com/trailofbits/skills --skill github-triage

Claude Code, by hand (all projects)

git clone --depth 1 https://github.com/trailofbits/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -R /tmp/skills/plugins/github-triage/skills/github-triage ~/.claude/skills/github-triage

For one project only, copy the folder into .claude/skills/ in that project instead. It is marked disable-model-invocation, so the agent won't pick it on its own: you run it as /github-triage.

What it costs your context

Agent Skills load in three steps. Tokens counted with the o200k tokenizer; your model's count will differ a little.

WhenWhat loadsCost
Every sessionName and description112 tok
When the agent uses itThe SKILL.md instructions5,718 tok
Only if opened3 bundled files (6 KB)varies

Until it is used, github-triage costs about 12× less than the median MCP server we measured (1,362 tokens on every turn). Installing all 97 skills from trailofbits/skills would load 7,555 tokens of descriptions. Skills vs MCP study

Checks

  • The instructions are over 5,000 tokens, the Agent Skills specification's guideline for SKILL.md.

Pre-approved tools (allowed-tools): Bash, Read, Grep, Agent, AskUserQuestion, Write. The agent can use these without asking while the skill is active.

Checked 2026-10-22 · method

What's inside

The headings of its SKILL.md. Read the full file on GitHub.

  • GitHub Triage
  • When to Use
  • When NOT to Use
  • Core Principles
  • Workflow
  • Phase 0: Select the target repository
  • Phase 1: Gather issues and context
  • Phase 2: Triage open pull requests (optional)
  • Phase 3: Classify each open issue
  • Phase 4: Score outstanding issues (LOCAL ONLY)
  • GATE 1: Present the full triage for review
  • Phase 5: Execute approved issue writes
  • Phase 6: Deliver the outstanding triage
  • Safety Rules
  • Rationalizations to Reject

More skills from trailofbits/skills

All skills in this repo
  1. address-sanitizertrailofbits/skills

    Builds and runs code under AddressSanitizer to catch buffer overflows, use-after-free, and other memory errors during fuzzing or tests. Covers -fsanitize=address builds, ASAN_OPTIONS, reading the crash report, LeakSanitizer, and the overhead and platform trade-offs. Use when fuzzing C/C++ or Rust that has unsafe blocks or FFI, when debugging a memory corruption crash, or when reading an ASan stack trace.

    7.7k97 tok idle · 2,723 in use
  2. adjudicate-regressiontrailofbits/skills

    Use when deciding whether source and live reproduction evidence establish a new regression or an exclusion.

    7.7k23 tok idle · 505 in use
  3. aflpptrailofbits/skills

    Sets up and runs AFL++ for multi-core fuzzing of C/C++ projects built with afl-clang-fast or afl-gcc-fast. Covers instrumentation modes, parallel main and secondary campaigns, persistent mode, corpus minimization, and crash triage. Use when scaling fuzzing across cores, fuzzing a mature C/C++ codebase, reading the afl-fuzz status screen, or moving on after libFuzzer has plateaued.

    7.7k91 tok idle · 5,638 in use
  4. agentic-actions-auditortrailofbits/skills

    Audits GitHub Actions workflows for security vulnerabilities in AI agent integrations including Claude Code Action, Gemini CLI, OpenAI Codex, and GitHub AI Inference. Detects attack vectors where attacker-controlled input reaches AI agents running in CI/CD pipelines, including env var intermediary patterns, direct expression injection, dangerous sandbox configurations, and wildcard user allowlists. Use when reviewing workflow files that invoke AI coding agents, auditing CI/CD pipeline security for prompt injection risks, or evaluating agentic action configurations.

    7.7k105 tok idle · 4,775 in use
  5. Scans Algorand smart contracts for 11 common vulnerabilities including rekeying attacks, unchecked transaction fees, missing field validations, and access control issues. Use when auditing Algorand projects (TEAL/PyTeal).

    7.7k54 tok idle · 2,979 in use
  6. atheristrailofbits/skills

    Sets up and runs Atheris, the coverage-guided Python fuzzer built on libFuzzer. Covers TestOneInput harnesses, FuzzedDataProvider, instrumenting both pure Python and native C extensions, and running under AddressSanitizer. Use when fuzzing a Python package, hunting memory corruption in a Python C extension, or choosing between Atheris and Hypothesis for a Python target.

    7.7k86 tok idle · 3,559 in use
  7. audit-augmentationtrailofbits/skills

    Augments Trailmark code graphs with external audit findings from SARIF static analysis results, weAudit annotation files, and version-gated Trailmark 0.4.x binary-analysis graph exports. Maps findings to graph nodes by file and line overlap, creates severity-based subgraphs, and enables cross-referencing findings with pre-analysis data (blast radius, taint, etc.). Use when projecting SARIF results onto a code graph, overlaying weAudit annotations, importing binary graph findings, cross-referencing Semgrep, CodeQL, or binary-analysis findings with call graph data, or visualizing audit findings in the context of code structure.

    7.7k130 tok idle · 2,108 in use
  8. audit-context-buildingtrailofbits/skills

    Understand a codebase before looking for bugs in it - what each function assumes, what it guarantees, and what it depends on elsewhere. Use when starting an audit, threat model, or architecture review on unfamiliar code, and before any vulnerability-hunting pass.

    7.7k55 tok idle · 797 in use