CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ci-monitor

Use when changing CI readiness, forge check collection, reruns, CI timeouts, CI step findings and fix rounds, or PR lifecycle monitoring.

Quality

52%

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 ./.agents/skills/ci-monitor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body contains deep, repo-specific knowledge that Claude could not reconstruct — invariants, owner files, and the exact regression tests guarding each behavior — which is genuinely valuable and specific. However, it is delivered as a monolithic, unpunctuated wall of prose with no workflow, no executable steps, and no file-level structure, which badly hurts token efficiency, navigation, and actionability.

Suggestions

Split each major bullet (rerun policy, findings model, behind-base, carry-review-on-replay, attestation restamping) into its own file under references/ and keep SKILL.md as a short index with one-line summaries plus explicit 'See [X](references/X.md)' links.

Add a short 'When changing CI monitor code' workflow — 1) identify the invariant touched, 2) preserve it, 3) run the named regression tests, 4) update the owning docs file — so the catalog becomes a procedure with validation checkpoints.

Move the exhaustive inline regression-test lists into per-topic reference files and keep only the 2–3 most representative test names per invariant in the main body to cut the token cost substantially.

DimensionReasoningScore

Conciseness

The body is a ~27KB wall of dense prose: single bullets run 300+ words (e.g. the rerun-policy bullet naming "TestCIStep_CancelledCheckIsRerunBeforeEscalating" among 16 inline regressions), burying each invariant in run-on sentences. It does not explain concepts Claude already knows (so not 1), but the sheer padding — exhaustive inline test enumerations and multi-clause sentences per bullet — is noticeably-to-severely inefficient, matching the 2 anchor better than 3's 'could be tightened'.

2 / 5

Actionability

Concrete pointers exist — named files and functions ("internal/pipeline/steps/ci_transient.go", "repairFromFindings in ci_fix.go"), config flags ("ci.release_after_checks_pass"), and per-invariant regression tests to run — but there is no executable procedure: no commands, no code, no 'do X then verify Y' steps. This lands on the 3 anchor (some concrete guidance but incomplete); above 2 because the pointers are specific and verifiable, below 4 because nothing is directly executable.

3 / 5

Workflow Clarity

There is no sequenced workflow at all: the body is a thematic catalog of invariants under two headers ("CI Monitor Lifecycle", "CI Step Findings Model"), with no ordered steps and no validation checkpoints for making changes (the implied 'change → keep invariant → run regression test' loop is never laid out). Not 1 because the material is coherently grouped rather than incoherent, but the many-gaps/no-explicit-sequence profile fits 2.

2 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), and the entire body is inlined as a monolith — distinct topics (rerun policy, findings model, behind-base rebasing, attestation restamping) each warrant their own reference file but are packed into two sections, with ownership pointers to repo docs ("docs/src/content/docs/reference/pipeline-steps.md") buried mid-paragraph. This matches the 2 anchor (content that clearly belongs in separate files is inlined) rather than 3, since the only structure is two headers over unbroken mega-bullets.

2 / 5

Total

9

/

20

Passed

Description

52%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 has a strong, explicit 'Use when' trigger clause with specific, niche domain terms, giving it good trigger quality and low conflict risk. Its main defect is that it completely omits the 'what' — it never says what the skill provides (guidance? invariants? a checklist?) — which caps completeness at the anchor for 'when'-only descriptions and limits specificity.

Suggestions

Add a 'what' clause before the trigger, e.g. 'Provides invariants and regression-test guides for the CI monitoring pipeline. Use when changing...' so the description answers both what and when.

Replace or gloss the internal jargon 'forge check collection' with terms a user would naturally say (e.g. 'CI check collection from GitHub/GitLab') and add common synonyms such as 'CI checks' or 'check reruns'.

DimensionReasoningScore

Specificity

The description enumerates concrete domain areas ("CI readiness, forge check collection, reruns, CI timeouts, CI step findings and fix rounds, or PR lifecycle monitoring") but describes no capability or action the skill performs — it names the domain, not what the skill does with it. It sits above 2 (the areas are specific and plural, not generic) but below 4 (no concrete actions are listed at all).

3 / 5

Completeness

Only the 'when' half is present: "Use when changing CI readiness... or PR lifecycle monitoring" is explicit, but the description never states what the skill does (no 'what' clause at all). This matches the 2 anchor ("only 'when' is present without 'what'") exactly; it cannot be 3 because the 'what' is not merely weak — it is absent.

2 / 5

Trigger Term Quality

Natural developer phrasings like "reruns", "CI timeouts", and "PR lifecycle monitoring" are present and would be said by someone touching this code, but "forge check collection" is internal jargon and common variants ("CI checks", "retry", "merge watch") are missing. Good coverage with a few gaps — matches the 4 anchor, not 5's comprehensive synonym coverage, and clearly above 3's partial coverage.

4 / 5

Distinctiveness Conflict Risk

The trigger set is a narrow, niche combination (CI step findings, forge check collection, PR lifecycle monitoring) unlikely to fire for unrelated skills, though it could overlap with a generic CI/CD or testing skill. Mostly distinct with minor overlap risk — the 4 anchor; not 5 because no identity statement distinguishes it from a hypothetical general CI skill.

4 / 5

Total

13

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

kunchenguid/no-mistakes

Path

.agents/skills/ci-monitor/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.