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.

73

Quality

91%

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

82%Weight 40%Scale 1-3

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

The content is a well-structured orchestrator: concrete commands, clear phased workflow with validation checkpoints, and clean one-level-deep progressive disclosure into real bundled assets. The main weakness is verbosity from restating invariants across sections.

Suggestions

Collapse the 'Architecture invariants' section so each invariant is stated once and referenced from phases, removing the duplicated worktree/one-writer/fold-by-default prose in Phase 4-5.

Inline-expand or footnote the B-series acronyms (A11, B4, B5, B12, B14b/c, B15/B16) on first use so the body is self-contained without model-routing.md.

DimensionReasoningScore

Conciseness

Mostly efficient and every section maps to a phase or invariant, but the body is long and re-states architecture invariants (e.g. worktree/one-writer rules, fold-by-default) in both prose and phase steps, and repeats B-invariant acronyms (A11, B4, B5, B12) that a reader must cross-reference.

2 / 3

Actionability

Provides concrete executable commands: dependency probes (`test -f ... && echo ...`), `gh issue list`, `git worktree add`, `git -C <row-worktree> merge-base ...`, the `uv run python .../owner_touch_gate.py verify ...` gate command, and named asset prompts/schemas loaded per phase.

3 / 3

Workflow Clarity

Seven phases (0-7) are explicitly sequenced with reload-at-boundary checkpoints, validation gates (schema-validate triage returns, two-gate verify before terminal state, wave-gate re-plan cap), and explicit retry/re-spawn policies for failures.

3 / 3

Progressive Disclosure

Body is an overview that offloads detail to one-level-deep asset references (all 19 assets in ./assets/ are real files and each is linked with a one-line purpose), with sibling skills probed before composition rather than inlined.

3 / 3

Total

11

/

12

Passed

Description

100%Weight 40%Scale 1-3

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, trigger-rich, and answers both what and when with explicit invocation guidance. It is dense but every clause carries capability or trigger information. No suggestions needed.

DimensionReasoningScore

Specificity

Names many concrete actions: 'drive any open microsoft/apm issue (bug, feature, docs, refactor, perf) from raw intake to a mergeable PR', 'Run the apm-triage-panel rubric per issue first', 'present ONE consolidated triage review', 'escalate to the maintainer BY DEFAULT', and 'drive each accepted PR to mergeability ... via the shepherd-driver loop'.

3 / 3

Completeness

Explicitly answers what (intake-to-mergeable-PR orchestration with triage gate, escalate-by-default, shepherd-driver convergence) and when ('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...').

3 / 3

Trigger Term Quality

Covers natural terms a user would say -- 'auto-tackle the issue queue', 'clear the backlog to PRs', 'run issues to merge', 'issue list or queue', 'backlog' -- with the deliberate note to activate 'even if "autopilot" is not named'.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (microsoft/apm batch issue autopilot with manual-only invocation and explicit never-by-label/event constraint) and names the specific sibling skills it composes, making conflict with generic issue skills unlikely.

3 / 3

Total

12

/

12

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.