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

77%

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 ./.claude/skills/trellis-update-spec/SKILL.md

Quality

Content

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

A highly actionable, well-structured instruction skill with excellent templates and a clear workflow, but it is verbose and inlines content that progressive disclosure would move into separate referenced files.

Suggestions

Extract the per-type markdown templates (Design Decision, Convention, Pattern, Forbidden, Common Mistake, Gotcha) into a references/TEMPLATES.md and reference it from SKILL.md to reduce repetition and improve progressive_disclosure.

Consolidate the duplicated 7-section list: keep the brief trigger summary inline and move the full mandatory template into a referenced file, removing the redundancy between the 'Mandatory Output (7 Sections)' list and the 'Mandatory Template' block.

Add an explicit validation feedback loop to the Update Process (e.g., after editing, re-read the spec to confirm the section fits and does not duplicate existing content) to strengthen workflow_clarity.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and avoids explaining concepts Claude already knows, but the ~350-line body repeats itself (the 7-section list appears as both a summary and a full template, and several tables make overlapping points) and could be tightened.	3 / 5
Actionability	Provides fully copy-paste-ready markdown templates for every update type, a concrete bash command, a file-structure tree, and an explicit 7-section output spec covering the common cases.	5 / 5
Workflow Clarity	A clearly sequenced 5-step process (Identify, Classify, Read, Update, Update Index) with a closing quality checklist as a checkpoint, but no explicit re-verify-after-edit feedback loop beyond the checklist.	4 / 5
Progressive Disclosure	Well-organized with clear headers, tables, and a target-structure tree, but the single monolithic file inlines all templates and an interactive mode that could be split into referenced bundle files, and no external references are used.	3 / 5
	Total	15 / 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 strong description that clearly states both the capability and explicit trigger conditions with a concrete target location. It distinguishes itself well via the .trellis/spec/ niche, with only minor gaps in action breadth and synonym coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and target ("Captures executable contracts and coding conventions into .trellis/spec/ documents") with concrete actions and a specific directory, though only two actions are listed rather than a comprehensive set.	4 / 5
Completeness	Explicitly answers both what (captures contracts/conventions into .trellis/spec/) and when (Use when learning from debugging, implementing, or discussion that should be preserved) with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural trigger phrases ("learning something valuable from debugging, implementing, or discussion") that users would realistically say, though a few common synonyms (e.g., 'fixing a bug', 'refactoring') are missing.	4 / 5
Distinctiveness Conflict Risk	The .trellis/spec/ target and the preserve-learnings framing carve a distinct niche with mostly distinct triggers, though the broad 'discussion' trigger carries minor overlap with general memory-capture skills.	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: mindfold-ai/Trellis
Path: .claude/skills/trellis-update-spec/SKILL.md
Commit: 64e6636

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