CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ci-flaky-patrol

Classify a bounded batch of stale PR CI failures and choose the safest response.

Quality

72%

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

Fix and improve this skill with Tessl

tessl review fix ./.qwen/skills/ci-flaky-patrol/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

76%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.

This is a strong, highly actionable instruction-only skill: exact contracts, a complete output example, and tight guardrails on untrusted logs and tool use. Its main weaknesses are the missing self-validation step for a batch operation with outward-facing effects and a small amount of duplicated flakyTest rule text.

Suggestions

Add an explicit verification checkpoint before finishing, e.g. "Before writing, confirm every candidate has exactly one decision, identity fields match the candidate verbatim, and flakyTest appears only on rerun decisions for named tests" — this lifts the batch-operation cap on workflow clarity.

Consolidate the flakyTest rules stated in both the flakyTest paragraph and the output-spec paragraph into one place to remove redundancy.

Add lightweight section headers (Input, Actions, Flaky tests, Output, Constraints) so the multi-part spec is scannable.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence with no background-concept explanations, but the flakyTest-only-for-test-nondeterminism rule is stated in full in the flakyTest paragraph and repeated in the output-spec paragraph ("omit it entirely for infra reruns"), which could be trimmed.

4 / 5

Actionability

Guidance is fully executable: exact input/output filenames, a copy-paste-ready decisions JSON example covering the common rerun+flakyTest case, per-field constraints (200-char limits, confidence pairing, exact enums), and explicit tool restrictions.

5 / 5

Workflow Clarity

The sequence is unambiguous (read input, classify each candidate, apply the flakyTest rule, write one output), but this is a batch operation whose decisions drive outward-facing PR actions, and the skill contains no explicit validation/verification checkpoint — the rubric caps such skills at 3.

3 / 5

Progressive Disclosure

At under 50 lines with no external references needed, all content is appropriately placed in one file with no nested references; however the multi-part spec (actions, flakyTest rules, output format, tool limits) is unsectioned prose, leaving a minor organization gap that keeps it below 5.

4 / 5

Total

16

/

20

Passed

Description

53%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.

The description states a clear, concrete capability in third person, but it omits any trigger guidance, so a user (or Claude) has no explicit signal for when to invoke it. It also misses the highest-value natural keywords like "flaky". Overall it sits at the midpoint: a decent what with no when.

Suggestions

Add a "Use when..." clause naming the trigger situations, e.g. "Use when triaging flaky or stale CI failures on pull requests, rerunning transient failures, or deciding whether a red check is caused by the PR."

Include the natural synonyms users actually say — "flaky tests", "flaky CI", "rerun failed checks", "red build" — to improve trigger-term coverage.

Briefly enumerate the response options (rerun, comment on the PR, or no action) so the capability scope is explicit rather than implied by "safest response".

DimensionReasoningScore

Specificity

"Classify a bounded batch of stale PR CI failures" and "choose the safest response" name the domain plus two concrete actions, but the possible responses (rerun/comment/no_action) are not enumerated, so coverage is not comprehensive.

3 / 5

Completeness

The "what" is clear (classify failures, choose a response), but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

"CI failures" and "PR" are natural terms, but the most common user phrasings for this need — "flaky tests", "flaky CI", "rerun failed checks", "red build" — are all missing.

3 / 5

Distinctiveness Conflict Risk

"Stale PR CI failures" plus "choose the safest response" carves a fairly distinct niche with only minor overlap risk against general CI-triage or debugging skills; triggers are not explicit enough for a 5.

4 / 5

Total

13

/

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

QwenLM/qwen-code

Path

.qwen/skills/ci-flaky-patrol/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.