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.

58

Quality

66%

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 ./.github/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 content is well-structured and highly actionable with concrete templates and a clear process, but it is longer than necessary and bundles everything into a single file rather than splitting reference material out. Tightening redundant framing and moving templates to a referenced file would raise both conciseness and progressive disclosure.

Suggestions

Collapse the overlapping 'When to Update', 'Update Process', 'Interactive Mode', and 'Quality Checklist' sections and drop rhetorical framing ('Key Insight', 'Core Philosophy') to cut length without losing guidance.

Move the seven update templates into a referenced file (e.g. references/templates.md) and keep SKILL.md as a concise overview pointing to it, improving progressive disclosure.

Add an explicit validation checkpoint in the 5-step process (e.g. 'verify no duplication against existing spec, then update index') to give the workflow a clear validate→fix loop.

DimensionReasoningScore

Conciseness

At ~350 lines the body repeats guidance across "When to Update", "Update Process", "Interactive Mode", and "Quality Checklist", and includes rhetorical padding ("Key Insight", "Core Philosophy") that a competent reader doesn't need, fitting the mostly-efficient-but-could-be-tightened anchor 3.

3 / 5

Actionability

Concrete scaffolding is strong: a 7-section mandatory template, six typed templates, a directory tree, and a real `cat .trellis/spec/<category>/<file>.md` command; minor gaps are the placeholder code blocks ("code example", "bad code example") that aren't executable, so it stays just below 5.

4 / 5

Workflow Clarity

A clear 5-step sequence (Identify → Classify → Read → Update → Index) with a post-hoc Quality Checklist as validation, but the checklist is not embedded as an explicit validate→fix→retry checkpoint inside the sequence, matching the anchor-4 "clear sequence, minor validation gaps".

4 / 5

Progressive Disclosure

No bundle files exist and the entire skill is one ~350-line monolith with all templates inlined; the section structure is reasonable, but content that could live in a references file (the seven templates) is kept inline, fitting anchor 3.

3 / 5

Total

14

/

20

Passed

Description

70%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 clearly states what the skill does and when to use it, with concrete target (.trellis/spec/) and natural trigger phrasing. It is solid and well above baseline, with room to expand specificity and trigger-term variety to reach the top anchor.

DimensionReasoningScore

Specificity

"Captures executable contracts and coding conventions into .trellis/spec/ documents" names the domain plus one concrete action, but stops short of enumerating multiple distinct actions (extract/fill/merge-style), so it sits at anchor 3 rather than 4.

3 / 5

Completeness

A clear "what" (capturing contracts/conventions into .trellis/spec/) and an explicit "Use when..." clause are both present, but the "when" lacks the varied concrete trigger phrases of the anchor-5 example, so it lands at 4.

4 / 5

Trigger Term Quality

"debugging, implementing, or discussion" and "preserved for future sessions" are natural phrases users would say, with good though not exhaustive coverage; a few shorthand trigger terms are missing, placing it just above anchor 3.

4 / 5

Distinctiveness Conflict Risk

The narrow .trellis/spec/ target gives it a distinct niche with minimal conflict risk, though the "debugging/implementing/discussion" trigger set is somewhat broad, keeping it just below the fully distinct anchor 5.

4 / 5

Total

15

/

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
EcoPasteHub/EcoPaste
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.