trellis-finish-work

Wrap up the current session: verify quality gate passed, remind user to commit, archive completed tasks, and record session progress to the developer journal. Use when done coding and ready to end the session.

Quality

91%

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

Quality

Content

90%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 well-built procedural skill: concrete commands, defensive classification of dirty paths with explicit routing, and clear sequencing with a genuine validation gate before archiving. The only notable issues are the absence of a final-state verification step and minor formatting noise in the Step 2 bail-out message.

Suggestions

Add a closing verification step: after Step 4, check that git log matches the stated expected order (work commits → archive commits → journal commit) before declaring the session wrapped.

Fix the malformed nested code formatting in the Step 2 bail-out message ('finish-work` (Trellis command)`') so the command name renders correctly when quoted to the user.

Dimension	Reasoning	Score
Conciseness	Lean and efficient throughout: no explanations of concepts Claude already knows, and every detail (dirty-path filter rationale, hash sourcing for --commit, default-no confirmation) is non-obvious project-specific knowledge that earns its tokens.	5 / 5
Actionability	Fully executable: exact bash commands for every step, exact CLI flags (--title, --commit, --summary), quoted user-facing messages, expected auto-commit messages, and the expected final git log order.	5 / 5
Workflow Clarity	Clear four-step sequence with an explicit validation checkpoint (Step 2 dirty-path classification) and feedback loops (bail out to Phase 3.4, ask-when-unsure routing, one-shot confirmation for batch archives). Held below 5 only because the expected final git log order is stated as an expectation but never verified as a closing check.	4 / 5
Progressive Disclosure	No bundle files exist and the ~65-line body is a single linear workflow cleanly sectioned per step, with nothing that belongs in a separate file. It sits just above the under-50-line simple-skill range, so structure is good but not exemplary.	4 / 5
	Total	18 / 20 Passed

Description

88%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: concrete, third-person, complete what/when structure with a natural trigger clause. Its main weakness is fidelity to the actual skill body, which contradicts two claimed actions — the body forbids prompting the user to commit and contains no quality-gate verification step.

Suggestions

Remove or reword 'remind user to commit': the skill body explicitly instructs 'Do NOT run git commit here. Do NOT prompt the user to commit', so the description over-claims this action.

Remove 'verify quality gate passed' or add a corresponding step in the body — no current step performs any quality-gate check.

Broaden trigger coverage with natural synonyms such as 'finish work', 'wrap up', or 'end of session' to improve trigger_term_quality.

Dimension	Reasoning	Score
Specificity	Lists four concrete actions — 'verify quality gate passed', 'remind user to commit', 'archive completed tasks', 'record session progress to the developer journal' — giving comprehensive coverage of session wrap-up duties rather than just several with gaps.	5 / 5
Completeness	Explicitly answers both what (verify gate, remind about commits, archive tasks, record journal) and when ('Use when done coding and ready to end the session') with a concrete trigger phrase, matching the top anchor exactly.	5 / 5
Trigger Term Quality	'Use when done coding and ready to end the session' plus 'Wrap up the current session' are natural phrases a user would say, but common synonyms like 'finish work', 'wrap up', or 'session summary' are absent, so coverage is good rather than comprehensive.	4 / 5
Distinctiveness Conflict Risk	The Trellis-specific vocabulary ('archive completed tasks', 'developer journal', session wrap-up) carves a clear niche, but 'remind user to commit' creates minor overlap risk with commit-message and git-workflow skills.	4 / 5
	Total	18 / 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: .agents/skills/trellis-finish-work/SKILL.md
Commit: f089cb3

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