CtrlK
BlogDocsLog inGet started
Tessl Logo

scienceworld-conditional-box-placer

Moves an object to one of two destination containers based on a numeric threshold check. Trigger after a measurement (e.g., temperature) is taken. Place object in 'green' box if value > threshold, or 'blue' box if value < threshold.

64

Quality

75%

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-conditional-box-placer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

The content is concise and reasonably structured, but a critical correctness bug routes the below-threshold case to the green box instead of blue, undermining actionability and workflow clarity. Additionally, the existing action_primer.md reference is orphaned and never linked from the body.

Suggestions

Fix the Decision Logic: change the 'measurement_result < threshold' branch to route to the blue box (it currently says green box, contradicting the description and making both branches identical).

Add a reference link to references/action_primer.md from the body (e.g., under Prerequisites or a References section) so the existing bundle file is discoverable rather than orphaned.

Define the equal-to-threshold case (measurement_result == threshold) explicitly, since the current logic only handles > and <, leaving the boundary ambiguous.

DimensionReasoningScore

Conciseness

The body is lean and well-organized across short sections (Purpose, Core Workflow, Required Parameters, Example, Action Template) with no padding or explanation of concepts Claude already knows, matching the score-3 anchor.

3 / 3

Actionability

Concrete parameters, an example invocation thought, and an action template are present, but the Decision Logic directs to the green box in BOTH branches (lines 13-14), making the guidance contradictory and missing the key blue-box detail — matching the score-2 'incomplete / missing key details' anchor rather than 3.

2 / 3

Workflow Clarity

Steps are sequenced (Prerequisites, Decision Logic, Execution) but the decision logic contains a logical error (both branches route to green) and omits the equal-to-threshold case, so the single action is not unambiguous — capping it at 2 rather than 3.

2 / 3

Progressive Disclosure

The body is well-sectioned, but the provided bundle file references/action_primer.md is never referenced or signaled from the body, matching the score-2 anchor 'references present but not clearly signaled' rather than the well-linked score-3 anchor.

2 / 3

Total

9

/

12

Passed

Description

85%

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 specific, distinctive, and explicitly covers both what the skill does and when to trigger it in third-person voice. Trigger-term coverage is the weakest area, being somewhat narrow and domain-internal.

DimensionReasoningScore

Specificity

Lists concrete actions: 'Moves an object to one of two destination containers based on a numeric threshold check' and 'Place object in green box if value > threshold, or blue box if value < threshold' — multiple specific actions, matching the score-3 anchor.

3 / 3

Completeness

Explicitly answers both what ('Moves an object to one of two destination containers based on a numeric threshold check') and when ('Trigger after a measurement (e.g., temperature) is taken') with an explicit trigger clause, so it is not capped at 2.

3 / 3

Trigger Term Quality

Relevant trigger terms appear ('measurement', 'temperature', 'threshold') but coverage is narrow and domain-specific with few common variations a user would naturally say, matching the score-2 anchor.

2 / 3

Distinctiveness Conflict Risk

A narrow, distinctive niche (conditional green/blue box placement after a threshold check) with unique triggers unlikely to conflict with other skills, matching the score-3 anchor.

3 / 3

Total

11

/

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.