$ ~/registry/skill/microsoft-packages-apm-triage-panel

SKILL

apm-triage-panel

Name: apm-triage-panel
Author: microsoft

Triage microsoft/apm issues and produce one unified resolution comment.

Stars

★ 3,163

Source

GitHub

Updated

2026-07-10

// securityLow risk

Prompt only, no code
Open source
Community-trusted· 3.2k

Running security audit…

Credentials
Network egress
Code execution
Data access
Supply chain

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "apm-triage-panel" skill from askskill:
1. Download https://raw.githubusercontent.com/microsoft/apm/main/packages/apm-triage-panel/SKILL.md
2. Save it as ~/.claude/skills/apm-triage-panel/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// examples

Triage a newly opened bug

Prompt

Please triage this newly opened issue in microsoft/apm and output one synthesized comment with the triage decision, recommended labels, milestone, and next action.

Expected

A publish-ready triage comment stating whether to accept it, which labels to apply, the milestone, and the recommended next step.

Handle a reopened issue

Prompt

Please triage this reopened microsoft/apm issue and provide a single comment with the decision, label set, milestone, and suggested action based on the context.

Expected

A single comment integrating prior discussion and current status to guide maintainers to fix, request more info, or close it.

Resolve needs-triage items

Prompt

Please triage this microsoft/apm issue labeled status/needs-triage and produce a final triage comment covering the decision, labels, milestone, and next-step recommendation.

Expected

A clearly structured triage result that helps the team finalize labels and assign follow-up work quickly.

// docs

APM Triage Panel -- Single-Issue Triage Orchestration

The panel is fixed at 3 mandatory specialist lenses + up to 3 conditional lenses + 1 arbiter lens = up to 6 active persona sections in one triage comment (3 mandatory + 3 conditional). You play each lens in turn from inside a single agent loop (progressive-disclosure skill model -- no sub-agent dispatch). Routing chooses which lenses execute; it never changes which headings appear in the final comment.

This skill mirrors the apm-review-panel orchestration shape on purpose. Same single-comment discipline, same completeness gate, same persona-pass procedure -- only the personas, the rubric, and the output template differ.

Agent roster

Agent	Persona	Always active?
DevX UX Expert	User-Need Reviewer	Yes
Supply Chain Security Expert	Risk-Surface Reviewer	Yes
APM CEO	Triage Arbiter	Yes (always arbitrates)
OSS Growth Hacker	Contributor-Tone Reviewer	Conditional (see below)
Python Architect	Architecture Reviewer	Conditional (see below)
Doc Writer	Documentation Reviewer	Conditional (see below)

Skipped by default: CLI Logging Expert, Auth Expert. Triage operates on issue intent, not on diffs -- those personas are invoked downstream by apm-review-panel once a PR exists.

Routing topology

   devx-ux-expert      supply-chain-security-expert
        \_______________________/
                    |
                    |   <-- python-architect (conditional; design /
                    |       architecture / new primitive / new schema)
                    |
                    |   <-- doc-writer (conditional; docs work or
                    |       user-facing change that needs new doc pages)
                    v
                apm-ceo               <----  oss-growth-hacker
           (final call / arbiter)           (conditional; tunes tone
                                             when author is new)

Specialists raise findings independently -- no implicit consensus.
CEO arbitrates the theme, milestone, priority, and tone of the reply. CEO has the final call on the decision rubric.
Growth Hacker, Python Architect, and Doc Writer are side-channels to the CEO when activated. They never block a specialist finding; they feed the CEO's arbitration:
- Growth Hacker tunes the comment's tone for first-time and low-interaction contributors.
- Python Architect flags feasibility and cross-cutting impact, and pushes the decision toward status/needs-design when warranted.
- Doc Writer flags whether docs work is implied and whether the suggested comment wording is grounded in the user vocabulary used in the README and guides.

Conditional panelists

Three personas are conditional: OSS Growth Hacker, Python Architect, and Doc Writer. Each follows the same shape: an explicit YES/NO activation rule plus an inactive-reason fallback. Maximum lenses in a single triage = 6 (3 mandatory + 3 conditional).

OSS Growth Hacker

Activate oss-growth-hacker if either rule below matches.

Fast-path author trigger. Activate the Growth Hacker lens immediately when the issue's author meets ANY of:
- GitHub author_association is FIRST_TIME_CONTRIBUTOR, FIRST_TIMER, or NONE against microsoft/apm.
- Author has fewer than 3 prior interactions (issues + PRs + comments) on microsoft/apm.
- Issue body explicitly says "first issue", "new to APM", or similar.
Fallback self-check. If author signals are ambiguous, answer this before activating the lens:

Would the warmth, framing, or pointer-set in the reply meaningfully

…

View full docs ↗

Analyze GitHub and Discord signals to prioritize project maintainer attention.

openclawGet→

$ loading_