CtrlK
BlogDocsLog inGet started
Tessl Logo

writing-plans

Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge

66

Quality

79%

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 ./.agency/plugins/nori/skills/writing-plans/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 a well-structured, actionable instruction skill: concrete markdown templates and a test checklist give clear execution guidance, and sections are cleanly organized. It falls just short of top marks due to minor padding, placeholder-dependent templates, and the absence of an explicit plan-level validation checkpoint.

Suggestions

Tighten the Overview by collapsing the three consecutive 'Assume they…' sentences into a single concise assumption statement to remove minor padding.

Add an explicit validation checkpoint in the workflow (e.g., 'Review the plan against the test section before presenting') so the produced plan is verified, not just the tests.

Replace embedded <system-reminder> tags with neutral instructional framing, since those tags are harness-level constructs and may not render as intended in a SKILL.md body.

DimensionReasoningScore

Conciseness

The body is mostly lean — copy-paste markdown templates and terse checklists — but the repeated 'Assume they…' lines and chatty asides ('questionable taste') add minor padding, fitting 'efficient; minor instances of over-explanation' rather than the fully lean 5.

4 / 5

Actionability

It provides concrete, copy-paste-ready header/test/footer templates plus a specific test checklist, but templates carry placeholder brackets and the actual plan content is feature-dependent, matching 'mostly executable guidance; minor gaps'.

4 / 5

Workflow Clarity

A clear Todo sequence (read guidelines → create plan → consider compat/edge cases/questions → emphasize testing → present) and a validation checklist for tests exist, but there is no explicit checkpoint validating the produced plan itself, fitting score 4 over 5.

4 / 5

Progressive Disclosure

The file is self-contained and well-organized with clear section headers (Overview, Header, Test Section, Footer) and no bundle files to reference, matching 'good structure; minor organization gaps'; with no references to signal it does not reach the 5 anchor.

4 / 5

Total

16

/

20

Passed

Description

83%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 strong: it clearly states both the capability and a concrete 'Use when' trigger, with specific deliverables (file paths, code examples, verification steps). Its main limitation is limited synonym/trigger breadth and minor overlap risk with general planning skills.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'exact file paths, complete code examples, and verification steps' — but stops short of comprehensive coverage of the planning skill's full capability set, matching the score-4 anchor rather than 5.

4 / 5

Completeness

It explicitly answers both what ('creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps') and when ('Use when design is complete and you need detailed implementation tasks…') with a concrete trigger phrase, matching the score-5 anchor.

5 / 5

Trigger Term Quality

It surfaces natural phrases a user might say ('design is complete', 'detailed implementation tasks', 'implementation plans'), but lacks synonym breadth, so it fits 'good keyword coverage; a few natural terms missing' rather than the comprehensive 5.

4 / 5

Distinctiveness Conflict Risk

The post-design, zero-context-engineer niche is fairly distinct, but 'implementation plans' overlaps with general planning/coding skills, placing it at 'mostly distinct; minor overlap risk' rather than the minimal-conflict 5.

4 / 5

Total

17

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
microsoft/FluidFramework
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.