executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Overall
score
72%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
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 the 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 'run my plan', 'execute steps', 'checkpoint review', 'phased implementation'
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' portion is essentially missing. The description only implies execution of plans without explaining the actual capabilities or actions performed. | 2 / 3 |
Trigger Term Quality | Contains some relevant terms like 'implementation plan', 'execute', 'session', and 'review checkpoints' that users might mention, but lacks common variations and natural phrasing users would typically use. | 2 / 3 |
Distinctiveness Conflict Risk | Terms like 'implementation plan' and 'review checkpoints' provide some specificity, but 'execute' and 'separate session' are generic enough to potentially overlap with other task execution or planning skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
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 process skill with excellent workflow clarity and appropriate conciseness. The main weakness is the lack of concrete examples - showing what a plan file looks like, what a batch report should contain, or what 'verification output' means would make this more actionable. The skill excels at defining when to stop and ask for help, which is critical for execution skills.
Suggestions
Add a concrete example of what a plan file format looks like (even a brief snippet)
Include a sample batch completion report showing the expected format for 'Show what was implemented' and 'Show verification output'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is lean and efficient with no unnecessary explanations. Every section serves a purpose, uses imperative language, and assumes Claude understands concepts like TodoWrite, verification, and batch processing. | 3 / 3 |
Actionability | Provides clear procedural guidance but lacks concrete examples. No sample plan format, no example of what a 'report' looks like, no specific commands or code. Instructions are clear but abstract. | 2 / 3 |
Workflow Clarity | Excellent multi-step workflow with clear sequence (5 steps), explicit checkpoints ('Ready for feedback'), validation requirements, and clear guidance on when to stop and when to revisit earlier steps. Feedback loops are well-defined. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections. References external skill (finishing-a-development-branch) appropriately with one-level-deep linking. Content is appropriately scoped for a SKILL.md overview without being monolithic. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_examples | No examples detected (no code fences and no 'Example' wording) | Warning |
Total | 13 / 16 Passed | |
- 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.