CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

plan-generator

Automatically generates a Markdown final-exam review plan or lab experiment schedule when you provide a date range, tasks/items, and available daily hours (via interactive prompts or a one-time JSON input).

Quality

71%

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 ./scientific-skills/Other/plan-generator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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 core usage documentation is strong — executable commands, complete JSON examples for both plan types, and a real script reference with an explicit validation-first workflow. The main weakness is heavy generic boilerplate (roughly 8 template sections that add little skill-specific value) and an inaccurate expected-output block for the --help validation step.

Suggestions

Cut the generic boilerplate sections ('When Not to Use', 'Required Inputs', 'Recommended Workflow', 'Output Contract', 'Validation and Safety Rules', 'Failure Handling', 'Deterministic Output Rules', 'Completion Checklist') and keep only skill-specific guidance; they restate process rules Claude already knows and double the document's length.

Fix or remove the fabricated 'Expected output format' block under 'Quick Validation' — 'python scripts/plan_generator.py --help' prints argparse usage text, not 'Result file: plan_generator_result.md / Validation summary: PASS/FAIL...'.

Merge the duplicate 'Validation Shortcut' and 'Quick Validation' sections into one, and either reference 'scripts/validate_skill.py' (e.g., its --check flag) or drop it from the bundle.

DimensionReasoningScore

Conciseness

Roughly 40% of the body is generic boilerplate ('Do not use this skill when the required source data, identifiers, files, or credentials are missing', 'Recommended Workflow', 'Output Contract', 'Validation and Safety Rules', 'Deterministic Output Rules', 'Completion Checklist') that restates process rules Claude already knows, plus a duplicated validation section ('Validation Shortcut' and 'Quick Validation' both give the same --help command). This matches anchor 2 ('several unnecessary explanations or padded sections') rather than anchor 3's 'some unnecessary explanation'.

2 / 5

Actionability

Commands are copy-paste ready ('python scripts/plan_generator.py --json input.json') and the JSON examples fully cover both plan types and both input modes. Docked one point because the 'Expected output format' block for --help is inaccurate: argparse prints usage text, not 'Result file: plan_generator_result.md / Validation summary: PASS/FAIL...'.

4 / 5

Workflow Clarity

Clear sequence with explicit checkpoints: 'Run this minimal command first to verify the supported execution path', documented input fields per plan type, and a 'Failure Handling' section with recovery steps. Not anchor 5 because the primary validation checkpoint's expected output is fabricated, which weakens the feedback loop.

4 / 5

Progressive Disclosure

A well-organized single-file skill where JSON examples are appropriately inline for this size, and the referenced path 'scripts/plan_generator.py' is a real bundle file. Minor gaps: the duplicate validation sections and the unreferenced bundle file 'scripts/validate_skill.py' keep it at anchor 4 rather than 5.

4 / 5

Total

14

/

20

Passed

Description

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

A specific, well-scoped description that clearly states what the skill does and its required inputs, with good natural trigger terms. Main weaknesses are the second-person 'when you provide' phrasing (violating third-person voice guidance) and a few missing common synonyms like 'study plan' or 'timetable'.

Suggestions

Rewrite in third person to avoid the second-person penalty: e.g., 'Generates a Markdown final-exam review plan or lab experiment schedule from a date range, tasks/items, and available daily hours, via interactive prompts or a one-time JSON input.'

Add natural trigger synonyms users would say, such as 'study plan', 'revision schedule', or 'timetable', and a scenario-based trigger clause like 'Use when planning exam study time or scheduling lab experiments across a date range.'

DimensionReasoningScore

Specificity

The description names concrete capabilities ('generates a Markdown final-exam review plan or lab experiment schedule', 'date range, tasks/items, and available daily hours', 'interactive prompts or a one-time JSON input'), placing it at anchor 4; however, 'when you provide a date range...' uses second-person voice, which the rubric guideline penalizes by 1 point. It is well above anchor 2 because the domain and actions are specific, not generic.

3 / 5

Completeness

The 'what' is clear (generates Markdown review plans or lab schedules) and an explicit when-clause exists ('when you provide a date range, tasks/items, and available daily hours'), so it is not capped at 3; but the trigger is input-condition-based rather than scenario-based ('Use when you need a study schedule...'), matching anchor 4 rather than anchor 5.

4 / 5

Trigger Term Quality

Good natural keyword coverage: 'final-exam review plan', 'lab experiment schedule', 'date range', 'daily hours', 'JSON'. A few natural synonyms users would say are missing (e.g., 'study plan', 'timetable', 'revision schedule'), which matches anchor 4 rather than anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The description carves a clear niche (exam review planning and lab experiment scheduling) with distinct trigger terms, so conflict risk is minor — matching anchor 4. It falls short of anchor 5 only because it could still overlap with generic calendar/planner skills.

4 / 5

Total

15

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Other/plan-generator/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.