CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

75

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-crafted, highly actionable workflow with concrete commands, an explicit validation checkpoint, and clean section organization. It respects token budget while leaving nothing ambiguous.

DimensionReasoningScore

Conciseness

Lean body of concrete commands plus purposeful routing/decision prose with no concept-explanation padding; every section earns its tokens.

3 / 3

Actionability

Provides exact, executable bash commands for each step (get_context.py, git status --porcelain, task.py archive, add_session.py with flags) and copy-ready quoted user messages.

3 / 3

Workflow Clarity

Steps 1–4 are clearly sequenced with an explicit validation gate in Step 2 (sanity check that bails back to Phase 3.4) and a user-confirmation checkpoint for batch archives, satisfying the destructive/batch validation requirement.

3 / 3

Progressive Disclosure

Self-contained single-file skill with no bundle references, organized into clear numbered sections; per the simple-skills note, well-organized sections warrant a top score.

3 / 3

Total

12

/

12

Passed

Description

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

A strong, complete description that pairs concrete actions with an explicit use-trigger, with only trigger-term breadth being a relative weakness. It is specific, distinct, and unambiguous about when to invoke.

Suggestions

Broaden trigger terms to cover phrasings a user might naturally say, e.g. 'Use when the user is done coding, ready to wrap up, end the session, or log off for the day'.

DimensionReasoningScore

Specificity

Names four concrete actions (verify quality gate, remind to commit, archive tasks, record journal), matching the 'lists multiple specific concrete actions' anchor rather than the partial level 2.

3 / 3

Completeness

Explicitly states what the skill does and provides an explicit 'Use when done coding and ready to end the session' trigger, satisfying both what and when.

3 / 3

Trigger Term Quality

Includes natural phrases ('wrap up the current session', 'done coding', 'ready to end the session') but covers essentially one trigger scenario with limited variation, so it stops at 'some relevant keywords but missing common variations'.

2 / 3

Distinctiveness Conflict Risk

Occupies a clear session-wrap-up niche (archive tasks, record journal) with a distinct end-of-session trigger; minor overlap with commit skills via 'remind user to commit' but unlikely to misfire.

3 / 3

Total

11

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
EcoPasteHub/EcoPaste
Reviewed

Table of Contents

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.