trigger-pipelines-for-copilot-pr

Trigger ADO pipelines for a Copilot-created PR by posting /azp run comments. Use when the user asks to trigger CI pipelines for a specific PR.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

80%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 tight, highly actionable single-purpose skill that gives exact commands and a sensible fallback chain. Its main gap is the absence of any verification step confirming the trigger comments succeeded, which the batch-operation cap pulls down to 3 on workflow clarity.

Suggestions

Add a verification step after posting, e.g. confirm each comment was created (gh pr comment outputs the comment URL) or check that the pipelines entered the queue, so the workflow has an explicit checkpoint.

Tighten the explanatory sentence 'Posting those comments will trigger all our pipelines, which is necessary for PRs that are created by Copilot.' to a single clause to improve token efficiency.

Make placeholder substitution explicit, e.g. note that <PULL_REQUEST_NUMBER> comes from $ARGUMENTS and <COMMENT_TEXT> is the literal block above, removing any ambiguity for the curl fallback.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, with only minor over-explanation such as 'Posting those comments will trigger all our pipelines, which is necessary for PRs that are created by Copilot.' that could be trimmed.	4 / 5
Actionability	Provides the exact two comment payloads, an exact gh CLI command, the MSYS_NO_PATHCONV caveat, and a full curl fallback — copy-paste ready and covering the common cases.	5 / 5
Workflow Clarity	The fallback sequence (check gh -> use gh; else GITHUB_TOKEN -> curl; else abort) is clear, but there is no validation that the comments posted or pipelines triggered; since triggering all pipelines is a batch operation, the rubric caps workflow_clarity at 3.	3 / 5
Progressive Disclosure	Under 50 lines, self-contained with no external references needed, and organized into clearly labeled comment/posting sections, satisfying the simple-skill exception for a 5.	5 / 5
	Total	17 / 20 Passed

Description

82%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 concise, well-targeted description that explicitly pairs a concrete capability with a clear use-when trigger and minimal conflict risk. Its only weakness is modest action coverage, which keeps specificity at the midpoint.

Dimension	Reasoning	Score
Specificity	Names the domain (ADO pipelines) and two concrete actions (trigger pipelines, post /azp run comments) but coverage is not comprehensive, matching anchor 3 rather than 4 which requires several actions.	3 / 5
Completeness	Explicitly answers both what ('Trigger ADO pipelines... by posting /azp run comments') and when ('Use when the user asks to trigger CI pipelines for a specific PR') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ('trigger CI pipelines', 'trigger pipelines for a specific PR', '/azp run') with good coverage; a few synonyms are missing so it sits at 4 rather than 5.	4 / 5
Distinctiveness Conflict Risk	Highly specific niche (Copilot-created PR, ADO pipelines, /azp comments) gives it a clear trigger with minimal overlap risk against other skills.	5 / 5
	Total	17 / 20 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: microsoft/FluidFramework
Path: .claude/skills/trigger-pipelines-for-copilot-pr/SKILL.md
Commit: f02e424

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.