Setup Matt Pocock Skills
bestofjs/bestofjs
Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout.
Provides issue triage workflow, priority definitions, and report format.
Install Triaging Issues
$ npx skills add microsoft-foundry/foundry-agent-webapp --skill triaging-issues -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install microsoft-foundry/foundry-agent-webapp triaging-issues --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/microsoft-foundry/foundry-agent-webapp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/triaging-issues .claude/skills/triaging-issues && rm -rf skills-srcUse ~/.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/
Install the "triaging-issues" agent skill from https://github.com/microsoft-foundry/foundry-agent-webapp/tree/main/.github/skills/triaging-issues into .claude/skills/triaging-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triaging-issues", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/microsoft-foundry/foundry-agent-webapp/tree/main/.github/skills/triaging-issuesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add microsoft-foundry/foundry-agent-webapp --skill triaging-issues -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install microsoft-foundry/foundry-agent-webapp triaging-issues --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft-foundry/foundry-agent-webapp.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/triaging-issues .agents/skills/triaging-issues && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "triaging-issues" agent skill from https://github.com/microsoft-foundry/foundry-agent-webapp/tree/main/.github/skills/triaging-issues into .agents/skills/triaging-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triaging-issues", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add microsoft-foundry/foundry-agent-webapp --skill triaging-issues -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install microsoft-foundry/foundry-agent-webapp triaging-issues --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft-foundry/foundry-agent-webapp.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/triaging-issues .cursor/skills/triaging-issues && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "triaging-issues" agent skill from https://github.com/microsoft-foundry/foundry-agent-webapp/tree/main/.github/skills/triaging-issues into .cursor/skills/triaging-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triaging-issues", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/microsoft-foundry/foundry-agent-webapp.git --path .github/skills/triaging-issues--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add microsoft-foundry/foundry-agent-webapp --skill triaging-issues -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install microsoft-foundry/foundry-agent-webapp triaging-issues --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft-foundry/foundry-agent-webapp.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/triaging-issues .gemini/skills/triaging-issues && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "triaging-issues" agent skill from https://github.com/microsoft-foundry/foundry-agent-webapp/tree/main/.github/skills/triaging-issues into .gemini/skills/triaging-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triaging-issues", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install microsoft-foundry/foundry-agent-webapp triaging-issuesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add microsoft-foundry/foundry-agent-webapp --skill triaging-issues -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/microsoft-foundry/foundry-agent-webapp.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/triaging-issues .github/skills/triaging-issues && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "triaging-issues" agent skill from https://github.com/microsoft-foundry/foundry-agent-webapp/tree/main/.github/skills/triaging-issues into .github/skills/triaging-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triaging-issues", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add microsoft-foundry/foundry-agent-webapp --skill triaging-issues -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install microsoft-foundry/foundry-agent-webapp triaging-issues --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft-foundry/foundry-agent-webapp.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/triaging-issues .opencode/skills/triaging-issues && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "triaging-issues" agent skill from https://github.com/microsoft-foundry/foundry-agent-webapp/tree/main/.github/skills/triaging-issues into .opencode/skills/triaging-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triaging-issues", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
triaging-issues- GitHub stars
- 127
- Token cost
- ~670 tokens
- SKILL.md length
- 251 words
- Files
- 1
- Skills in repo
- 19
- Repo updated
- First seen
- Licence
- MIT
At a glance
Provides issue triage workflow, priority definitions, and report format.
- Works in 3 steps: Use gh issue list --search "" with key… → Check closed issues too: gh issue list… → If a duplicate exists, note it in the…
- Analyzing GitHub issues and PRs
- SKILL.md covers Priority Definitions, Complexity Scale, Label Taxonomy and Triage Report Format, plus 3 more sections
- Calls gh
What it does
Triaging Issues is an agent skill from microsoft-foundry/foundry-agent-webapp. Provides issue triage workflow, priority definitions, and report format. Use when analyzing GitHub issues and PRs, assessing priority, or generating triage reports.
Its SKILL.md is about 670 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Issue triage. It works with GitHub. The repository describes itself as: GitHub Copilot enabled repo for building and deploying a web application with Entra ID authentication and integrated with Azure AI Foundry Agents. The licence is MIT.
When your agent uses it
- Analyzing GitHub issues and PRs
- Assessing priority
- Generating triage reports
Example prompts
- “Use the triaging-issues skill to provide issue triage workflow, priority definitions, and report format”
- “/triaging-issues”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Use gh issue list --search "" with key terms from the issue title and body.
- Check closed issues too: gh issue list --state closed --search "".
- If a duplicate exists, note it in the triage report with a cross-reference.
What it can do on your machine
Read from SKILL.md and the folder at commit f6cb362. 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:
gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
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
Triaging Issues loads about 670 tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 251 words of instructions outside code blocks.
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 microsoft-foundry/foundry-agent-webapp at commit f6cb362, republished under its MIT licence (© microsoft-foundry). 251 words, ~670 tokens.
Download SKILL.mdSave it as
.claude/skills/triaging-issues/SKILL.md (or your agent's skills folder).- name
- triaging-issues
- description
- Provides issue triage workflow, priority definitions, and report format. Use when analyzing GitHub issues and PRs, assessing priority, or generating triage reports.
Issue Triage Guidance
Gather open issues and PRs, analyze them, and recommend next steps. Search the codebase to identify affected components — don't rely on hardcoded file mappings.
Priority Definitions
| Priority | Criteria |
|---|---|
| 🔴 Critical | Production broken, security issue, data loss |
| 🟠 High | Major feature broken, blocking users |
| 🟡 Medium | Feature degraded, workaround exists |
| 🟢 Low | Minor issue, cosmetic, nice-to-have |
Complexity Scale
| Size | Estimate |
|---|---|
| S | Hours |
| M | 1-2 days |
| L | 3-5 days |
| XL | 1+ week |
Label Taxonomy
| Prefix | Values |
|---|---|
area: | backend, frontend, auth, streaming, infra, docs |
type: | bug, feature, enhancement, chore, docs |
priority: | critical, high, medium, low |
Triage Report Format
Open Issues Summary
| # | Title | Priority | Type | Complexity |
|---|
Per Issue — #[number]: [title]
- Priority / Type / Complexity
- Affected Areas: checklist of areas
- Relevant Files: table with file + reason
- Suggested Labels: using taxonomy above
- Recommended Next Steps: numbered list
Open PRs Summary
| # | Title | Author | Status | Files Changed |
|---|
Per PR — #[number]: [title]
- Status: Draft | Ready for review | Changes requested | Approved
- Review Notes: concerns or things to check
gh CLI Commands for Read-Only Analysis
# List open issues
gh issue list --state open
# Search for potential duplicates
gh issue list --search "keyword"
# View issue details
gh issue view <number>
# List open PRs
gh pr list --state open
# View PR details and diff
gh pr view <number>
gh pr diff <number>Duplicate Detection
Before deep-diving into an issue, search for duplicates:
- Use
gh issue list --search "<keywords>"with key terms from the issue title and body. - Check closed issues too:
gh issue list --state closed --search "<keywords>". - If a duplicate exists, note it in the triage report with a cross-reference.
Constraints
- ❌ Read-only — do NOT modify issues or PRs
- ❌ No
gh issue edit,gh issue close,gh issue label - ❌ No
gh pr merge,gh pr close,gh pr review --approve - ✅ Only use read commands:
list,view,search,diff
© microsoft-foundry, 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 .github/skills/triaging-issues of microsoft-foundry/foundry-agent-webapp.
Open the folder on GitHubat commit f6cb362
Compare with similar skills
Triaging Issues 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Triaging Issues this skillmicrosoft-foundry/foundry-agent-webapp | 127 | — | ~670 | Automated safety check: Pass | MIT | |
| Setup Matt Pocock Skillsbestofjs/bestofjs | 3.1k | 20 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Windows App SDK Issue Triage Reportmicrosoft/WindowsAppSDK | 4.7k | — | ~3.4k | Automated safety check: Pass | Apache-2.0 | |
| Exposed Bug Fix WorkflowJetBrains/Exposed | 9.3k | — | ~3.8k | Automated safety check: Pass | Apache-2.0 | |
| Pre-Release PR Triagejamiepine/voicebox | 57k | — | ~3.1k | Automated safety check: Pass | MIT | |
| WinAppSDK Triage Meeting Prepmicrosoft/WindowsAppSDK | 4.7k | — | ~2.8k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Windows App SDK Issue Triage Report
microsoft/WindowsAppSDK
Generates GitHub Feature Area Status reports for the Windows App SDK repository, scoring issues so teams can see what needs attention in each area.
- Official
Exposed Bug Fix Workflow
JetBrains/Exposed
Takes a GitHub or YouTrack issue for the Exposed project through reproduction, a failing test, a fix, validation and a pull request.
Pre-Release PR Triage
jamiepine/voicebox
Sorts a backlog of open pull requests into must-merge, candidate, superseded and deferred, writes a triage doc and works the merge loop before a release.
- Official
WinAppSDK Triage Meeting Prep
microsoft/WindowsAppSDK
Prepares the triage meeting summary for WinAppSDK Needs-Triage issues, with research-backed area suggestions, draft replies and a diff since the last triage.
A2ui Issue Triage
a2ui-project/a2ui
Automates the triage of GitHub issues in the A2UI repository.
More from microsoft-foundry/foundry-agent-webapp
All 19 skills in this repoCommitting Code
microsoft-foundry/foundry-agent-webapp
Provides commit message format and workflow for this repository.
Implementing Chat Streaming
microsoft-foundry/foundry-agent-webapp
Provides SSE streaming patterns for the chat API and frontend.
Planning Features
microsoft-foundry/foundry-agent-webapp
Provides structured plan template for feature implementation.
Researching Azure AI SDK
microsoft-foundry/foundry-agent-webapp
Provides research patterns for Foundry Agent Service SDK. An agent skill from microsoft-foundry/foundry-agent-webapp.
Deploying To Azure
microsoft-foundry/foundry-agent-webapp
Provides deployment commands and troubleshooting for Azure Container Apps.
Syncing MCP Servers
microsoft-foundry/foundry-agent-webapp
Synchronize MCP server configuration between VS Code (.vscode/mcp.json) and Copilot CLI (~/.copilot/mcp-config.json).
Related
Works with
Categories
Questions about Triaging Issues
What does Triaging Issues do?
Provides issue triage workflow, priority definitions, and report format. Triaging Issues is an agent skill from microsoft-foundry/foundry-agent-webapp. Provides issue triage workflow, priority definitions, and report format.
When should I use Triaging Issues?
Triaging Issues fits situations like: analyzing GitHub issues and PRs; assessing priority; generating triage reports.
How do I install Triaging Issues in Claude Code?
Run `npx skills add microsoft-foundry/foundry-agent-webapp --skill triaging-issues -a claude-code`. Or copy the skill folder (.github/skills/triaging-issues in microsoft-foundry/foundry-agent-webapp) into .claude/skills/triaging-issues in your project. Claude Code loads it when a task matches its description.
How do I install Triaging Issues in Codex?
Run `npx skills add microsoft-foundry/foundry-agent-webapp --skill triaging-issues -a codex`. Or copy the skill folder (.github/skills/triaging-issues in microsoft-foundry/foundry-agent-webapp) into .agents/skills/triaging-issues in your project. Codex loads it when a task matches its description.
Can I use Triaging Issues 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 microsoft-foundry/foundry-agent-webapp --skill triaging-issues -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/triaging-issues, .gemini/skills/triaging-issues, .github/skills/triaging-issues and .opencode/skills/triaging-issues in your project.
What does Triaging Issues need to run?
Going by SKILL.md and its folder, Triaging Issues needs the command-line tools its instructions call (gh).
Does Triaging Issues access the network?
SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Triaging Issues 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 Triaging Issues use?
Triaging Issues 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 Triaging Issues use?
About 670 tokens (SKILL.md is roughly 2.7k 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 Triaging Issues?
Skills that share tags, products or a category with Triaging Issues: Setup Matt Pocock Skills (bestofjs/bestofjs, 3.1k stars), Windows App SDK Issue Triage Report (microsoft/WindowsAppSDK, 4.7k stars), Exposed Bug Fix Workflow (JetBrains/Exposed, 9.3k stars) and Pre-Release PR Triage (jamiepine/voicebox, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Triaging Issues?
microsoft-foundry (a GitHub organization) maintains it in microsoft-foundry/foundry-agent-webapp, which has 127 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on April 21, 2026.
Source: microsoft-foundry/foundry-agent-webapp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.