executing-plans

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

0.75x

Quality

62%

Does it follow best practices?

Impact

21%

0.75x

Average score across 10 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/executing-plans/SKILL.md

Quality

Content

85%

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

This is a well-structured workflow skill that clearly defines a batch execution process with review checkpoints. Its strengths are excellent organization, clear sequencing, and appropriate cross-references to related skills. The main weakness is the lack of concrete examples showing exact tool usage or command syntax for operations like TodoWrite or marking tasks.

Suggestions

Add a concrete example showing the exact syntax for TodoWrite creation and task status updates

Include a sample 'Report' output showing what the batch completion message should look like

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, using bullet points and short phrases. No unnecessary explanations of concepts Claude already knows. Every section serves a clear purpose.	3 / 3
Actionability	Provides clear procedural guidance with specific steps, but lacks concrete code examples or commands. Instructions like 'Create TodoWrite' and 'Mark as in_progress' assume familiarity with tools without showing exact syntax.	2 / 3
Workflow Clarity	Excellent multi-step workflow with clear sequencing (Steps 1-5), explicit validation checkpoints ('Run verifications as specified'), and dedicated sections for when to stop and when to revisit. Includes feedback loops between batches.	3 / 3
Progressive Disclosure	Well-organized with clear sections. References to related skills (git-worktrees, writing-plans, finishing-a-development-branch) are one level deep and clearly signaled in the Integration section. Content is appropriately scoped for an overview.	3 / 3
	Total	11 / 12 Passed

Description

40%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description fails to explain what the skill actually does, focusing only on when to use it. While it includes a 'Use when' clause, the lack of concrete actions and capabilities makes it difficult for Claude to understand what this skill provides. The description needs substantial improvement in specifying actual functionality.

Suggestions

Add specific concrete actions the skill performs (e.g., 'Executes multi-step implementation plans by breaking them into reviewable chunks, tracking progress, and pausing at defined checkpoints')

Include natural trigger terms users would say such as 'execute plan', 'step-by-step implementation', 'checkpoint review', 'phased execution'

Clarify what 'separate session' means and what distinguishes this from general task execution skills

Dimension	Reasoning	Score
Specificity	The description uses vague language like 'execute' and 'implementation plan' without specifying any concrete actions. It doesn't describe what the skill actually does - no verbs indicating specific capabilities.	1 / 3
Completeness	Has a 'Use when' clause addressing when to use it, but the 'what does this do' component is essentially missing. The description only implies execution of plans without explaining the actual capabilities.	2 / 3
Trigger Term Quality	Contains some relevant terms like 'implementation plan', 'session', and 'review checkpoints' that users might mention, but lacks common variations and natural phrasing users would typically use.	2 / 3
Distinctiveness Conflict Risk	The mention of 'separate session' and 'review checkpoints' provides some distinctiveness, but 'implementation plan' and 'execute' are generic enough to potentially overlap with other planning or coding skills.	2 / 3
	Total	7 / 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: roman01la/skills-agents
Commit: 45417f2

Reviewed: 3 months 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.