CtrlK
BlogDocsLog inGet started
Tessl Logo

scienceworld-recipe-retriever

This skill locates and acquires a recipe or instruction document by using 'pick up' on the recipe object. Use when the task involves following a specific procedure (e.g., crafting, mixing) and the agent needs to obtain the written instructions. The skill assumes the recipe is visible in the current room and moves it to the inventory, allowing the agent to read it later to understand required ingredients and steps.

69

Quality

87%

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

85%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, well-sequenced skill body with explicit validation and error recovery for a simple single-purpose task. Its main weakness is bundle integration: two useful reference files exist but are completely unlinked, so their content (additional error messages, teleport-based search) is undiscoverable from SKILL.md.

Suggestions

Add a short 'References' section linking references/action_primitives.md (action semantics, error messages like "Your inventory is full") and references/trajectory_analysis.md (search strategy, observation patterns) so the bundle content is discoverable.

Incorporate or link the additional error cases from action_primitives.md (e.g., "Your inventory is full" requiring inventory management) into the Error Handling section.

Trim the Trigger Conditions section, which largely duplicates the frontmatter description's 'Use when...' clause, to reduce token overhead.

DimensionReasoningScore

Conciseness

The body is lean with concrete commands throughout, but "Trigger Conditions" largely restates the description's use-when clause and "This skill assumes the recipe is visible and accessible" repeats the frontmatter — minor instances that could be trimmed.

4 / 5

Actionability

Fully executable guidance: `look around`, `pick up <recipe_object>`, and `read recipe for red paint`, plus a worked example with the exact expected observation ("You move the recipe for red paint to the inventory.") covering the common case.

5 / 5

Workflow Clarity

Three clearly sequenced steps with an explicit validation checkpoint ("Confirm the recipe is now in your inventory before proceeding") and a feedback loop in Error Handling (pick up fails → examine the object; not found → expand search). The simple-skill exception applies and the single task is unambiguous.

5 / 5

Progressive Disclosure

The body itself is well-organized and self-sufficient, but the bundle's references/action_primitives.md and references/trajectory_analysis.md — containing complementary content like the `teleport` search action, the "Your inventory is full" error, and observation patterns — are never referenced or signaled anywhere in the body.

3 / 5

Total

17

/

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.

A strong description: third-person, concrete about the mechanism and outcome, with an explicit 'Use when...' clause and concrete example triggers. Minor improvements possible by naming the survey action and tightening the 'when' trigger to reduce overlap with general procedure-following tasks.

DimensionReasoningScore

Specificity

Names several concrete actions — "locates and acquires a recipe or instruction document by using 'pick up' on the recipe object", "moves it to the inventory" — but omits the locate/survey mechanism (e.g., 'look around'), leaving minor gaps in coverage.

4 / 5

Completeness

Explicitly answers both what ("locates and acquires a recipe... by using 'pick up'... moves it to the inventory") and when ("Use when the task involves following a specific procedure (e.g., crafting, mixing) and the agent needs to obtain the written instructions") with concrete trigger phrasing.

5 / 5

Trigger Term Quality

Includes natural domain terms like "recipe", "instruction document", "crafting, mixing", and "written instructions", but misses common synonyms such as 'manual', 'formula', or 'blueprint'.

4 / 5

Distinctiveness Conflict Risk

The recipe-acquisition niche with inventory scoping is mostly distinct, but the trigger "task involves following a specific procedure" is broad enough to minorly overlap with procedure-execution or document-reading skills.

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.

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.