CtrlK
BlogDocsLog inGet started
Tessl Logo

execute

Carry an approved task through to working, verified code

48

Quality

52%

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 ./skills/execute/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A compact, well-structured orchestration skill that respects token budget and lays out a clear sequenced workflow with completion checks. Its weakness is actionability: guidance is abstract process direction with no concrete commands, examples, or copy-paste code.

Suggestions

Add one or two concrete examples of an 'independent unit' and how it is delegated (e.g., a sample executor prompt or the exact agent invocation) to lift actionability.

Spell out the verify->fix->retry feedback loop explicitly in the Workflow or Completion section so error recovery is unambiguous.

Show the minimal command or check used to 'verify as you go' (e.g., running the affected test) so the step is executable rather than implied.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: short imperative lines, no explanation of basic concepts, and every section earns its place with no padding.

5 / 5

Actionability

It gives clear directives but no concrete executable code or commands; guidance is procedural ('Break the work into independent units', 'delegate to executor agents') rather than copy-paste ready steps.

3 / 5

Workflow Clarity

The numbered Workflow and Completion sections sequence steps with explicit checkpoints ('Verify as you go', 'Before claiming done: tests pass'), though recovery/feedback loops are implied rather than fully spelled out.

4 / 5

Progressive Disclosure

Under 50 lines with no bundle files, well-organized into labeled sections (Goal, Workflow, Scale, Rules, Completion, Output); the simple-skill exception applies and structure is clear.

5 / 5

Total

17

/

20

Passed

Description

28%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 is grammatically clean and third-person but terse to a fault: it states a single abstract action with no concrete capabilities and no 'Use when...' trigger clause. It is distinguishable as the execution step but weak on trigger-term coverage.

Suggestions

Add concrete actions the skill performs (e.g., 'breaks work into independent units, implements the smallest correct change, verifies as it goes, reports what changed').

Append an explicit 'Use when the work is understood and the job is to build it' clause so the trigger is unambiguous.

Include natural user-facing trigger phrases like 'implement', 'build', 'execute the task', or 'make it work' to improve trigger-term coverage.

DimensionReasoningScore

Specificity

It names the domain ('carry an approved task through to working, verified code') but the action is a single generic phrase ('carry through') rather than multiple concrete capabilities.

2 / 5

Completeness

It states a clear 'what' but has no 'Use when...' clause or equivalent trigger guidance, which the rubric caps at 3; combined with vague phrasing it sits at 2.

2 / 5

Trigger Term Quality

It offers almost no natural trigger keywords a user would say; 'approved task', 'working, verified code' are process jargon rather than the phrases users speak when requesting execution.

2 / 5

Distinctiveness Conflict Risk

'Execute' has a reasonably distinct niche among the routing skills, but the bare phrasing could overlap with general coding/build requests and sibling skills.

3 / 5

Total

9

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Yeachan-Heo/oh-my-claudecode
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.