CtrlK
BlogDocsLog inGet started
Tessl Logo

ci

CI red? Call us. Pipeline fire brigade deploys. Use when user mentions CI failures, build errors, test failures, or pipeline issues. Do NOT load for: local builds, standard implementation work, reviews, or setup.

68

Quality

82%

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

The canonical home for this skill is ci in Chachamaru127/claude-code-harness

SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable skill body with a clear gated workflow and clean one-level reference split, weakened mainly by redundant restatements of the anti-tampering rules and the verbose VibeCoder section.

Suggestions

Consolidate the test-tampering prohibition into a single canonical section and reference it elsewhere rather than restating it four times.

Tighten or remove the VibeCoder section, which re-explains basics Claude already knows and duplicates the prohibition guidance.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete commands, but the test-tampering prohibition is restated across Step 0, the 禁止事項 table, 判断フロー, and the VibeCoder section, and the VibeCoder section re-explains concepts Claude already understands.

2 / 3

Actionability

Executable git log commands with specific format flags (--format, --topo-order, --raw), a flags-to-effect table, and a concrete Task tool invocation pattern with subagent_type and prompt template are copy-paste ready.

3 / 3

Workflow Clarity

The 実行手順 sequence, Step 0 triage/validation gate, the prohibition checklist, and the explicit feedback loop (修正→再実行→失敗 2回以上 → escalate to ci-cd-fixer) provide clear sequencing with checkpoints and error recovery.

3 / 3

Progressive Disclosure

The body is an overview that signals two real one-level-deep references (analyzing-failures.md, fixing-tests.md) in a table, with detailed procedures appropriately split into those leaf files.

3 / 3

Total

11

/

12

Passed

Description

80%

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 distinctive, well-triggered description with explicit use/exclusion guidance, undermined by a metaphorical, first-person capability statement that lacks concrete actions.

Suggestions

Replace the metaphorical opener "CI red? Call us. Pipeline fire brigade deploys." with concrete actions, e.g. "Diagnoses CI failures, identifies root-cause commits, and fixes failing tests and builds."

Drop the first-person "Call us" voice in favor of third-person capability verbs to avoid the specificity penalty.

DimensionReasoningScore

Specificity

The capability statement is metaphorical fluff ("Pipeline fire brigade deploys", "Call us") rather than concrete actions like diagnose/fix/rerun, and the first-person "Call us" voice triggers the rubric's specificity penalty.

1 / 3

Completeness

Both what (deploys for CI problems) and when are explicitly present via the "Use when user mentions..." clause, supplemented by an explicit "Do NOT load for" exclusion.

3 / 3

Trigger Term Quality

"CI failures, build errors, test failures, or pipeline issues" plus "CI red" are natural terms users would actually say, giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

The targeted CI/pipeline niche combined with the explicit "Do NOT load for: local builds, standard implementation work, reviews, or setup" exclusion makes triggering for the wrong skill unlikely.

3 / 3

Total

10

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 missing, 2 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository
Chachamaru127/claude-code-harness
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.