CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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 direct CI evidence or a legacy `ci-scan` issue, including frozen ownership snapshots, Continue/Watch/Stop/Skip classification, manual dispatches, and scheduled sweeps.

Quality

87%

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

81%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 well-crafted protocol body: it is tightly written, unambiguous about what to do at each phase, and fail-closed by design, with explicit validation checkpoints throughout. The main improvement opportunities are trimming cross-section rule repetition and adding one or two worked evidence-to-decision examples.

Suggestions

Add a short worked example mapping sample ownership evidence (e.g., an incidental comment hit vs. a PR body with 'Fixes dotnet/maui#N') to the resulting Decision, to lift actionability to fully example-covered guidance.

Deduplicate the repeated rules — the 'do not monitor or plan a fallback CI-fix PR' Stop rule and the keep-one-PR Watch rule each appear in two sections — by stating them once and cross-referencing.

Consider moving the legacy issue-linked instructions and the closing-keyword reference formats into a small references/ file linked from the body, keeping SKILL.md as a leaner overview for the direct-CI path.

DimensionReasoningScore

Conciseness

The body is dense and imperative with no explanations of concepts Claude already knows — every line states a protocol rule ("Reject transport unless the saved base is an ancestor, all new commits are append-only and merge-free"). It is not a 5 because rules repeat across sections: "Do not monitor it or plan a fallback CI-fix PR" appears verbatim in both "Return a decision" and "Deduplicate without false ownership", and the keep-one-PR Watch rule is stated twice, so minor trimming is possible.

4 / 5

Actionability

For an instruction-only skill the guidance is highly concrete: copy-paste-ready decision tokens ("Decision: Continue/Watch/Stop/Skip"), an exhaustive closing-keyword list ("`Fix`, `Fixes`, `Fixed`, `Close`, `Closes`, `Closed`, `Resolve`, `Resolves`, or `Resolved`") with exact reference formats ("`#<issue>`, `dotnet/maui#<issue>`, or the issue URL"), and precise gate criteria. It stops short of the 5 anchor because there are no worked examples covering common cases (e.g., a sample PR body, a sample search hit classified as incidental vs. ownership).

4 / 5

Workflow Clarity

The sections form a clear execution sequence — discovery, state the decision, deduplicate, verify evidence, bound attempts, fail-closed write boundary — with numbered sub-steps and explicit validation at every phase ("Verify the cited failure still reproduces on the latest completed base-branch build", "Trace the exact failing test, platform path, and deepest relevant stack frame") and a defined error-recovery rule (backend error → "Request one bounded `report_incomplete` safe output and stop"). This matches the 5 anchor's explicit checkpoints and error-recovery handling; the destructive-operation cap does not apply since verification is pervasive.

5 / 5

Progressive Disclosure

No bundle files exist, and the single ~100-line file is well-organized into seven clearly-named sections ("Direct CI discovery", "Return a decision", "Deduplicate without false ownership", "Require current, specific evidence", "Bound autonomous work", "Fail closed at the write boundary") making navigation easy. It does not reach 5 because the under-50-line simple-skill exception does not apply and all operational material — including the separable legacy issue-linked instructions and keyword tables — is inlined in one file rather than split behind well-signaled references.

4 / 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 description: it explicitly states what the skill does and when to use it, with distinctive, niche-specific trigger tokens that make misfiring unlikely. Its only weaknesses are jargon-dense capability phrasing and a few missing common trigger variations (e.g., CI failure, flaky test).

DimensionReasoningScore

Specificity

The description lists several concrete actions — "investigating, creating, or advancing a `[ci-fix]` or `[ci-fix-net11]` pull request" plus "frozen ownership snapshots, Continue/Watch/Stop/Skip classification, manual dispatches, and scheduled sweeps" — matching the 'several specific actions; minor gaps' anchor. It falls short of the 5 anchor because items like "frozen ownership snapshots" lean on internal jargon whose concrete meaning is not explicit, and it sits clearly above the 3 anchor's '1-2 concrete actions' scope.

4 / 5

Completeness

Both halves are explicit: the 'what' is "Common safety and triage protocol for .NET MAUI CI-fixer workflows... including frozen ownership snapshots, Continue/Watch/Stop/Skip classification, manual dispatches, and scheduled sweeps", and the 'when' is an explicit "Use whenever investigating, creating, or advancing..." clause with concrete trigger phrases. This directly matches the 5 anchor; the 'Use when' cap of 3 does not apply.

5 / 5

Trigger Term Quality

Strong natural triggers for this niche: "`[ci-fix]` or `[ci-fix-net11]` pull request", "direct CI evidence", "legacy `ci-scan` issue", "scheduled sweeps" — a user needing this skill would plausibly say these. It does not reach 5 because common variations like "CI failure", "flaky test", or "broken build" are absent, leaving a few natural terms missing per the 4 anchor.

4 / 5

Distinctiveness Conflict Risk

The description carves a clear niche via distinctive tokens — ".NET MAUI CI-fixer", "`[ci-fix]`", "`[ci-fix-net11]`", "`ci-scan`" — that virtually no other skill would share, giving minimal conflict risk as the 5 anchor requires. It is far more differentiated than the 4 anchor's generic file-type pairing.

5 / 5

Total

18

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

dotnet/maui

Path

.github/skills/ci-fix/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.