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.

61

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/trellis-break-loop/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

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

A well-organized, self-contained analysis framework with concrete file paths and an output template. It is held back by motivational filler, abstract analytical prompting, and the absence of validation checkpoints in its workflow.

Suggestions

Trim the "Core Philosophy" section and motivational lines (e.g. "30 minutes of analysis saves 30 hours of future debugging") to remove padding that does not guide action.

Add an explicit verification step after the spec-update actions — e.g. confirm the updated guide file exists and re-read the changed section — to close the workflow's missing validation checkpoint.

Tighten the analytical dimensions ("What broader problems does this bug reveal?") with more concrete prompts or worked examples so the guidance is less abstract.

DimensionReasoningScore

Conciseness

The framework tables and checklists are reasonably efficient, but the "Core Philosophy" block, motivational lines ("30 minutes of analysis saves 30 hours"), and repeated emphasis ("The analysis is worthless if it stays in chat") add padding that could be tightened without losing clarity.

2 / 3

Actionability

It supplies concrete specifics — named file paths (`.trellis/spec/guides/`), named guides (`cross-layer-thinking-guide.md`), and a copy-paste output template — but the core framework is largely analytical prompting rather than executable commands, leaving some guidance abstract.

2 / 3

Workflow Clarity

The five-dimension analysis and three-step immediate-action list are clearly sequenced, but there are no validation or verification checkpoints, which caps clarity at 2 even though the sequence itself is well ordered.

2 / 3

Progressive Disclosure

The skill is self-contained with no bundle files and no need for external references, and its content is organized into clearly labeled sections (Analysis Framework, Output Format, After Analysis), meeting the bar for a well-structured single-file skill.

3 / 3

Total

9

/

12

Passed

Description

85%

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 specific, third-person description that clearly conveys both capability and trigger, occupying a distinct niche. Its only weak spot is limited natural keyword variation for a meta-skill whose triggers are inherently abstract.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Analyzes root cause category, why fixes failed, prevention mechanisms, and captures knowledge into specs" — matching the anchor for naming several specific actions rather than vague language.

3 / 3

Completeness

It explicitly states what it does (deep bug analysis across named dimensions) and when to use it ("Use after fixing a bug to prevent the same class of bugs"), satisfying both halves with an explicit trigger.

3 / 3

Trigger Term Quality

It includes some natural terms ("bug", "fixing a bug", "prevent the same class of bugs") but offers few common variations a user would naturally say, falling short of the rich keyword coverage of the top anchor.

2 / 3

Distinctiveness Conflict Risk

It carves a clear niche — post-fix deep analysis to break the fix-forget-repeat cycle — with triggers unlikely to overlap with other skills.

3 / 3

Total

11

/

12

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.