executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Install with Tessl CLI
npx tessl i github:projectbluefin/dakota --skill executing-plans26
Quality
62%
Does it follow best practices?
Impact
21%
0.75xAverage score across 10 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./.opencode/skills/executing-plans/SKILL.mdDiscovery
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 or capabilities makes it difficult for Claude to understand what this skill provides. The description needs to specify what actions are performed during plan execution and what 'review checkpoints' entail.
Suggestions
Add specific concrete actions describing what the skill does (e.g., 'Executes multi-step implementation plans by breaking them into phases, running code changes, and pausing at defined checkpoints for user review')
Include natural trigger terms users would say, such as 'run my plan', 'execute steps', 'phased implementation', 'checkpoint review', or 'step-by-step execution'
Clarify the unique value proposition - what makes this different from simply following instructions or other 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 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 workflow skill that excels at defining a clear process with appropriate checkpoints and error handling. The content is concise and well-organized with good progressive disclosure. The main weakness is the lack of concrete executable examples, though for a process-oriented skill this is less critical than for a technical implementation skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, using short imperative sentences and bullet points. 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 copy-paste commands. The instructions are specific but remain at the process level rather than executable level. | 2 / 3 |
Workflow Clarity | Excellent multi-step workflow with clear sequencing (Steps 1-5), explicit validation checkpoints ('Run verifications as specified'), and well-defined stopping conditions. Includes feedback loops and clear guidance on when to stop and ask for help. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections and appropriate references to related skills (using-git-worktrees, writing-plans, finishing-a-development-branch). Content is appropriately scoped with one-level-deep references clearly signaled in the Integration section. | 3 / 3 |
Total | 11 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.