CtrlK
BlogDocsLog inGet started
Tessl Logo

alfworld-inventory-management

Use when the agent must collect and track multiple instances of the same object type in ALFWorld (e.g., "put two cellphone in bed"). This skill maintains a count of collected versus needed objects, guides systematic searching through receptacles, and ensures each found object is placed at the target before searching for the next.

72

Quality

88%

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

77%

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

The body is highly actionable with concrete ALFWorld commands, a clear sequenced workflow, and validation checkpoints. Its main weaknesses are mild redundancy of the placement rule and an orphaned reference file that the body never points to.

Suggestions

Link `references/common_mistakes.md` from the body (e.g., add a "Common pitfalls" pointer in Error Handling) so the existing bundle file is discovered and progressive disclosure is one level deep rather than orphaned.

Remove the prose restatement of the placement rule in the §2 "Critical Rule" since the §4 per-object cycle and decision tree already encode it, tightening the document.

Trim or shorten the worked transcript example to the minimum needed to illustrate one full find→place→continue cycle.

DimensionReasoningScore

Conciseness

Mostly efficient and free of generic concept padding, but the immediate-placement rule is restated as prose in the §2 "Critical Rule" and again fully encoded in the §4 per-object cycle, and the transcript example is lengthy — it could be tightened.

2 / 3

Actionability

Provides exact executable commands (`take {object} from {current_receptacle}`, `go to {target_receptacle}`, `put {object} in/on {target_receptacle}`) plus a complete worked transcript that is effectively copy-paste ready.

3 / 3

Workflow Clarity

Clear sequenced workflow (initialize → search → decision tree → per-object cycle) with explicit checkpoints (`collected == needed → TASK COMPLETE`) and an error-handling section with recovery steps for counter mismatches and failed actions.

3 / 3

Progressive Disclosure

The body is well-sectioned but the provided `references/common_mistakes.md` bundle file is never linked or signaled from the body, leaving it orphaned; the body also partially inlines common-mistake content in Error Handling that the reference already covers.

2 / 3

Total

10

/

12

Passed

Description

100%

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 well-crafted description with an explicit trigger clause, concrete capabilities, natural domain task language, and a clearly distinct niche. It concisely answers both what the skill does and when to use it.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: "maintains a count of collected versus needed objects", "guides systematic searching through receptacles", and "ensures each found object is placed at the target before searching for the next" — specific rather than vague.

3 / 3

Completeness

Explicitly answers both what (maintains counts, guides search, ensures placement) and when via a clear "Use when the agent must collect and track multiple instances..." trigger clause.

3 / 3

Trigger Term Quality

Includes natural ALFWorld task language such as "put two cellphone in bed" plus "collect and track multiple instances of the same object type", matching phrases a user/task would actually use.

3 / 3

Distinctiveness Conflict Risk

Scoped tightly to ALFWorld multi-instance object collection, a clear niche with distinct triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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.