CtrlK
BlogDocsLog inGet started
Tessl Logo

azsdk-common-pipeline-analysis

Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdk_analyze_pipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in CI", "analyze pipeline", "debug SDK pipeline". DO NOT USE FOR: local build issues without pipeline context, API design review, SDK publishing, applying code fixes (instead use azsdk-common-pipeline-fixer). INVOKES: azure-sdk-mcp:azsdk_analyze_pipeline, azure-sdk-mcp:azsdk_get_pipeline_llm_artifacts, azure-sdk-mcp:azsdk_get_pr_checks, azure-sdk-mcp:azsdk_get_pipeline_status.

80

Quality

100%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized instruction-only skill body: lean, actionable with concrete tool names and return fields, a clear sequenced workflow with error-recovery guidance, and clean progressive disclosure through two real reference files.

DimensionReasoningScore

Conciseness

The ~40-line body is lean with no concept padding — Rules, a tool table, numbered Steps, Examples, and Troubleshooting each earn their place and assume Claude's competence, matching the lean-and-efficient anchor.

3 / 3

Actionability

Concrete, executable guidance: exact MCP tool names and their return fields ('failed_tasks', 'failed_test_titles'), a specific four-way categorization scheme, and pointed references to output-format.md and failure-patterns.md — actionable without code since it is an instruction-only skill.

3 / 3

Workflow Clarity

A clearly sequenced Identify→Analyze→Categorize→Diagnose→Report flow with a Troubleshooting section providing error-recovery feedback (verify build ID, fall back to failed_tasks, az login); being read-only analysis, no destructive-operation validation gap applies.

3 / 3

Progressive Disclosure

The body is an overview that signals two real one-level-deep reference files (references/output-format.md, references/failure-patterns.md, both verified present) at the points of need, matching the clear-overview-with-well-signaled-references anchor.

3 / 3

Total

12

/

12

Passed

Description

100%

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 precise, well-structured description that states concrete capabilities, provides natural trigger terms, and clearly separates its scope from the sibling fixer skill via USE FOR / DO NOT USE FOR clauses.

DimensionReasoningScore

Specificity

Names the concrete domain and multiple specific actions — 'Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format' and 'interprets and formats' raw failure data — matching the multiple-concrete-actions anchor rather than the single-domain score-2 example.

3 / 3

Completeness

Explicitly answers both what (analyze pipeline failures into a structured diagnosis) and when via an explicit 'USE FOR' trigger clause, satisfying the both-what-and-when anchor rather than the what-only score-2 example.

3 / 3

Trigger Term Quality

The 'USE FOR' list gives natural user phrasings — 'pipeline failed', 'build failure', 'CI check failing', 'tests failing in CI', 'analyze pipeline', 'debug SDK pipeline' — with good coverage of how users actually ask, matching the natural-keywords anchor.

3 / 3

Distinctiveness Conflict Risk

Scoped to a clear niche (Azure SDK CI/CD pipeline failures) with distinct triggers plus an explicit 'DO NOT USE FOR' list that hands off to azsdk-common-pipeline-fixer, making conflict with sibling skills unlikely.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Azure/azure-sdk-for-net
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.