CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

autopilot-issue-accept

Use this skill to accept ONE microsoft/apm issue with a declared scope. The canvas Accept button, or a maintainer asking to accept an issue, starts it. Draft only from the latest triage proposed scope, get exact-text approval in this chat from a GOVERNANCE roster human, post that comment as that human, then add status/accepted. Do not invent scope, do not accept pull requests, and do not implement the issue.

Quality

97%

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

96%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 an exceptionally lean, command-driven governance procedure: every step is executable, every write is gated by an explicit re-read or eligibility validation, and failure paths consistently stop rather than guess. Its only structural weakness is that everything lives in one ~170-line file where the activation-card protocol and comment template could be externalized as bundled references.

Suggestions

Move the activation-card template, its field rules, and the exit receipt into a bundled reference file (e.g. references/activation-card.md) and keep a one-line pointer in SKILL.md, since this protocol appears self-contained and likely shared across autopilot skills.

Extract the exact apm-scope:v1 comment format into a short reference file so SKILL.md reads as an overview of the workflow with the template loaded only at post time.

DimensionReasoningScore

Conciseness

The body is telegraphic imperative prose with zero explanation of concepts Claude already knows (no explanation of gh, GitHub labels, or what a scope is) and no padding: "Do not implement the issue. Do not assign. Do not request reviewers." Only one or two safety-motivated duplicated constraints ("do not edit the comment" restated in the failure-handling sentence) could be trimmed, which fits the 5 anchor ('every token earns its place') better than the 4 anchor's 'minor instances of over-explanation'.

5 / 5

Actionability

Quotes: "gh api user --jq '{login:.login,type:.type}'", "gh issue comment \"$ISSUE\" --repo microsoft/apm --body-file \"$BODY\"\"", "node scripts/governance/eligibility.cjs --repo microsoft/apm --issue \"$ISSUE\" --approval-url \"$COMMENT_URL\"\"", "gh issue edit \"$ISSUE\" --repo microsoft/apm --add-label status/accepted". All commands are copy-paste ready, the comment body is given as an exact fence template, variables are anchored ("`COMMENT_URL` is its `html_url`") and edge cases (missing brief, conflict, unclear Area, changed field) each have concrete handling — matching the 5 anchor.

5 / 5

Workflow Clarity

Quotes: the sequence activation card → Draft → Chat approval → Identity → "Post, re-read, then label"; validation checkpoints include the four-bullet re-read checklist ("the body is the approved text", "user.login is the `gh api user` login", "updated_at equals created_at"), the eligibility gate "Require `state: record-present`", and stop conditions ("If that brief is missing, stop", "Any other token, bot, or login -> stop"). A feedback loop exists for changed drafts ("A change to any field... is a new draft. Show the new fence and wait again"), matching the 5 anchor; the destructive/batch cap does not apply because validation is pervasive.

5 / 5

Progressive Disclosure

Sections are clearly headed and linearly navigable, and external dependencies are well signaled with provenance rules ("Read the single `apm-scope-roster` block in `GOVERNANCE.md` on the trusted default branch", eligibility tool "from a trusted default-branch checkout"). However, at ~170 lines in a single file it exceeds the under-50-line case where organized sections alone earn a 5, and the activation-card protocol (~40 lines of card template, rules, and exit receipt) and the exact comment-format spec are self-contained chunks that could be split into bundled reference files — minor organization gaps matching the 4 anchor rather than the 5 anchor's 'content appropriately split' with one-level-deep references.

4 / 5

Total

19

/

20

Passed

Description

100%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 exemplary: it names the exact trigger conditions (canvas Accept button or maintainer request), enumerates the complete action sequence (draft from triage brief, exact-text approval, post, label), states hard exclusions, and is unmistakably scoped to one repo and label. It reads as a model operational description with no fluff or over-claims.

DimensionReasoningScore

Specificity

Quotes: "Draft only from the latest triage proposed scope, get exact-text approval in this chat from a GOVERNANCE roster human, post that comment as that human, then add status/accepted" — the full workflow is enumerated as concrete actions, and exclusions are explicit ("do not accept pull requests, and do not implement the issue"). This lists multiple specific concrete actions with comprehensive coverage, matching the 5 anchor; the 4 anchor ('minor gaps in coverage') fits worse because drafting, approval, posting, labeling, and exclusions are all named.

5 / 5

Completeness

Quotes: what — "Draft only from the latest triage proposed scope... post that comment as that human, then add status/accepted"; when — "The canvas Accept button, or a maintainer asking to accept an issue, starts it." Both what and when are answered explicitly with concrete trigger phrases, matching the 5 anchor; the 'Use when...' cap does not apply because explicit trigger guidance is present.

5 / 5

Trigger Term Quality

Quotes: "accept ONE microsoft/apm issue", "The canvas Accept button, or a maintainer asking to accept an issue, starts it", "status/accepted", "triage proposed scope". Natural trigger phrases a user would actually say or invoke are comprehensively covered for this domain (accept an issue, Accept button, maintainer request, triage scope); score 4 ('a few natural terms missing') fits worse since every natural way to trigger this skill is stated.

5 / 5

Distinctiveness Conflict Risk

Quotes: "microsoft/apm issue", "status/accepted", "do not accept pull requests". The description is pinned to one repository, one label, and a named governance flow, and explicitly disambiguates PR acceptance — a clear niche with distinct triggers and minimal conflict risk, matching the 5 anchor rather than the 4 anchor's 'minor overlap risk'.

5 / 5

Total

20

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 1 possibly missing (scripts/governance/eligibility.cjs), 1 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

microsoft/apm

Path

.agents/skills/autopilot-issue-accept/SKILL.md

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.