CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

autopilot-pr-triage-worker

Use this skill to triage ONE microsoft/apm pull request already selected by autopilot-pr-triage-scheduler. Covers community PRs that fix an issue and PRs opened without an issue. Return one advisory recommendation, never human approval, never a diff review, never merge. Not a queue manager and not autopilot-pr-review-worker.

64

Quality

80%

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-triage-worker/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 lean, actionable instruction-only skill with a well-sequenced procedure, explicit stop/patch validation checkpoints, and clean references to bundled assets. Its main weakness is reliance on an external autopilot-comment skill and some deliberate-but-trimmable rule repetition.

DimensionReasoningScore

Conciseness

Terse, imperative prose ("Missing field -> stop", "One PR. Do not nest a scheduler path.") assumes Claude's competence and earns its tokens, though rules like the forbidden status labels and "never assign, never request reviewers" recur across sections and could be trimmed.

4 / 5

Actionability

Concrete guidance throughout — exact labels, exact template fields, the probe path "$REPO_ROOT/.agents/skills/autopilot-comment/SKILL.md", and explicit call prohibitions ("Do not call gh pr comment yourself") — but execution depends on the external autopilot-comment skill whose behavior is not bundled, leaving minor gaps short of copy-paste-ready 5.

4 / 5

Workflow Clarity

A clear 6-step Procedure with explicit validation checkpoints ("Missing number -> stop", "Missing -> stop. Do not post") and an error-recovery loop ("failed post -- patch via autopilot-comment (intent: patch)"); a few checkpoints remain implicit, keeping it just below the fully-checklisted 5.

4 / 5

Progressive Disclosure

Well-sectioned overview (Activation card, Origin and writes, Context, Procedure, Hard nos) pointing to real one-level-deep assets (label-contract.json, pr-triage-template.md) with clear navigation; minor organization gaps (some inline rule repetition) keep it short of 5.

4 / 5

Total

16

/

20

Passed

Description

78%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 tight, specific description that states concrete actions and explicit non-actions while clearly distinguishing itself from sibling skills. The trigger and completeness are strong but the 'when' is narrowly scoped to the scheduler context rather than broad user phrasing.

DimensionReasoningScore

Specificity

Names the domain ("triage ONE microsoft/apm pull request") and several concrete actions ("Return one advisory recommendation") plus explicit non-actions ("never human approval, never a diff review, never merge"), but the core verb "triage" stays somewhat generic, leaving minor coverage gaps short of a 5.

4 / 5

Completeness

Answers both what (triage one PR, return one advisory recommendation) and when ("Use this skill to triage ONE ... pull request already selected by autopilot-pr-triage-scheduler"), but the when is bound to a specific scheduler context and could be more explicit, so it sits above anchor 3 but below 5.

4 / 5

Trigger Term Quality

Natural terms a user would say are present ("triage", "pull request", "community PRs", "fix an issue", "without an issue") with good coverage, though a few common synonyms are absent.

4 / 5

Distinctiveness Conflict Risk

Explicit disambiguation ("Not a queue manager and not autopilot-pr-review-worker") carves a clear niche with minimal conflict risk, matching the anchor for clear distinct triggers.

5 / 5

Total

17

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

microsoft/apm

Path

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