CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

auto-build-repair

Repair custom-code build failures in generated Azure SDK pull requests with one bounded customized-update invocation. WHEN: an eligible release-planner Auto SDK PR labeled auto-sdk-build-fix needs repair, or requests mention auto build repair, custom-code build repair, or fixing the SDK PR build. Not for migrations, TypeSpec authoring, or API review.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

—

The risk profile of this skill

SKILL.md
Quality
Evals
Security

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.

An unusually actionable and well-gated operational skill: exact commands, artifacts, and validation gates cover every branch. Its main weakness is progressive disclosure — all referenced bundle files are missing from the skill directory, and version-sensitive and minutiae-level detail is inlined in SKILL.md.

Suggestions

Ship the referenced bundle files (repair-config.yml, capture-engine-result.ps1, emit-repair-report.ps1, telemetry-schema.v1.json) in the skill directory (e.g., scripts/ and references/) so the in-body links resolve and the capture/report steps are actually executable.

Move the engine-command serialization minutiae (LC_ALL=C printf '%q', ANSI-C ampersand escaping) and the reporting flag semantics into a reference file, leaving SKILL.md as a concise overview with clearly signaled one-level-deep links.

Relocate time-sensitive version requirements (azsdk_0.6.50, Azure/azure-sdk-tools#17068) into a dedicated compatibility or 'old patterns' section so mainline guidance stays version-independent.

DimensionReasoningScore

Conciseness

The body is dense and operational with no explanations of concepts Claude already knows, but it is not fully lean: time-sensitive version pins ("available in azsdk_0.6.50", PR #17068) are inline rather than in a compatibility/deprecated section, and the ANSI-C/printf '%q' serialization paragraph is intricate prose that could be tightened. It sits above anchor 3 (mostly efficient, no padding) but short of every-token-earns-its-place.

4 / 5

Actionability

Fully concrete and executable: a complete command block with every flag ("--edit-scope CustomCode", "--package-path", "--customization-request", "--max-attempts"), the equivalent MCP arguments, exact artifact filenames (pre-repair-errors.txt, result.json, engine-command.txt), and exact script invocations with per-branch flags (-Eligible:$false, -ForcedStatus skipped_already_green, -EngineErrorsFile). Specific guidance covers the common and failure cases.

5 / 5

Workflow Clarity

A clear sequenced workflow (configure/verify capability, identify failing package, invoke once, capture, report, commit) with explicit validation gates at every stage: "If unavailable, stop and report", "If the package is already green, skip", commit "only after the final package build is green and the final response has Boolean success: true", and a capture helper that "rejects missing, malformed, ambiguous, or contradictory responses". Every terminal outcome has a defined reporting path, satisfying the destructive/batch validation requirement.

5 / 5

Progressive Disclosure

Sections are well-organized and references are clearly signaled as markdown links, but scored against the actual bundle none of the four referenced files (repair-config.yml, capture-engine-result.ps1, emit-repair-report.ps1, telemetry-schema.v1.json) exist — there are no references/, scripts/, or assets/ directories — so every pointer dangles, and dense procedural minutiae (serialization rules, reporting flag semantics) is inlined that belongs in reference files. Good body structure keeps it above anchor 2; broken bundle references and inlined detail keep it below anchor 4.

3 / 5

Total

17

/

20

Passed

Description

87%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 strong, tightly-scoped description that answers what, when, and when-not with concrete trigger phrases and explicit boundary guidance. The only minor gaps are that it states a single (though precisely bounded) action and could include a few more natural trigger variants.

DimensionReasoningScore

Specificity

"Repair custom-code build failures in generated Azure SDK pull requests with one bounded customized-update invocation" names a precisely bounded, concrete action with its tool and domain, plus negative scope ("Not for migrations, TypeSpec authoring, or API review"). It stays at 4 rather than 5 because it describes a single action rather than listing several, omitting the capture/reporting half of the skill, and it is clearly above the anchor-3 example's generic 1-2 action coverage.

4 / 5

Completeness

Both halves are explicit: the "what" ("Repair custom-code build failures... with one bounded customized-update invocation") and a literal "WHEN:" clause with concrete trigger phrases plus an explicit exclusion clause. This matches the anchor-5 structure of concrete triggers for both what and when; nothing is merely implied.

5 / 5

Trigger Term Quality

"auto build repair, custom-code build repair, or fixing the SDK PR build" plus the label "auto-sdk-build-fix" give good natural-phrase coverage a user would actually say. A few plausible variants (e.g., "SDK build failure", "broken SDK build") are missing, keeping it below the comprehensive-synonym anchor of 5.

4 / 5

Distinctiveness Conflict Risk

A clear niche (eligible release-planner Auto SDK PR build repair) with a distinct label trigger ("auto-sdk-build-fix") and explicit exclusions ("Not for migrations, TypeSpec authoring, or API review"), so the risk of firing for the wrong skill is minimal.

5 / 5

Total

18

/

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

relative_links

Relative link issues: 4 missing

Warning

Total

15

/

16

Passed

Repository

Azure/azure-sdk-for-net

Path

.github/skills/auto-build-repair/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.