trellis-continue

Resume work on the current task. Loads the workflow Phase Index, figures out which phase/step to pick up at, then pulls the step-level detail via get_context.py --mode phase. Use when coming back to an in-progress task and you need to know what to do next.

Quality

79%

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-continue/SKILL.md

Quality

Content

75%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-structured resume workflow with concrete commands and a precise routing decision tree, appropriately deferring canonical detail to workflow.md. Minor trims and an explicit failure/retry path would lift it to top marks.

Suggestions

Tighten the explanatory asides (e.g., 'Confirms: current task, git state, recent commits' and the Trellis-flow sentence) or fold them into the command comments to improve conciseness.

Add a brief error-recovery note for when get_context.py fails or returns unexpected status, giving the workflow an explicit feedback loop.

Consider moving the dense status-routing table into .trellis/workflow.md and keeping a condensed 2–3 line summary here to sharpen progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Lean and assumes Claude's competence; minor explanatory lines ('Confirms: current task, git state, recent commits', 'This command replaces the user needing to remember the Trellis flow') could be trimmed but earn their place.	4 / 5
Actionability	Gives concrete, runnable commands (get_context.py with --mode phase, --step <X.X> --platform kiro) and a precise status-based routing table; the <X.X> placeholder and dynamically-loaded step instructions are minor gaps versus copy-paste-ready 5.	4 / 5
Workflow Clarity	Clear Step 1–4 sequence with an explicit decision tree routing on status + artifact presence and a user-confirmation checkpoint before task.py start; no error-recovery feedback loop for command failures, so it sits below 5.	4 / 5
Progressive Disclosure	Acts as an entry point with a well-signaled one-level reference to .trellis/workflow.md for canonical detail; the inline routing table is arguably overview-level but is fairly dense, keeping it just below 5.	4 / 5
	Total	16 / 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 tight, third-person description that states concrete actions and an explicit 'Use when' trigger for resuming in-progress work. Slightly below top marks on specificity and trigger breadth, but fully complete and clearly distinct.

Dimension	Reasoning	Score
Specificity	Names several concrete actions — 'Loads the workflow Phase Index', 'figures out which phase/step to pick up at', 'pulls the step-level detail via get_context.py --mode phase' — with only minor coverage gaps; not quite the comprehensive multi-action list of a 5.	4 / 5
Completeness	Explicitly answers both what (load Phase Index, determine phase/step, pull step detail) and when ('Use when coming back to an in-progress task and you need to know what to do next') with a concrete trigger phrase.	5 / 5
Trigger Term Quality	Natural phrases a user would say — 'Resume work on the current task', 'coming back to an in-progress task', 'need to know what to do next' — with good coverage; a few synonyms (e.g., 'continue', 'pick up where I left off') are absent.	4 / 5
Distinctiveness Conflict Risk	Clear niche (resume/continue an in-progress Trellis task) with distinct triggers and minimal conflict risk; minor overlap possible with generic task-management skills, keeping it just below 5.	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-continue/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.