ci-fix

Common safety and triage protocol for .NET MAUI CI-fixer workflows. Use whenever investigating, creating, or advancing a `[ci-fix]` or `[ci-fix-net11]` pull request from a `ci-scan` issue, including frozen ownership snapshots, Continue/Watch/Stop/Skip classification, manual single-issue dispatches, and scheduled sweeps.

Quality

86%

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

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.

A lean, well-structured instruction-only protocol: every section is an actionable rule with explicit validation gates and fail-closed error handling, and it is appropriately self-contained with no external references. The only improvements are removing duplicated sentences and concretizing the deferred caller-side mechanisms (transport gate, safe-output calls).

Dimension	Reasoning	Score
Conciseness	The body is terse, imperative, and teaches nothing Claude already knows, but contains literal repetition — 'Do not monitor it or plan a fallback CI-fix PR' appears twice (Stop bullet and dedup rule 4), and the keep-one-PR rule is restated across sections. Minor trims would earn a 5.	4 / 5
Actionability	Concrete guidance throughout: exact decision labels (Continue/Watch/Stop/Skip), an exhaustive closing-keyword list (Fix, Fixes, Fixed, Close... Resolved), exact reference formats (Refs: dotnet/maui#<issue>), and a named error path (report_incomplete). Falls short of fully executable because several mechanisms stay abstract ('the caller's transport gate', 'a supported safe-output call', 'patch-byte bounds') with no concrete command or shape.	4 / 5
Workflow Clarity	Sections are clearly sequenced (decision -> dedup -> evidence -> bounds -> write gate) with explicit validation checkpoints ('Verify the cited failure still reproduces on the latest completed base-branch build', ancestor/append-only/in-bounds transport checks) and explicit error-recovery behavior (never retry a failed mutation; request report_incomplete and stop). The destructive/batch cap does not apply because validation is abundantly present.	5 / 5
Progressive Disclosure	No bundle files exist and none are needed: the ~85-line protocol is self-contained, well-sectioned with descriptive headers, free of nested references, and all inline content (rules, keyword list) legitimately belongs in SKILL.md.	5 / 5
	Total	18 / 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 description: third-person, dense with domain-specific concrete actions, and an explicit 'Use whenever...' trigger clause naming the exact PR labels and issue source. Its only weaknesses are missing natural-language synonyms for triggering and a merely implied account of what the safety half of the protocol does.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions and scope items ('investigating, creating, or advancing a [ci-fix]... pull request', 'frozen ownership snapshots, Continue/Watch/Stop/Skip classification, manual single-issue dispatches, and scheduled sweeps'), but the safety half of the protocol is only gestured at, leaving minor gaps in coverage.	4 / 5
Completeness	Explicitly answers both what ('Common safety and triage protocol... including frozen ownership snapshots, ... classification, ... dispatches, and scheduled sweeps') and when ('Use whenever investigating, creating, or advancing a [ci-fix] or [ci-fix-net11] pull request from a ci-scan issue') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Triggers are the concrete tokens a caller would naturally emit ('[ci-fix]', '[ci-fix-net11]', 'ci-scan issue', 'scheduled sweeps'), giving good keyword coverage, but plainer natural-language synonyms a user might say (e.g. 'fix the CI failure', 'MAUI build break') are missing.	4 / 5
Distinctiveness Conflict Risk	A clear, tightly-scoped niche (.NET MAUI CI-fixer PRs from ci-scan issues, two specific title-prefix labels) with distinct trigger tokens and minimal overlap risk with other skills.	5 / 5
	Total	18 / 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: dotnet/maui
Path: .github/skills/ci-fix/SKILL.md
Commit: 7a5a5d6

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