CtrlK
BlogDocsLog inGet started
Tessl Logo

trellis-break-loop

Deep bug analysis to break the fix-forget-repeat cycle. Analyzes root cause category, why fixes failed, prevention mechanisms, and captures knowledge into specs. Use after fixing a bug to prevent the same class of bugs.

73

Quality

90%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured, highly actionable analysis skill with clear sequencing and decision checkpoints. Its main weaknesses are minor motivational padding and an inline Bayesian section that could be extracted to a reference file.

Suggestions

Trim the 'Core Philosophy' aphorisms and 'Three levels of insight' list to reduce token overhead without losing the methodology.

Move the full 'Thinking Framework: Bayesian Reasoning' section into a separate reference file and link to it one level deep, keeping only a brief pointer inline.

Add a few trigger synonyms (debugging, regression, defect) to the description to improve keyword coverage.

DimensionReasoningScore

Conciseness

Mostly efficient structured tables and applied Bayesian guidance, but the 'Core Philosophy' aphorisms ('30 minutes of analysis saves 30 hours') and 'Three levels of insight' prose are minor motivational padding that could be trimmed.

4 / 5

Actionability

Provides a copy-paste output template, concrete category/prevention tables with examples, and specific file targets (e.g. 'cross-layer-thinking-guide.md', 'src/templates/markdown/spec/') making the guidance fully executable for an analysis skill.

5 / 5

Workflow Clarity

Sequences a clear 5-dimension analysis, a confidence-gating table that acts as a validation checkpoint before acting, and a checklist-driven 'Immediate Actions' closeout with explicit MUST steps.

5 / 5

Progressive Disclosure

Well-organized with clear section headers and no external bundle files, but at ~180 lines the sizable Bayesian Reasoning section could be split into a one-level-deep reference rather than fully inlined.

4 / 5

Total

18

/

20

Passed

Description

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

A strong, specific description that clearly states capabilities and a concrete use-trigger in third person. It is comprehensive on what/when and well-differentiated, with only minor room to broaden trigger synonyms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions—'Analyzes root cause category, why fixes failed, prevention mechanisms, and captures knowledge into specs'—giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both what ('Deep bug analysis... Analyzes root cause category...') and when ('Use after fixing a bug to prevent the same class of bugs') with concrete trigger phrasing.

5 / 5

Trigger Term Quality

Includes the natural phrase 'Use after fixing a bug' that users would say, but lacks synonyms like 'debugging', 'defect', or 'regression' for fuller keyword coverage.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche—post-fix deep bug analysis—with a distinct trigger unlikely to fire for unrelated skills, giving minimal conflict risk.

5 / 5

Total

19

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
mindfold-ai/Trellis
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.