CtrlK
BlogDocsLog inGet started
Tessl Logo

scienceworld-task-parser

Analyzes user instructions in ScienceWorld environments to extract specific task requirements and constraints. Use when receiving a new task to identify required objects, target locations, and action sequences before taking any environment actions.

69

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is lean, highly actionable, and clearly sequenced with a verification checkpoint, but it underuses its own reference bundle — task_patterns.md is orphaned rather than linked from the overview.

Suggestions

Add a one-line pointer to the reference bundle, e.g. under step 1: 'See [task_patterns.md](references/task_patterns.md) for common instruction templates and the object/action mapping', so the existing reference is discoverable.

Consider moving the Object Classification detail (currently only in the reference) into a brief inline disambiguation note or explicitly linking to it where Target Object Type is identified.

DimensionReasoningScore

Conciseness

The body is lean, gives concrete commands in each section, and avoids explaining concepts Claude already knows; the only mild redundancy is the worked example re-walking the steps, which still earns its place.

3 / 3

Actionability

Provides concrete, copy-paste-ready ScienceWorld commands throughout ('teleport to LOC', 'focus on OBJ', 'move OBJ to OBJ', 'pour OBJ into OBJ') and a fully worked example with a named object (battery).

3 / 3

Workflow Clarity

Clear numbered sequence (Parse, Survey, Identify, Execute) with an explicit Verification principle allowing a second 'look around'; the task is non-destructive, so the missing error-recovery loop does not cap the score.

3 / 3

Progressive Disclosure

The body is well-organized into clear sections, but the bundled references/task_patterns.md (which catalogs parse patterns and an action map) is never referenced or linked from the body, so the reference is present but not clearly signaled.

2 / 3

Total

11

/

12

Passed

Description

75%

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 well-structured with a clear what/when split and a distinct ScienceWorld niche, but its action language is somewhat abstract and its trigger terms rely on domain jargon rather than natural user phrasings.

Suggestions

Replace abstract verbs with concrete actions the skill performs, e.g. 'parse task instructions, classify objects, and plan action sequences' to lift specificity.

Add natural-language trigger variations a user might actually say (e.g. 'Use when given a ScienceWorld task like find-and-move or mix substances') to broaden trigger term coverage.

DimensionReasoningScore

Specificity

Names the ScienceWorld domain and several extraction targets ('required objects, target locations, and action sequences'), but the verbs are abstract ('extract', 'identify') rather than a comprehensive list of concrete actions, matching the 'names domain and some actions' anchor.

2 / 3

Completeness

Clearly states what it does ('Analyzes user instructions... to extract specific task requirements and constraints') and when to use it via an explicit 'Use when...' clause, satisfying both what and when.

3 / 3

Trigger Term Quality

Includes an explicit 'Use when receiving a new task' trigger, but leans on environment jargon ('ScienceWorld environments', 'task requirements and constraints') and misses common user phrasings, fitting 'some relevant keywords but missing common variations.'

2 / 3

Distinctiveness Conflict Risk

The 'ScienceWorld environments' framing carves out a clear niche with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

10

/

12

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.