CtrlK
BlogDocsLog inGet started
Tessl Logo

continue

Use after an execution slice to reassess whether the current tactic still serves the user's north star, then keep course, pivot, replan, or stop. Designed for long-running loops where the agent should keep moving unless a real blocker or completed lane exists.

60

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/continue/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The content is a well-structured, highly actionable governance skill with clear sequencing, explicit validation checkpoints, and a copy-ready output format plus a worked example. Its only weak spot is mild redundancy across the bias/question/rule sections.

DimensionReasoningScore

Conciseness

The body is lean, imperative, and assumes Claude's competence with no padded concept explanations; minor redundancy between Default Bias, Core Questions, and Escalation Rules keeps it just short of fully efficient.

4 / 5

Actionability

Fully actionable for an instruction-only skill: exact state-file fields, explicit verdict conditions, a copy-ready output template, and a complete worked example give concrete executable guidance.

5 / 5

Workflow Clarity

Clear sequenced workflow (Read First → assess → verdict → state update → execute next move) with explicit validation checkpoints and feedback loops, e.g. the Completion Guard and the rule that a checkpoint with a Next move and no blocker must be executed.

5 / 5

Progressive Disclosure

The skill is a single self-contained SKILL.md with no bundle files and is organized into well-labeled sections; structure is good, though no external references are used to split detail.

4 / 5

Total

18

/

20

Passed

Description

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

The description clearly states what the skill does and when to use it, with specific named actions. Its weakness is trigger-term quality: the phrasing relies on internal jargon ('execution slice', 'lane', 'north star') that a user would rarely say aloud, limiting natural discoverability.

Suggestions

Add a 'Use when...' clause with natural user-facing triggers (e.g. 'Use when mid-loop and unsure whether to continue, change tactic, replan, or stop') instead of relying on 'execution slice' jargon.

Include common phrasings a user might actually say (e.g. 'stuck in a loop', 'should I keep going', 'replan the work') to improve natural trigger matching.

Tighten the 'when' framing so it reads as a trigger condition rather than an internal process state.

DimensionReasoningScore

Specificity

Names several concrete actions ('keep course, pivot, replan, or stop') plus the core reassessment action against the north star, giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Both 'what' (reassess tactic, then keep/pivot/replan/stop) and 'when' (after an execution slice, in long-running loops) are explicitly present, though the 'when' is concrete but framed in internal terms rather than natural trigger phrases.

4 / 5

Trigger Term Quality

Triggers ('after an execution slice', 'long-running loops', 'north star', 'lane') are process-internal jargon rather than natural phrases a user would actually say, with no user-facing synonyms.

1 / 5

Distinctiveness Conflict Risk

The keep/pivot/replan/stop verdict vocabulary and 'progress governor' framing give it a recognizable niche, but the broad planning/looping governance concept could still overlap with general planning skills.

3 / 5

Total

13

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
udecode/plate
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.