CtrlK
BlogDocsLog inGet started
Tessl Logo

soil-extraction

Uses a shovel tool to dig soil from the ground in outdoor environments. Execute this skill when you need to obtain soil for planting tasks and have both the shovel in inventory and access to an appropriate digging location. The skill produces soil that can then be collected and transported.

65

Quality

82%

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

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 concise, highly actionable instruction skill with exact commands, a clear step sequence, and explicit error-handling guidance. The only notable gap is that the bundled trajectory reference is never explicitly linked from SKILL.md, weakening navigation to the bundle.

Suggestions

Link the bundle file explicitly where it is mentioned (e.g., 'as demonstrated in [the trajectory excerpt](references/trajectory_excerpt.md)') so the reference is discoverable from SKILL.md.

Convert the reactive error note into an explicit checkpoint after digging (e.g., 'Verify soil appears nearby before attempting pickup') to strengthen the workflow's validation loop.

DimensionReasoningScore

Conciseness

The body is lean and efficiently organized with no explanation of concepts the agent already knows, but a few phrases could be trimmed (e.g., 'It is a foundational step for planting tasks, transforming a bare outdoor location into a source of usable soil'), placing it just below the fully lean anchor.

4 / 5

Actionability

The guidance is fully executable with exact copy-paste commands covering the common cases: 'use shovel in inventory on ground', 'pick up soil', and 'teleport to outside', including how chaining skills (teleport, move) follow.

5 / 5

Workflow Clarity

The three-step sequence (Navigate, Execute Dig, Collect Output) is clear and the Error Handling section provides recovery guidance ('If no soil appears after digging, verify your location and that the shovel is correctly in your inventory'), but verification is reactive rather than an explicit checkpoint in the flow, so it sits below the top anchor.

4 / 5

Progressive Disclosure

The skill is under 50 lines with well-organized sections (Purpose, Prerequisites, Core Procedure, Key Notes, Error Handling), but the bundle file references/trajectory_excerpt.md exists and is only alluded to ('as demonstrated in the trajectory') without an explicit link, a minor organization gap against the actual bundle structure.

4 / 5

Total

17

/

20

Passed

Description

73%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 solid description that states concrete capabilities and an explicit invocation condition with prerequisites. Its main gaps are limited action coverage, mild second-person phrasing, and missing common synonyms for soil-related trigger terms.

Suggestions

List the concrete actions more fully and consistently in third person (e.g., 'Digs soil from the ground, collects it into inventory, and prepares it for transport and planting') instead of the mild second-person 'when you need to obtain soil'.

Broaden trigger-term coverage with natural synonyms users might say, such as 'dirt', 'earth', 'potting soil', or 'filling pots/planters'.

Reframe the 'when' clause around user-facing triggers (e.g., 'Use when the user asks to get soil or dirt for planting') rather than only internal agent preconditions.

DimensionReasoningScore

Specificity

The description names the domain ('soil extraction with a shovel in outdoor environments') and a couple of concrete actions ('dig soil from the ground', soil that 'can then be collected and transported'), but action coverage is not comprehensive, and the 'when you need to obtain soil' phrasing introduces mild second person.

3 / 5

Completeness

It clearly answers 'what' ('Uses a shovel tool to dig soil from the ground') and includes an explicit 'Execute this skill when...' clause with concrete preconditions, but the 'when' is condition-based rather than natural user trigger phrases, so it falls short of the top anchor.

4 / 5

Trigger Term Quality

Natural keywords are present ('soil', 'dig', 'shovel', 'ground', 'planting') and would match what a user asks for, but common synonyms like 'dirt', 'earth', or 'potting soil' are missing, keeping it just below comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

The niche is narrow and well-delineated — extracting soil with a shovel in outdoor environments for planting — with distinct triggers (shovel in inventory, digging location), so overlap with other skills is minimal.

5 / 5

Total

16

/

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.

Validation — 16 / 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.