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

92%

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

100%

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

The content is tight, actionable, and well-sequenced with validation gates appropriate to the batch archive operation. It needs no external references and is organized for easy navigation.

Dimension	Reasoning	Score
Conciseness	The body is lean and command-driven, assumes Claude's competence, and avoids explaining concepts Claude already knows; every section earns its place with executable commands and brief, purposeful routing logic.	3 / 3
Actionability	Provides fully executable commands with concrete flags (get_context.py --mode record, git status --porcelain, task.py archive, add_session.py --title/--commit/--summary), copy-paste ready and specific.	3 / 3
Workflow Clarity	A clearly numbered 4-step sequence with an explicit validation checkpoint in Step 2 (classify dirty paths, bail out if current-task work is uncommitted) and a confirmation gate in Step 1 before batch archiving, matching the anchor for clear sequence with explicit validation.	3 / 3
Progressive Disclosure	A single well-organized SKILL.md with clear step sections and no nested external references; per the rubric's simple-skill note, well-organized sections with no need for external references score 3.	3 / 3
	Total	12 / 12 Passed

Description

85%

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 is specific, complete, and distinct, with an explicit 'Use when...' trigger. It is slightly narrow in trigger-term coverage and contains a small inconsistency with the body regarding commit prompting.

Suggestions

Broaden trigger terms with natural variations users might say, e.g. 'wrap up', 'finish up', or 'before stopping for the session', to improve trigger coverage.

Reconcile 'remind user to commit' in the description with the body's explicit 'Do NOT prompt the user to commit' — the description currently misrepresents the skill's behavior.

Consider adding 'Trellis' or the project context to the trigger so it is unambiguously scoped to this workflow.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'verify quality gate passed, remind user to commit, archive completed tasks, and record session progress to the developer journal' — matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	Explicitly answers both what (verify gate, archive tasks, record journal) and when ('Use when done coding and ready to end the session'), matching the anchor for clearly answering both what AND when with explicit triggers.	3 / 3
Trigger Term Quality	The single 'Use when done coding and ready to end the session' clause offers natural phrasing but limited coverage of common variations (e.g., 'wrap up', 'finish up', 'before stopping'), fitting the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	The session-wrap-up niche (archive tasks, record developer journal, end of session) is distinct and unlikely to fire for unrelated skills, matching the clear-niche anchor.	3 / 3
	Total	11 / 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: mindfold-ai/Trellis
Path: .agents/skills/trellis-finish-work/SKILL.md
Commit: 12e279a

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.