Skip to content
TrustedSkillsbeta
Back to all skills

Github Triage

Checked
code-yeongyu·vlatest·backend

Prioritizes GitHub issues based on labels, assignees, and activity to streamline workflow and focus on critical tasks.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add code-yeongyu/oh-my-openagent --skill github-triage -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

code-yeongyu

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned code-yeongyu/oh-my-opencode at 1b3bb502b8.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
1b3bb502b8
Manifest
.agents/skills/github-triage/SKILL.md
Scanned
4 files, 1,922 lines
Copies in repo
2 — all of them scanned
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The github-triage skill enables AI agents to analyze GitHub repositories, identify issues, and prioritize them based on severity, impact, or other criteria. It can automatically label, categorize, and sort open issues or pull requests, helping maintainers manage their projects more efficiently.

When to use it

  • You need to triage a large number of GitHub issues quickly before a release cycle.
  • Your team is overwhelmed with bug reports and feature requests on GitHub.
  • You want to automate the process of sorting and labeling GitHub issues based on predefined rules or AI analysis.

Key capabilities

  • Automatic issue categorization by type (bug, enhancement, documentation, etc.)
  • Prioritization of issues using severity levels or impact assessment
  • Labeling of issues based on keywords or patterns in their descriptions

Example prompts

  • "Triage all open GitHub issues in the main branch and label them as bug, feature request, or documentation."
  • "Sort the latest 50 GitHub pull requests by priority and assign labels for review status."
  • "Analyze this GitHub repository's issues and highlight those with high impact on user experience."

Tips & gotchas

  • Ensure your AI agent has access to the GitHub API and proper authentication credentials.
  • Custom rules or filters may be needed to fine-tune triage logic based on specific project needs.