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

70%

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

56%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 actionable with concrete templates, paths, and a sequenced workflow, but it is noticeably verbose with redundant tables and inlines material that would be better split across reference files. Consolidating overlapping sections and extracting templates into referenced files would materially improve it.

Suggestions

Consolidate the overlapping classification tables ('When to Update Code-Specs', 'Step 2: Classify the Update Type', and 'Interactive Mode') into a single source of truth to cut redundancy.

Move the per-type markdown templates (Design Decision, Convention, Pattern, Forbidden Pattern, Common Mistake, Gotcha) into a references/ file and link to it from SKILL.md to improve progressive disclosure.

Tighten the code-spec-vs-guide explanation, which is restated in three places, into one concise section.

Dimension	Reasoning	Score
Conciseness	The ~350-line body is noticeably verbose, with overlapping tables (When to Update, Step 2 Classify, Interactive Mode) and the code-spec-vs-guide distinction explained multiple times; several padded sections could be trimmed.	2 / 5
Actionability	Provides concrete file paths, a bash command ('cat .trellis/spec/<category>/<file>.md'), and fill-in markdown templates for each update type; templates use placeholders rather than fully executable examples, leaving minor gaps.	4 / 5
Workflow Clarity	A clear 5-step Update Process is sequenced with a Quality Checklist acting as the finishing validation checkpoint and a read-before-edit step; lacks an explicit validate-and-retry loop but the task is not destructive/batch.	4 / 5
Progressive Disclosure	No bundle files exist (references/scripts/assets absent) and all templates are inlined in a single monolithic SKILL.md; header structure is present but content that would benefit from separate files is not split out.	3 / 5
	Total	13 / 20 Passed

Description

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

A well-constructed description that clearly states both what it does and when to use it, with concrete domain references and natural trigger phrases. Its main weakness is a broad learning-oriented trigger that could overlap with other capture/memory skills.

Dimension	Reasoning	Score
Specificity	Names the domain ('executable contracts and coding conventions') and the concrete target ('.trellis/spec/ documents'), with several specific capture actions implied; minor gaps in enumerating the individual actions.	4 / 5
Completeness	Explicitly answers both 'what' (captures executable contracts and conventions into spec documents) and 'when' ('Use when learning something valuable from debugging, implementing, or discussion') with concrete triggers.	5 / 5
Trigger Term Quality	Natural trigger phrases like 'debugging, implementing, or discussion' are present and user-relatable; some internal jargon ('executable contracts', '.trellis/spec/') limits the breadth of natural keywords.	4 / 5
Distinctiveness Conflict Risk	The '.trellis/spec/' niche is distinct, but the 'learning something valuable' trigger is fairly broad and could overlap with general memory/learning skills, giving minor conflict risk.	4 / 5
	Total	17 / 20 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: 5139d30

Reviewed: 18 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.