CtrlK
BlogDocsLog inGet started
Tessl Logo

failure-codifier

Extract recurring failure patterns from breezing orchestration logs and Judgment Ledger, emit failure-rule.v1 proposals with confidence scores. SSOT promotion to patterns.md or decisions.md is proposal-only — human-approval-required. Use when user mentions failure codifier, failure patterns, self-learning loop, codify failures, or failure-rule proposals. Do NOT load for: direct SSOT edits, auto-promotion, or implementation unrelated to failure analysis.

75

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

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

SKILL.md
Quality
Evals
Security

Quality

Content

87%

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

A well-organized, actionable body that delegates the multi-step human-approval promotion workflow to a single one-level-deep reference while keeping executable commands inline. Its main gap is that validation/feedback checkpoints for the destructive-adjacent SSOT workflow are not surfaced in the body itself.

Suggestions

Add a brief inline validation note in the 使い方 section (e.g. 'Verify stdout JSON: evidence_refs trace to real ledger lines and confidence matches the ≥3/≥5 thresholds') so the feedback loop does not depend on opening the reference.

Surface a one-line pointer to the human-review checklist from promotion-workflow.md near the dry-run command so the validation checkpoint is discoverable from the body.

Confirm the templates/schemas/failure-rule.v1.json and go/internal/failurecodifier/ paths are reachable from the skill bundle, or mark them as repo-relative so navigation expectations are unambiguous.

DimensionReasoningScore

Conciseness

The body is lean — concrete commands, threshold literals with file pointers, and a tight prohibitions list — without explaining concepts Claude already knows; every section earns its place.

3 / 3

Actionability

Provides fully executable commands ('./scripts/failure-codifier-propose.sh --dry-run', 'cd go && go test ./internal/failurecodifier/... -count=1') plus exact file paths for the schema and core implementation, copy-paste ready.

3 / 3

Workflow Clarity

The core propose→test sequence is present, but the validation/feedback checkpoints (evidence-ref checklist, confidence threshold verification) live only in the referenced promotion-workflow.md rather than inline, leaving the body's own workflow checkpoints implicit.

2 / 3

Progressive Disclosure

A concise overview with a clearly signaled 参照 section pointing one level deep to the real references/promotion-workflow.md (verified present), plus schema and core paths; content is appropriately split.

3 / 3

Total

11

/

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 strong, third-person description that names concrete capabilities, provides explicit positive and negative triggers, and clearly scopes the skill's read-only/proposal-only boundary. It is concise without padding and unlikely to conflict with adjacent skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Extract recurring failure patterns', 'emit failure-rule.v1 proposals with confidence scores', and proposal-only SSOT promotion to specific files (patterns.md/decisions.md).

3 / 3

Completeness

Explicitly answers both what (extract/emit proposals with confidence scores) and when (a 'Use when...' clause with concrete triggers), satisfying the top completeness anchor.

3 / 3

Trigger Term Quality

'Use when user mentions failure codifier, failure patterns, self-learning loop, codify failures, or failure-rule proposals' gives natural keyword coverage a user would actually say.

3 / 3

Distinctiveness Conflict Risk

A clear niche (read-only failure-pattern codification) is reinforced by negative triggers — 'Do NOT load for: direct SSOT edits, auto-promotion, or implementation unrelated to failure analysis' — minimizing misfires.

3 / 3

Total

12

/

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: 1 missing, 1 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.