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.

74

Quality

91%

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

100%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.

The body is a tight, well-structured instruction skill: concrete commands, a sequenced procedure with an explicit check-and-retry loop, and a single real one-level reference for deeper timing data. It hits the top anchor on all four dimensions.

DimensionReasoningScore

Conciseness

Roughly 30 lines of lean, sectioned content that assumes Claude's competence and adds no concept padding; every line (procedure, duration guidance, worked example, reference pointer) earns its place. Not below 5 because nothing reads as filler.

5 / 5

Actionability

Provides concrete executable commands ('wait' advancing 10 steps, 'wait1' 1 step, 'look around', 'examine <OBJECT>') plus a fully worked example with expected output; instruction-only guidance is specific and copy-ready, satisfying the actionability anchor.

5 / 5

Workflow Clarity

A clearly numbered procedure with an explicit validation checkpoint (step 3: check target state) and an explicit feedback loop (step 4: repeat 2-3 if not reached, exit if reached). Not a destructive/batch operation, so no cap applies.

5 / 5

Progressive Disclosure

A concise overview under 50 lines with well-signaled, one-level-deep reference to references/botanical_growth_patterns.md (verified to exist), matching the anchor 5 pattern of clear overview plus clearly pointed deeper material.

5 / 5

Total

20

/

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.

The description is well-constructed: third-person voice, clear capability statement, and an explicit 'Use when' clause with concrete trigger examples. It is slightly short of the top anchor on specificity and trigger breadth given the inherently small action space.

DimensionReasoningScore

Specificity

Names the domain (timed waiting) and concrete actions 'wait'/'wait1' to 'advance the simulation clock'; not 5 because the action space is small (only two wait commands) and verification actions like 'look'/'examine' are omitted from the description.

4 / 5

Completeness

Explicitly answers both 'what' (executes timed waiting via wait/wait1 to advance the simulation clock) and 'when' ('Use when a time-dependent process... must progress before you can continue'), matching the anchor 5 example with concrete trigger phrases.

5 / 5

Trigger Term Quality

The 'Use when a time-dependent process like plant growth, chemical reaction, or mechanical cycle must progress' clause supplies several natural trigger phrases; not 5 because common synonyms/variants a user might say are not exhaustively covered.

4 / 5

Distinctiveness Conflict Risk

The simulation-clock-advancement niche via specific wait/wait1 commands is mostly distinct with only minor overlap risk against other timing/patience skills; not 5 because the broad 'time-dependent process' framing could brush adjacent 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.

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.