CtrlK
BlogDocsLog inGet started
Tessl Logo

executing-plans

当你有一份书面实现计划需要在单独的会话中执行,并设有审查检查点时使用

56

Quality

65%

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/executing-plans/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a well-sequenced, actionable execution workflow with strong validation checkpoints and feedback loops. Its main weakness is redundancy between the notes, stop-conditions, and error-handling sections.

Suggestions

Merge the '注意事项' section into the relevant process steps or trim it to non-duplicative items only, since most points restate earlier guidance.

Cut or condense the upstream/downstream meta-commentary in '常见异常处理'; it does not advance execution.

Consider moving the long worked examples (review example, task-rhythm block, report template) into a references file to tighten the SKILL.md overview.

DimensionReasoningScore

Conciseness

The body is mostly efficient and process-focused without explaining concepts Claude already knows, but the '注意事项' section repeats points already made earlier and the '常见异常处理' section overlaps with '何时停下来求助', plus the upstream/downstream meta-commentary adds little.

3 / 5

Actionability

Concrete, executable guidance is provided throughout — real commands in the task-rhythm example ('npm test -- --grep validation', 'git commit -m "feat: ...(任务 2/5)"'), a ready-to-use review example, and a completion-report template — with only minor gaps.

4 / 5

Workflow Clarity

A clear three-step sequence with explicit validation checkpoints (per-task '运行验证', review checklist), feedback loops for error recovery (stop when a test fails 2+ times, fix-before-continuing self-check), and checklists (review checklist, notes) for a batch-execution skill.

5 / 5

Progressive Disclosure

Well-organized into clearly headed sections (概述, 流程, 何时停下来求助, 异常处理, 注意事项) with no nested references and clearly signaled cross-skill links; the long inline example templates could arguably live in reference files, hence not a 5.

4 / 5

Total

16

/

20

Passed

Description

57%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 provides an explicit, condition-rich trigger clause and a distinct niche, but the 'what' is brief and the phrasing uses second-person voice, which costs it specificity. Overall a solid but improvable description.

Suggestions

Rewrite in third person to avoid the second-person voice penalty, e.g. 'Executes a written implementation plan in an isolated session with review checkpoints. Use when a written plan must be carried out step-by-step with verification gates.'

Expand the 'what' with the skill's core actions (load, critically review, execute all tasks, report) so the capability is as explicit as the trigger.

Add a couple of natural trigger synonyms (e.g. 'follow a plan', 'carry out an implementation plan') to broaden keyword coverage.

DimensionReasoningScore

Specificity

The description names the domain ('书面实现计划...执行') and one concrete action (execute) plus conditions (separate session, review checkpoints), which would be a 3, but it uses second-person voice ('当你有一份...' / 'when you have'), which the guidelines penalize by reducing specificity by 1.

2 / 5

Completeness

Both 'what' (execute the plan) and an explicit, detailed 'when' ('当你有一份书面实现计划需要在单独的会话中执行,并设有审查检查点时使用') are present; the 'when' is strongly explicit while the 'what' is somewhat brief.

4 / 5

Trigger Term Quality

Relevant natural terms are present ('实现计划', '执行', '单独的会话', '审查检查点') that a user might say, but coverage is fairly narrow with few synonyms or common variations.

3 / 5

Distinctiveness Conflict Risk

The niche is fairly distinct thanks to specific triggers (written plan, separate session, review checkpoints), with only minor overlap risk against closely related planning/execution skills like subagent-driven-development referenced in the body.

4 / 5

Total

13

/

20

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.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository
jnMetaCode/superpowers-zh
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.