CtrlK
BlogDocsLog inGet started
Tessl Logo

scienceworld-planting-operation

Plants seeds into prepared containers with soil to initiate plant growth. Execute this when you have both seeds and properly prepared planting containers available. This skill handles the specific action pattern of transferring seeds from storage to growth containers to begin cultivation processes.

59

Quality

67%

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 ./experiments/src/skills/scienceworld/scienceworld-planting-operation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 skill body is concise and actionable with concrete environment action patterns and a clear workflow, and validation is mentioned for the batch planting operation. Its main weakness is progressive disclosure: two reference files exist but are never linked from the body, and the validation checkpoints are not embedded as explicit inline workflow steps.

Suggestions

Link the existing reference files from the body (e.g., 'See [prerequisite_checklist.md](references/prerequisite_checklist.md)' and 'See [action_patterns.md](references/action_patterns.md)') and avoid duplicating their content inline.

Embed validation as explicit numbered checkpoints in the Core Workflow (e.g., add a 'Verify: examine <container> before planting' and 'Confirm: examine <container> after planting' step) rather than only in Important Notes.

Add a short inline copy-paste example of the full planting command (e.g., 'move banana seed in seed jar to flower pot 1') to make the primary action immediately executable.

DimensionReasoningScore

Conciseness

The body is lean with short, organized sections and does not over-explain concepts Claude already knows. Not a 5 because the Purpose and Core Workflow mildly restate each other and the third description sentence is mildly padded.

4 / 5

Actionability

Provides concrete, executable environment actions ('move OBJ to OBJ', 'examine'/'look at', select option '0', 'seed jar') rather than abstract direction. Not a 5 because the full copy-paste-ready action examples live in the reference file rather than inline.

4 / 5

Workflow Clarity

The Core Workflow lists a clear Prerequisites/Execution/Completion sequence and includes verification ('Always verify the state of the container... before and after planting'), so the batch-operation cap is not triggered. However, the validation checkpoints are stated in Important Notes rather than embedded as explicit inline checkpoints in the numbered sequence, leaving them implicit.

3 / 5

Progressive Disclosure

The body is well-structured into labeled sections and two reference files exist (action_patterns.md, prerequisite_checklist.md), but the body never links to or signals those references, and it inlines prerequisite and action-pattern content that duplicates them. Not a 2 because the body itself is organized rather than a wall of text; not a 4 because the references are not clearly signaled.

3 / 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.

The description clearly states what the skill does and when to use it with a concrete trigger, and occupies a distinct niche. It is slightly held back by restating a single action rather than listing several and by limited trigger synonym coverage.

Suggestions

List a few distinct concrete actions (e.g., examine container, move seed to container, confirm planting) rather than restating 'planting/transferring seeds' to raise specificity.

Add natural trigger synonyms and variations (e.g., 'Use when planting seeds, sowing, or starting plant growth in pots') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain (planting seeds) and 1-2 concrete actions ('Plants seeds into prepared containers', 'transferring seeds from storage to growth containers') but the actions are essentially one operation restated, so coverage is not comprehensive. Not a 4 because it does not list several distinct actions.

3 / 5

Completeness

Clearly answers 'what' (plants seeds into prepared containers to initiate growth) and 'when' (when you have both seeds and properly prepared containers available). Not a 5 because the trigger covers a single condition and lacks the multiple concrete trigger phrasings seen in the top anchor.

4 / 5

Trigger Term Quality

Natural terms like 'seeds', 'prepared planting containers', 'plant growth', and 'cultivation' appear with an explicit trigger ('Execute this when you have both seeds and properly prepared planting containers available'). Not a 5 because common synonyms and variations are limited.

4 / 5

Distinctiveness Conflict Risk

The niche of planting seeds into soil-filled containers is fairly distinct. Not a 5 because it sits adjacent to related skills (seed acquisition, soil preparation, watering) noted in the body, creating minor overlap risk.

4 / 5

Total

15

/

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
zjunlp/SkillNet
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.