analyze-test-run

Analyze a GitHub Actions integration test run and produce a skill invocation report with failure root-cause issues. TRIGGERS: analyze test run, skill invocation rate, test run report, compare test runs, skill invocation summary, test failure analysis, run report, test results, action run report

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Quality

Content

85%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 content is highly actionable with a clear, validated multi-phase workflow and clean progressive disclosure to two real reference files. The only meaningful weakness is repetition of the azure-deploy chain caveat across the body and references.

Suggestions

Consolidate the azure-deploy full-chain caveat to one canonical statement and cross-reference it, instead of restating it in Phase 2, Phase 3, report-format.md, and issue-template.md.

In the Skill Invocation Rate section, merge the deploy-vs-non-deploy prose and tables into a single compact treatment to reduce redundant explanation.

Move the per-skill detection table and invocation-matrix format fully into report-format.md, keeping only the decision rule (deploy chain vs. single skill) in SKILL.md.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean (tables, code blocks, concrete steps, no basic-concept padding), but the azure-deploy full-chain caveat is restated in Phase 2, Phase 3, report-format.md, and issue-template.md, and the deploy-vs-non-deploy distinction is explained in both prose and tables, which could be tightened.	3 / 5
Actionability	MCP tool calls are given as copy-paste-ready code blocks with concrete owner/repo/resource_id parameters, exact issue title formats, explicit label lists, and precise artifact filenames — fully executable guidance covering the common cases.	5 / 5
Workflow Clarity	Three clearly sequenced phases with numbered steps, explicit validation (search for existing open issue before creating), feedback loops for error recovery (artifact download blocked → fall back to get_job_logs), and a dedicated error-handling table satisfy the batch-operation validation requirement.	5 / 5
Progressive Disclosure	SKILL.md is an overview that delegates templates to two real one-level-deep references ([report-format.md], [issue-template.md]) with clear markdown links and a References section; neither reference nests further, so navigation is easy.	5 / 5
	Total	18 / 20 Passed

Description

95%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 strong: concrete actions, explicit trigger phrases, and a clear what/when pair in a distinctive niche. The only minor gap is that the action list, while specific, is not exhaustive enough to fully reach the top specificity anchor.

Dimension	Reasoning	Score
Specificity	"Analyze a GitHub Actions integration test run and produce a skill invocation report with failure root-cause issues" lists several concrete actions (analyze run, produce invocation report, root-cause failures) with minor coverage gaps; not quite the comprehensive multi-action list of a 5.	4 / 5
Completeness	It explicitly states what the skill does ("Analyze a GitHub Actions integration test run and produce a skill invocation report with failure root-cause issues") and provides explicit trigger guidance via the TRIGGERS clause, satisfying both what and when with concrete trigger phrases.	5 / 5
Trigger Term Quality	The TRIGGERS list — "analyze test run, skill invocation rate, test run report, compare test runs, ... test results, action run report" — gives comprehensive coverage of natural phrases a user would say, including synonyms and variations.	5 / 5
Distinctiveness Conflict Risk	The niche is narrow and specific — GitHub Actions integration test run analysis with skill invocation tracking and issue filing — with distinct triggers that are unlikely to fire for unrelated skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: microsoft/GitHub-Copilot-for-Azure
Path: .github/skills/analyze-test-run/SKILL.md
Commit: a55fe6d

Reviewed: 2 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.