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.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/trellis-update-spec/SKILL.md

Quality

Content

77%Weight 40%Scale 1-3

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

A well-structured, actionable spec-capture skill with concrete templates and a clear sequenced workflow. Its main weakness is length and redundancy, plus a fully inline layout with no progressive disclosure despite exceeding the single-file threshold.

Suggestions

Collapse the overlapping 'When to Update Code-Specs', 'Interactive Mode', and 'Quality Checklist' sections into a single trigger+checklist block to cut redundancy and roughly halve the body length.

Move the 'Update Templates' library into a separate references/ file (e.g. references/templates.md) and link to it from a concise overview, giving the >50-line skill real progressive disclosure.

Tighten the description trigger terms by adding concrete user phrasing (e.g. 'code-spec', 'spec update', 'capture a contract') alongside the abstract 'learning something valuable'.

Dimension	Reasoning	Score
Conciseness	The ~350-line body restates the same triggers across 'When to Update Code-Specs', 'Update Process', 'Interactive Mode', and 'Quality Checklist' — mostly efficient per section but padded with redundant checklists; not 3 because the repetition could be tightened, not 1 because it avoids explaining concepts Claude already knows.	2 / 3
Actionability	Provides copy-paste-ready markdown templates (Design Decision, Convention, Pattern, Forbidden Pattern, Common Mistake, Gotcha), a concrete 7-section mandatory template, a directory tree, and an executable `cat .trellis/spec/<category>/<file>.md` command; per the instruction-only scoring note this matches anchor 3.	3 / 3
Workflow Clarity	A clearly sequenced 5-step 'Update Process' (Identify → Classify → Read → Make → Update Index) closes with an explicit 'Quality Checklist' validation step; not 2 because checkpoints are present, and no destructive/batch feedback loop is required for a low-risk documentation update.	3 / 3
Progressive Disclosure	The skill ships as a single monolithic SKILL.md with no bundle files and no external references; it is well-sectioned but content that should be separate (the long template library, interactive prompts) is inline, matching anchor 2 rather than 3.	2 / 3
	Total	10 / 12 Passed

Description

75%Weight 40%Scale 1-3

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 clear, third-person description that pairs a concrete what with an explicit when-trigger tied to a distinct .trellis/spec niche. It is slightly held back by abstract trigger phrasing and a single broad action verb rather than multiple concrete capabilities.

Dimension	Reasoning	Score
Specificity	Quotes 'Captures executable contracts and coding conventions into .trellis/spec/ documents' — it names the domain and a single concrete action ('captures ... into ... documents') but does not list multiple specific concrete actions, so it matches anchor 2 rather than 3.	2 / 3
Completeness	It explicitly answers both what ('Captures executable contracts and coding conventions into .trellis/spec/ documents') and when ('Use when learning something valuable...'), which is the anchor-3 pattern; not 2 because the when-clause is explicit, not merely implied.	3 / 3
Trigger Term Quality	The 'Use when learning something valuable from debugging, implementing, or discussion' clause supplies some natural terms ('debugging', 'implementing') but they are abstract and miss common variations, matching 'some relevant keywords but missing common variations' rather than full coverage.	2 / 3
Distinctiveness Conflict Risk	The '.trellis/spec/ documents' anchor and 'executable contracts' framing give it a clear niche unlikely to trigger for unrelated skills; not 2 because the target location is specific rather than a generic 'document files' overlap.	3 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: EcoPasteHub/EcoPaste
Path: .github/skills/trellis-update-spec/SKILL.md
Commit: 6dbbf4f

Reviewed: 12 days ago

Table of Contents

Discovery Implementation Validation

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.