CtrlK
BlogDocsLog inGet started
Tessl Logo

rewrite-plan

Author a long-running multi-file rewrite plan that subsequent patch-edit + diff-review + build-test stages will execute, with explicit ownership boundaries and patch-safety guarantees.

61

Quality

72%

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 ./plugins/_official/atoms/rewrite-plan/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 content is concise, well-structured, and gives concrete field-level guidance with clear convergence and safety guardrails. Its main gap is the absence of a worked example and an explicit validation feedback loop for the produced plan.

DimensionReasoningScore

Conciseness

The body is lean and well-sectioned with no padding or explanation of concepts Claude already knows; every section (Inputs, Output, Convergence, Anti-patterns, Status) earns its place.

5 / 5

Actionability

Provides a concrete output file tree with exact JSON field shapes and an explicit convergence predicate, but lacks a worked example of an actual steps.json/ownership.json entry that would make it fully copy-paste ready.

4 / 5

Workflow Clarity

Inputs, output, convergence, and anti-patterns are clearly sequenced with an explicit completion checkpoint and a refusal rule for shell-tier files, but there is no explicit validate->fix->retry feedback loop for the plan itself.

4 / 5

Progressive Disclosure

A self-contained skill under 50 lines with no external bundle files, organized into clear well-labeled sections, which per the simple-skill exception warrants a top score.

5 / 5

Total

18

/

20

Passed

Description

58%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 specific and distinct, clearly stating what the skill produces, but it lacks any explicit trigger guidance for when to use it and leans on internal pipeline jargon rather than natural user terms.

Suggestions

Add an explicit 'Use when...' clause naming natural user triggers (e.g., 'Use when refactoring or migrating a multi-file component and a structured plan is needed before editing').

Replace or supplement internal stage jargon ('patch-edit', 'diff-review', 'build-test') with user-facing synonyms like 'refactor', 'migrate', 'rewrite', 'restructure' to improve trigger-term quality.

Include common file/extension or scenario cues so the description surfaces for the right user requests.

DimensionReasoningScore

Specificity

Names a concrete action ('Author a long-running multi-file rewrite plan') plus concrete downstream stages ('patch-edit + diff-review + build-test') and guarantees ('ownership boundaries', 'patch-safety'), but coverage is narrow rather than comprehensive.

4 / 5

Completeness

The 'what' is clear and specific but the 'when' is entirely absent with no 'Use when...' clause or equivalent trigger guidance, which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Contains domain keywords (rewrite plan, patch-edit, diff-review, build-test) but these are internal pipeline jargon rather than natural phrases a user would say, and common synonyms (refactor, migrate, restructure) are missing.

3 / 5

Distinctiveness Conflict Risk

The ownership-boundaries and patch-safety framing carves a clear niche within a multi-stage pipeline, with only minor overlap risk against general refactoring/rewrite-planning skills.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
nexu-io/open-design
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.