CtrlK
BlogDocsLog inGet started
Tessl Logo

trellis-update-spec

Captures executable contracts and coding conventions into .trellis/spec/ documents. Use when learning something valuable from debugging, implementing, or discussion that should be preserved for future sessions.

60

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-update-spec/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 is a well-structured, actionable instruction skill with concrete templates and a clear sequenced workflow backed by a quality checklist. Its main weaknesses are redundancy across overlapping sections and the absence of any progressive disclosure to reference files despite substantial template bulk.

Suggestions

Consolidate the overlapping 'When to Update Code-Specs', 'Update Process', and 'Interactive Mode' sections into a single decision flow to remove repeated identification questions and tighten the body.

Move the seven update templates into a references/templates.md file and link to it from SKILL.md so the main file stays a lean overview (improves both conciseness and progressive_disclosure).

Add an explicit validation feedback loop to the Update Process (e.g., re-read the edited spec to confirm it passes the Quality Checklist before finishing) to push workflow_clarity toward 5.

DimensionReasoningScore

Conciseness

The ~350-line body is mostly useful but carries notable redundancy: 'When to Update Code-Specs', 'Update Process', and 'Interactive Mode' re-ask the same identification questions, and the code-spec-vs-guide distinction is reiterated several times, so it could be tightened considerably.

3 / 5

Actionability

Provides concrete, copy-paste-ready markdown templates (7-section infra template, design decision, convention, pattern, forbidden pattern, common mistake, gotcha) plus a real bash command, with only minor fill-in gaps keeping it below a 5.

4 / 5

Workflow Clarity

A clear 5-step Update Process (Identify -> Classify -> Read -> Update -> Update Index) is sequenced and closes with a Quality Checklist acting as a validation checkpoint, though an explicit validate-and-retry feedback loop is only implicit.

4 / 5

Progressive Disclosure

Section headers and tables give decent structure, but no bundle files exist and all seven templates plus every reference are inlined in SKILL.md; at over 50 lines this content clearly belongs partly in separate reference files, so it is not the well-split 5.

3 / 5

Total

14

/

20

Passed

Description

78%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 cleanly states both what the skill does and when to invoke it, with a distinct .trellis/spec/ niche and natural trigger terms. It is slightly thin on enumerating multiple distinct concrete actions and could add a few more synonyms, which caps specificity and trigger coverage just below the top.

DimensionReasoningScore

Specificity

Names the domain ('executable contracts and coding conventions into .trellis/spec/ documents') with the single concrete action of capturing, but does not enumerate several distinct actions, so it sits at '1-2 concrete actions' rather than the comprehensive 4-5.

3 / 5

Completeness

Explicitly answers both 'what' (captures executable contracts and conventions into .trellis/spec/ documents) and 'when' (Use when learning something valuable from debugging, implementing, or discussion) with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

'debugging, implementing, or discussion that should be preserved for future sessions' are natural phrases a user would say, with good coverage; a few common synonyms (e.g., 'spec', 'conventions') are underrepresented, keeping it just below 5.

4 / 5

Distinctiveness Conflict Risk

The .trellis/spec/ target gives it a clear niche with minimal conflict risk, though the broad 'learning something valuable... preserved for future sessions' framing could overlap slightly with general memory/journal skills.

4 / 5

Total

16

/

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.