CtrlK
BlogDocsLog inGet started
Tessl Logo

controlled-waiting

Executes timed waiting using 'wait' or 'wait1' actions to advance the simulation clock. Use when a time-dependent process like plant growth, chemical reaction, or mechanical cycle must progress before you can continue the task.

76

Quality

93%

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

87%

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

Concise and actionable with a clean worked example and a well-signaled reference, but the workflow lacks error-recovery for the stalled case — its primary failure mode — which the bundled reference addresses but the body does not surface.

Suggestions

Add an explicit stalled-progress escalation step to the Procedure: e.g., 'If the target state is not reached after two wait cycles, stop waiting and investigate environmental prerequisites (pollinators, water, light, containment) before resuming.'

Surface the reference's key insight — that some transitions require environmental triggers in addition to time — in the body's Procedure or Duration guidance so Claude does not loop indefinitely on a trigger-gated stage like fruit set.

Expand the reference pointer to note it also covers stalled-progress troubleshooting, not just growth-stage timings, improving navigation signaling toward the error-recovery guidance.

DimensionReasoningScore

Conciseness

The body is lean with no concept explanations Claude already knows; every section (When to Use, Procedure, Duration guidance, Example) earns its place and avoids padding.

3 / 3

Actionability

Gives concrete, executable commands with explicit semantics — 'wait (advances 10 steps)', 'wait1 (1 step)', 'look around', 'examine <OBJECT>' — plus a fully walked-through example, all copy-paste ready for the simulation domain.

3 / 3

Workflow Clarity

The sequence is clear with an explicit check (look around/examine) and a repeat loop, but the only failure path is 'not reached, repeat' — there is no termination or escalation guidance for a permanently stalled process, which the reference shows is a real scenario.

2 / 3

Progressive Disclosure

A concise overview body with a single, clearly signaled one-level-deep reference (references/botanical_growth_patterns.md, verified present) that exists and is relevant; content is appropriately split for a sub-50-line skill.

3 / 3

Total

11

/

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 strong, well-structured description: third-person voice, concrete commands, an explicit 'Use when' trigger, and a distinct simulation niche. It matches the good-example pattern with no over-claims or fluff.

DimensionReasoningScore

Specificity

Names concrete actions — 'wait' or 'wait1' actions to advance the simulation clock' — with the specific step granularity of each, matching the anchor for multiple specific concrete actions.

3 / 3

Completeness

Explicitly answers both: what it does ('Executes timed waiting...') and when to use it via a clear 'Use when...' clause with concrete triggers, matching the top anchor.

3 / 3

Trigger Term Quality

Covers natural trigger domains a user would name — 'plant growth, chemical reaction, or mechanical cycle' plus 'time-dependent process' — giving good coverage of recognizable terms rather than jargon.

3 / 3

Distinctiveness Conflict Risk

The simulation-clock-advancement niche via wait/wait1 is clearly distinct and unlikely to trigger for unrelated skills; it carves a specific, non-overlapping role.

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.