CtrlK
BlogDocsLog inGet started
Tessl Logo

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 manual single-issue dispatches and scheduled sweeps.

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.

The body is a tight, highly actionable triage protocol with clear sequencing and embedded validation steps. It respects token budget, assumes Claude's competence, and is well-organized without requiring external references.

DimensionReasoningScore

Conciseness

Lean throughout with no explaining of concepts Claude already knows; every line is actionable triage rule rather than padded context.

3 / 3

Actionability

Gives exact, executable guidance — terminal decision labels, the exact `Refs: dotnet/maui#<issue>` format, an enumerated keyword list, and precise stop/watch conditions — with no vague direction.

3 / 3

Workflow Clarity

Numbered sequences (dedup 1–4, evidence 1–5) with explicit validation checkpoints ('Verify the cited failure still reproduces', 'Check whether an intervening merged PR already fixed that path') for a batch/autonomous operation.

3 / 3

Progressive Disclosure

A single self-contained protocol file, cleanly sectioned with no nested or dangling references; no bundle files are needed so well-organized sections suffice.

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 concise, well-targeted description that states concrete capabilities, an explicit 'Use whenever...' trigger, and a distinctive niche. It avoids fluff and stays in third person.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'investigating, creating, or advancing a `[ci-fix]`... pull request from a `ci-scan` issue' — rather than vague abstractions.

3 / 3

Completeness

Explicitly answers both what ('Common safety and triage protocol') and when ('Use whenever investigating, creating, or advancing...').

3 / 3

Trigger Term Quality

Covers the domain's natural trigger vocabulary ('`[ci-fix]`', '`[ci-fix-net11]`', '`ci-scan`', 'manual single-issue dispatches', 'scheduled sweeps') in third-person voice with no first/second person.

3 / 3

Distinctiveness Conflict Risk

A narrowly scoped .NET MAUI CI-fixer niche with distinct label-based triggers makes conflict with other skills very 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
dotnet/maui
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.