CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

create-plan

Create a new plan file in .agents/plans/

Quality

69%

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

Quality

Content

71%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 strongly actionable, well-sectioned skill with copy-paste-ready commands and a clear task sequence; its main weaknesses are duplicated/speculative prose that could be trimmed and a referenced script that is not present in the bundle. It would score solidly across the board with a deduplicated intro and a verification step after file creation.

Suggestions

State the ARCHITECTURE.md read requirement once (in the task steps) and drop the duplicated opening paragraph and the speculative gradient example, which assume PDF-library context Claude does not need here.

Add a final verification step, e.g. 'Confirm the file exists and report its generated `{id}-{slug}.md` path to the user'.

Ensure `scripts/create-plan.ts` actually ships in the skill's `scripts/` directory (or inline the creation as a plain file write) so the referenced path is real.

DimensionReasoningScore

Conciseness

The body is mostly efficient but includes avoidable padding: the ARCHITECTURE.md read instruction is stated twice ("**First, read `.agents/ARCHITECTURE.md`**... This is crucial" and again as task step 1 "**Read ARCHITECTURE.md**"), and the Architecture Considerations section spends ~15 lines on API-layer theory plus a speculative gradient example ("A gradient feature might have...") that is not needed to create a plan file. This fits 'Mostly efficient but includes some unnecessary explanation or could be tightened' rather than score 4's 'minor instances'.

3 / 5

Actionability

The guidance is fully executable: three copy-paste-ready invocations of `bun scripts/create-plan.ts` (direct argument, heredoc, pipe), a concrete output file format example, and a worked slug-to-title transformation ("`my-feature` → `My Feature`"). These cover the common cases exactly as the top anchor requires; there is no pseudocode or vague direction.

5 / 5

Workflow Clarity

The four-step task sequence (read ARCHITECTURE.md → determine slug → gather content → create file) is clear and ordered, and includes a decision checkpoint ("Ask the user if unclear" for the slug). This matches 'Clear sequence with most checkpoints present; minor validation gaps' — the gap is that no step confirms the file was actually created and its path reported back. Score 5 is not earned because there is no explicit post-creation verification, though the operation is low-risk (new-file creation, not destructive/batch), so the workflow-clarity-at-3 cap does not apply.

4 / 5

Progressive Disclosure

The single-file body is well-sectioned, but it references `scripts/create-plan.ts` and `.agents/ARCHITECTURE.md`, and no `scripts/` directory (or any bundle files) exists in the skill bundle, so the primary executable reference cannot be verified. Per the guideline to score against the actual bundle structure, this sits at 'Some structure but could be better organized; references present but not clearly signaled' — below score 4, whose example assumes verifiable, clearly signaled external files.

3 / 5

Total

15

/

20

Passed

Description

53%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 concise and names a concrete, project-specific action, but it is a single bare statement with no trigger guidance and no enumeration of what the skill actually does (ID generation, dating, title formatting). Adding a 'Use when...' clause and 1-2 more capability/trigger phrases would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to create, save, or write a plan for a feature or task.'

Enumerate the concrete capabilities: 'generates a unique three-word ID, adds dated frontmatter, and formats the title from a kebab-case slug'.

Include natural synonyms users would say — 'planning', 'feature plan', 'implementation plan' — to improve trigger-term coverage.

DimensionReasoningScore

Specificity

"Create a new plan file in .agents/plans/" names the domain (plan files, specific directory) and exactly one concrete action, matching the 'Names domain and 1-2 concrete actions, but not comprehensive' anchor. It is above score 2 because the action and target location are concrete rather than generic, but below score 4 because capabilities the skill actually has (dated frontmatter generation, unique ID slugification, title formatting) are absent from the description.

3 / 5

Completeness

The description has a clear 'what' ("Create a new plan file in .agents/plans/") but no 'Use when...' or equivalent trigger guidance, which per the judging guidelines caps completeness at 3. It is not score 2 because the 'what' is specific rather than vague; it cannot be 4 without any explicit 'when' clause.

3 / 5

Trigger Term Quality

"plan" and "plan file" are natural terms a user might say, but the description is missing common variations like "planning", "write a plan", "proposal", or "roadmap". This fits the anchor 'Some relevant keywords but missing common variations or synonyms' — better than score 2 (not purely generic) but not the good coverage of score 4.

3 / 5

Distinctiveness Conflict Risk

The project-specific path ".agents/plans/" gives this a clear niche that generic planning or documentation skills would not match, fitting 'Mostly distinct; minor overlap risk with closely related skills'. It falls short of 5 because without trigger phrases, a request like 'make a plan for X' could plausibly route to other planning/task-management skills.

4 / 5

Total

13

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

15

/

16

Passed

Repository

LibPDF-js/core

Path

.opencode/skills/create-plan/SKILL.md

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.