CtrlK
BlogDocsLog inGet started
Tessl Logo

apm-issue-autopilot

Use this skill to drive any open microsoft/apm issue (bug, feature, docs, refactor, perf) from raw intake to a mergeable PR with triage as the central, paramount gate. Run the apm-triage-panel rubric per issue first, then present ONE consolidated triage review for the whole batch and escalate to the maintainer BY DEFAULT on any doubt (needs-design, decline, duplicate, defer, auto-handle, breaking- change, auth/security/governance surface, low arbiter confidence, unbounded scope, or a missing brief); only auto-implement clear, bounded, high-confidence accepts the maintainer approved. Then drive each accepted PR to mergeability batch-bug- shepherd style via the shepherd-driver loop: fold copilot + panel follow-ups by default, watch CI green, iterate under a bounded cap. Invoke MANUALLY, in-session, on an issue list or queue -- never by label or event. Activate when the maintainer asks to auto-tackle the issue queue, clear the backlog to PRs, or run issues to merge -- even if "autopilot" is not named.

69

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, action-oriented orchestrator with a clear phased workflow, robust validation gates, and exemplary progressive disclosure via verified bundle files. Its main weakness is conciseness: opaque internal taxonomy tags and repeated escalation prose add avoidable token weight.

Suggestions

Strip the opaque internal codenames (A11, B4, B5, B12, B13, B14b, B14c, B15/B16) or move them to a glossary in a bundled reference; they cost tokens without aiding execution.

Consolidate the repeated 'escalate by default' language (stated in the description, Hard boundaries, Architecture invariants, and Phase 2) into a single canonical statement to reduce redundancy.

Tighten parenthetical asides such as the model-routing.md asset blurb and the routing_receipts note into shorter pointers to the bundled file.

DimensionReasoningScore

Conciseness

The body is mostly efficient orchestration detail, but carries repeated verbose hedging and opaque internal codenames ('A11 RECONCILIATION LOOP', 'B4 PLAN MEMENTO', 'B12 MODEL ROUTER', 'B14b CAVEMAN BRIEF layer', 'B14c audience-boundary PER-SPAWN DECLARATION TABLE', 'B15/B16') that add tokens without aiding execution and could be trimmed.

3 / 5

Actionability

Provides concrete executable commands (gh issue list, git worktree add, gh pr view --json mergeable,mergeStateStatus, the owner_touch_gate.py verify invocation, test -f probe blocks) plus concrete model classes and iteration caps; minor gaps exist where real detail lives in bundled prompts.

4 / 5

Workflow Clarity

Phases 0-7 are clearly sequenced with explicit validation checkpoints (schema-validate triage returns, confidence gate, wave-gate rubric, owner-touch gate before terminal state) and feedback loops (re-plan cap 2, one re-spawn then blocked) for this batch operation — validation is present, so the batch cap does not apply.

5 / 5

Progressive Disclosure

Clear overview with well-signaled one-level-deep references to bundled assets (prompts, schemas, rubrics, templates), every referenced asset file verified present on disk, and a dedicated 'Bundled assets' index; bulk detail is appropriately split out of SKILL.md.

5 / 5

Total

17

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, complete, and distinctive, clearly stating both the capability and the manual activation triggers tied to maintainer requests. It is slightly dense and niche-anchored, which costs a little on broad trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain (microsoft/apm issues) and lists multiple concrete actions: 'run the apm-triage-panel rubric per issue', 'present ONE consolidated triage review', 'escalate to the maintainer BY DEFAULT', 'drive each accepted PR to mergeability ... fold copilot + panel follow-ups', 'watch CI green, iterate under a bounded cap' — comprehensive coverage of specific actions.

5 / 5

Completeness

Explicitly answers both what ('drive any open microsoft/apm issue ... from raw intake to a mergeable PR') and when ('Activate when the maintainer asks to auto-tackle the issue queue, clear the backlog to PRs, or run issues to merge') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural maintainer phrasings ('auto-tackle the issue queue', 'clear the backlog to PRs', 'run issues to merge', 'issue list or queue', 'autopilot') and the issue-type keywords (bug, feature, docs, refactor, perf), but is anchored to a niche internal repo so a few broader synonyms are absent.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (microsoft/apm intake-to-merge orchestrator) and names specific sibling skills (apm-triage-panel, shepherd-driver, batch-bug-shepherd), making it highly distinguishable with minimal conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 8 suspicious

Warning

Total

15

/

16

Passed

Repository
microsoft/apm
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.