CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

autopilot-pr-review-worker

Use this skill to run a multi-persona expert advisory review on a labelled pull request in microsoft/apm. panel-mode (full | lean | delta) selects a surface-gated roster plus a CEO synthesizer; omitted or unknown mode is lean. Do not spawn inactive stubs. The orchestrator is the sole writer to the PR: ONE recommendation comment, no verdict labels, no merge gating. The panel is advisory -- it surfaces findings, prioritizes follow-ups, and renders a ship-recommendation that the maintainer and author weigh.

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/autopilot-pr-review-worker/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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.

An exceptionally actionable and well-sequenced orchestration skill: every step carries executable commands, schema contracts, and fail-closed validation gates with explicit retry loops. The main costs are repetition of the same three invariants across four sections and inlining of persona-gating detail (fast-path file lists, routing matrix) that belongs in the already-present bundle assets.

Suggestions

State the synchronous fan-out / non-empty-exit / label-sweep rules once in a canonical section (e.g. Architecture invariants) and use short back-references from steps 5, 8, 9, and the Gotchas instead of re-explaining each failure mode in full.

Move the per-persona fast-path file lists (auth, doc-writer, performance-expert globs) and the routing matrix into assets/panel-mode.md or persona reference files so SKILL.md stays an orchestration overview.

Restore or remove the 'evals/fixtures/03-panel-mode-walkthrough.md' reference in step 1 -- the file is absent from the bundle (and, unlike the .agent.md files, is not declared consumer-provided).

DimensionReasoningScore

Conciseness

The body is dense with genuinely non-obvious operational knowledge (gh-aw failure modes, CODEOWNERS gates, repo-specific file paths), but the three load-bearing rules -- synchronous fan-out, non-empty turn exit, and the label sweep -- are each re-explained three to five times (Architecture invariants, checklist preamble, steps 5/8/9, and the Gotchas section), plus rationale padding like 'This is the architectural fix for the previous regime's over-strictness'. This fits anchor 3 ('mostly efficient but includes some unnecessary explanation or could be tightened') better than 2, since nearly all content is skill-specific rather than concepts Claude already knows.

3 / 5

Actionability

The guidance is fully executable: exact commands ('gh pr view <PR_NUMBER> --json author,reviewRequests,headRefOid', 'gh pr edit --add-reviewer @me'), a complete copy-paste invocation of scripts/check_required_agents.py with arguments, an exact label list '[panel-review, panel-approved, panel-rejected]', an exact receipt format ('<!-- apm-review-advisory:v1 target=pr#<N> head=<sha> watermark=<watermark> -->'), and schema-cited JSON return contracts. This matches anchor 5 ('copy-paste ready code or commands; specific examples cover the common cases').

5 / 5

Workflow Clarity

The numbered execution checklist (steps 0-9) is strictly ordered with explicit validation gates at every risky point: the acceptance gate, CODEOWNERS last-comment gate, S4 schema validation with capped re-spawn retries ('Maximum two re-spawn attempts per panelist'), persona preflight, and the ownership consistency gate with a re-render-then-noop fallback. These feedback loops for error recovery and checklists for a complex process match anchor 5 exactly.

5 / 5

Progressive Disclosure

Bundle references are real, clearly signaled, and one level deep (assets/panelist-return-schema.json, assets/ceo-return-schema.json, assets/recommendation-template.md, assets/panel-mode.md, assets/shared-brief.example.json, scripts/check_required_agents.py all exist), matching anchor 4's 'most content is appropriately placed; references mostly clear'. It falls short of 5 because roughly a hundred lines of per-persona fast-path file globs and the routing matrix are inlined in SKILL.md rather than split into the existing panel-mode/asset files, and one referenced path, 'evals/fixtures/03-panel-mode-walkthrough.md', does not exist in the bundle.

4 / 5

Total

17

/

20

Passed

Description

62%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.

A specific, well-scoped description with a clear 'what' and excellent distinctiveness, but it lacks an explicit 'Use when...' trigger clause and natural trigger phrasings (e.g. 'PR', 'code review'), leaving both completeness and trigger-term quality at the midpoint. Adding one sentence of explicit activation guidance would lift it substantially.

Suggestions

Add an explicit trigger clause such as 'Use when a pull request in microsoft/apm is labelled panel-review (with status/accepted) and needs an advisory expert-panel review' to raise completeness above the cap of 3.

Include natural user-facing synonyms -- 'PR', 'code review', 'review pull request' -- alongside 'pull request' and 'advisory review' so the natural-keyword coverage matches how users would actually phrase the request.

Trim internal jargon from the description ('surface-gated roster', 'CEO synthesizer') or pair each term with its plain-language equivalent so trigger matching does not depend on vocabulary unique to this repo.

DimensionReasoningScore

Specificity

The description lists several concrete actions -- 'run a multi-persona expert advisory review', 'panel-mode (full | lean | delta) selects a surface-gated roster plus a CEO synthesizer', 'ONE recommendation comment, no verdict labels, no merge gating', 'surfaces findings, prioritizes follow-ups, and renders a ship-recommendation' -- with only minor coverage gaps, matching the 'several specific actions' anchor. It falls short of 5 because it does not comprehensively enumerate the skill's capabilities (fan-out topology, shared brief, label sweep are absent), and sits clearly above 3's '1-2 concrete actions'.

4 / 5

Completeness

The 'what' is clear (multi-persona advisory review, sole-writer single-comment contract), but there is no 'Use when...' clause or equivalent explicit trigger guidance -- 'on a labelled pull request in microsoft/apm' only weakly implies when. Per the judging guideline, a missing 'Use when...' clause caps completeness at 3; it does not drop to 2 because the 'what' half is explicit and concrete.

3 / 5

Trigger Term Quality

Some relevant natural keywords are present ('pull request', 'review', 'advisory review'), but common variations and synonyms users would actually say -- 'PR', 'code review' -- are missing, and the phrase space leans on internal jargon ('surface-gated roster', 'CEO synthesizer') that no user would utter. This matches anchor 3 ('Some relevant keywords but missing common variations or synonyms') rather than 4, whose keyword coverage would include the natural phrasings.

3 / 5

Distinctiveness Conflict Risk

The description is pinned to a narrow niche -- 'a labelled pull request in microsoft/apm' with a panel-mode roster and advisory-only comment contract -- so it is clearly distinguishable from any generic review skill and carries minimal conflict risk. This matches anchor 5 ('Clear niche with distinct triggers; minimal conflict risk'); the repo-specific scoping rules out the 'minor overlap risk' of anchor 4.

5 / 5

Total

15

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (768 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 2 possibly missing (references/algorithmic-patterns.md, scripts/perf/)

Warning

Total

13

/

16

Passed

Repository

microsoft/apm

Path

.agents/skills/autopilot-pr-review-worker/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.