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.

57

Quality

72%

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

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

A highly actionable, clearly sequenced orchestration skill with strong validation checkpoints and a well-structured asset bundle. Its main weakness is verbosity: critical invariants are repeated across five-plus sections rather than stated once and cross-referenced.

Suggestions

State each architecture invariant exactly once (in Architecture invariants) and cross-reference it from the Execution checklist and Gotchas instead of re-explaining the advisory-not-gate, sole-writer, and synchronous-fan-out rules in each location.

Extract the conditional-panelist fast-path file lists and self-check questions into a referenced assets file (e.g. assets/surface-gating.md) so the main SKILL.md stays an overview, keeping progressive disclosure one level deep and trimming the body.

Tighten the Gotchas section to only the non-obvious traps (mermaid :::cssClass, false-negative auth, false-positive test coverage) and drop restatements of invariants already covered above.

DimensionReasoningScore

Conciseness

The body restates the same invariants multiple times — the advisory-not-gate / no-verdict-label / sole-writer / synchronous-blocking-spawn / non-empty-exit rules each recur across the frontmatter, intro, Architecture invariants, Execution checklist, Output contract, and Gotchas — which is noticeably verbose with padded sections despite the operational detail being legitimate.

2 / 5

Actionability

Provides concrete, copy-paste-ready commands ('gh pr view <PR_NUMBER> --json author,reviewRequests,headRefOid', 'gh pr edit --add-reviewer @me'), exact label lists ('[panel-review, panel-approved, panel-rejected]'), exact receipt-line and schema references; minor gaps only because the rendering logic lives in referenced template/schema files rather than inline.

4 / 5

Workflow Clarity

The numbered Execution checklist (steps 0-9) is clearly sequenced with explicit validation gates (acceptance gate, CODEOWNERS last-comment gate, S4 schema gate with bounded re-spawn, ownership-consistency re-render/no-op, non-empty exit guarantee) and feedback loops for error recovery, which is exactly the anchor-5 pattern for a batch/write operation.

5 / 5

Progressive Disclosure

All five referenced bundle files (assets/panel-mode.md, panelist-return-schema.json, ceo-return-schema.json, recommendation-template.md, shared-brief.example.json) exist and are signaled one-level-deep with clear paths, but the SKILL.md itself is a ~740-line monolith with inlined conditional-panelist rules, routing matrix, and gotchas that could be split into referenced files.

4 / 5

Total

15

/

20

Passed

Description

71%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-bounded trigger description with strong distinctiveness and a clear what/when statement. It is held back from the top band by jargon-heavy trigger terms and a merged rather than separately-stated 'when' clause.

Suggestions

Add common synonyms a maintainer would actually type (e.g. 'PR', 'code review') alongside 'pull request' and 'advisory review' to broaden natural trigger coverage.

Split the 'when' into its own explicit clause naming the triggering precondition (e.g. 'Use when a PR in microsoft/apm carries the panel-review label and needs an advisory pass').

DimensionReasoningScore

Specificity

Lists several concrete actions ('run a multi-persona expert advisory review', 'surfaces findings, prioritizes follow-ups, and renders a ship-recommendation', 'ONE recommendation comment, no verdict labels, no merge gating') rather than vague language, with only minor coverage gaps.

4 / 5

Completeness

The 'Use this skill to run a...review on a labelled pull request in microsoft/apm' clause answers both what and when explicitly, but the when is merged with the what and the 'labelled' precondition is not spelled out, so it could be more specific.

4 / 5

Trigger Term Quality

Contains relevant natural keywords ('pull request', 'advisory review', 'findings', 'follow-ups') but leans on internal jargon ('panel-mode', 'surface-gated roster', 'CEO synthesizer', 'orchestrator') that users would not naturally say, and omits common synonyms like 'PR' or 'code review'.

3 / 5

Distinctiveness Conflict Risk

The description carves a clear niche (multi-persona advisory review of a labelled PR in microsoft/apm with a panel-mode selector) tied to a specific repo and automation regime, giving it distinct triggers and minimal conflict risk.

5 / 5

Total

16

/

20

Passed

Validation

75%

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

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

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

Warning

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 10 missing, 10 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

12

/

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.