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

72%

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 ./.kiro/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.

The body is highly actionable with concrete templates and a well-sequenced, checklist-backed workflow. Its weaknesses are verbosity with some redundant/decorative sections and the absence of any progressive disclosure into bundle files despite its length.

Suggestions

Move the six 'Update Templates' (and possibly 'Interactive Mode') into a references/ file, keeping SKILL.md as an overview that links to them, to improve progressive disclosure for a 350-line skill.

Remove the decorative 'Relationship to Other Commands' ASCII diagram and the 'Core Philosophy' callout, or compress them to one line, to tighten conciseness.

Consolidate the 'Interactive Mode' section with the existing 'When to Update Code-Specs' and 'Step 2: Classify' tables to eliminate the duplicated classification content.

Dimension	Reasoning	Score
Conciseness	The body is mostly actionable and avoids explaining concepts Claude already knows, but at ~350 lines it carries redundant content (the 'Interactive Mode' section re-derives the earlier classification) and decorative padding (the ASCII 'Relationship to Other Commands' diagram and 'Core Philosophy' callout) that could be trimmed.	2 / 3
Actionability	It provides concrete, complete scaffolding: a mandatory 7-section template with named fields, plus copy-ready templates for design decisions, conventions, patterns, forbidden patterns, common mistakes, and gotchas, with exact section names and field expectations.	3 / 3
Workflow Clarity	The 'Update Process' gives a clear 5-step sequence (Identify → Classify → Read target → Make update → Update index) reinforced by an explicit pre-edit read step and a closing 'Quality Checklist' serving as a validation checkpoint.	3 / 3
Progressive Disclosure	The skill is a single monolithic file with no bundle files (no references/scripts/assets) and no one-level-deep references; for a ~350-line skill, the six templates and interactive mode are inline content that could be split into reference files, though internal section organization is good.	2 / 3
	Total	10 / 12 Passed

Description

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

The description clearly states both capability and an explicit 'Use when...' trigger, anchored to a distinct '.trellis/spec/' niche. It is held back by a single-cluster action statement, moderate trigger-term coverage, and somewhat generic trigger activities that could overlap with sibling skills.

Suggestions

Expand the action phrase into a few concrete verbs (e.g. 'Captures signatures, validation/error matrices, and conventions into .trellis/spec/ documents') to reach full specificity.

Broaden trigger terms to include artifact keywords users would say, such as 'code-spec', 'spec update', 'design decision', or 'convention', alongside the activity-based triggers.

Tighten the 'when' clause to tie triggers more tightly to the .trellis/spec/ output (e.g. 'Use when a debugging or implementation session reveals a contract or convention worth persisting to .trellis/spec/') to reduce overlap with generic note-taking skills.

Dimension	Reasoning	Score
Specificity	It names a concrete domain ('executable contracts and coding conventions into .trellis/spec/ documents') and an action ('Captures'), but describes one action cluster rather than listing multiple distinct concrete actions like 'extract, fill, merge', so it is not comprehensive.	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 from debugging, implementing, or discussion that should be preserved for future sessions') with an explicit trigger clause.	3 / 3
Trigger Term Quality	The 'Use when...' clause offers some natural activity terms ('debugging, implementing, or discussion') but misses common variations and artifact keywords (e.g. 'spec', 'code-spec', 'convention', 'design decision'), giving partial rather than broad coverage.	2 / 3
Distinctiveness Conflict Risk	The '.trellis/spec/' niche is specific, but the trigger activities ('debugging, implementing, discussion, learning something valuable') are generic dev activities that could overlap with other knowledge-capture or documentation skills, so conflict risk is not fully resolved.	2 / 3
	Total	9 / 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: .kiro/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.