CtrlK
BlogDocsLog inGet started
Tessl Logo

executing-plans

Use when you have a written implementation plan to execute in a separate session with review checkpoints

56

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

70%

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

A well-structured, clearly sequenced workflow skill with strong validation checkpoints, weakened only by some tangential verbosity and guidance that defers concrete verification specifics to the plan and sub-skills.

Suggestions

Trim or relocate the subagent 'Note' and the 'Remember' recap, which restate guidance already covered in the process sections.

Add one or two concrete verification specifics (e.g. example commands or what 'verification' entails) instead of fully deferring to the plan, to lift actionability.

DimensionReasoningScore

Conciseness

The body is mostly lean with terse steps, but the subagent 'Note' paragraph and the 'Remember' recap restate information and add tangential context that could be trimmed.

2 / 3

Actionability

It gives a concrete checklist (mark in_progress, follow steps exactly, mark completed) but defers specifics to the plan ('Run verifications as specified') and to sub-skills, with no concrete verification details of its own.

2 / 3

Workflow Clarity

Steps 1-3 are clearly sequenced with explicit validation checkpoints ('If concerns: Raise', stop conditions, 'When to Revisit Earlier Steps') and feedback loops for blockers, matching the clear-sequence-with-validation anchor.

3 / 3

Progressive Disclosure

No bundle files exist; the body is self-contained and well-organized into clearly labeled sections, satisfying the rubric's simple-skill allowance for progressive disclosure without external references.

3 / 3

Total

10

/

12

Passed

Description

57%

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 concise trigger-style description that covers both what and when, but its second-person voice incurs a specificity penalty and its trigger terms lack breadth and distinctiveness against similar skills.

Suggestions

Rewrite in third person to avoid the specificity penalty, e.g. 'Executes a written implementation plan in a separate session with review checkpoints. Use when a plan exists to be carried out step-by-step with verification.'

Add natural user-side keyword variations such as 'run a plan', 'follow an implementation plan', or 'carry out a plan with review checkpoints' to strengthen trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain and actions ('execute', 'review checkpoints') but is not comprehensive; the second-person 'you' in 'Use when you have a written implementation plan' triggers the rubric's specificity penalty, dropping the base 2 to 1.

1 / 3

Completeness

It explicitly answers both what ('execute... in a separate session with review checkpoints') and when ('Use when you have a written implementation plan'), matching the explicit-trigger anchor.

3 / 3

Trigger Term Quality

'written implementation plan', 'execute', and 'review checkpoints' are reasonably natural keywords a user might say, but coverage lacks common variations and is somewhat internal/meta.

2 / 3

Distinctiveness Conflict Risk

The plan-execution-with-checkpoints niche is fairly distinct, but the trigger could still overlap with other planning or execution skills.

2 / 3

Total

8

/

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
obra/superpowers
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.