CtrlK
BlogDocsLog inGet started
Tessl Logo

loop

Schedule a prompt to fire on a fixed cadence (recurring loop). Use when the user asks to "run X every N minutes/hours/days", "loop X", "babysit Y", "be proactive about Y every N", or invokes `/loop` directly. Parses `[interval] <prompt>`, picks a clean cron expression, registers the job via the `cron` tool, and executes the prompt once immediately so the user sees activity without waiting for the first cron tick.

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

88%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 content is a tight, highly actionable procedure: deterministic parsing rules, an exact cron mapping with justified rounding behavior, and an examples table that covers the common and edge cases. Structure is clean and every section is needed at execution time. The only real levers are trimming minor redundancy and, if the skill grows, moving the examples or cron table into a reference file.

DimensionReasoningScore

Conciseness

The body is efficient and adds genuinely non-obvious knowledge (cron divisibility quirks, rounding rules), but minor trimming is possible: the sample rounding messages and parts of the 'Do not' section restate guidance already given inline.

4 / 5

Actionability

Fully executable guidance: an exact regex ('^\d+[smhd]$'), a literal interval-to-cron mapping table, explicit tool-call parameters, and a worked examples table covering common and edge cases (default interval, 30s, 7m rounding, empty input).

5 / 5

Workflow Clarity

Steps 1–7 are clearly sequenced with an explicit validation checkpoint (empty or interval-only input → usage hint and stop), mandatory disclosure of rounding, and ordering ('After the cron call succeeds') before the immediate execution step. The operation is non-destructive, so no validation cap applies.

5 / 5

Progressive Disclosure

Sections are well-organized and all content (parsing rules, cron table, examples) earns its place inline with no buried references. It scores 4 rather than 5 because the body is ~78 lines — above the under-50-line simple-skill bar that would justify a 5 on organization alone, and no reference split is used.

4 / 5

Total

18

/

20

Passed

Description

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

A strong description: concrete, third-person action statements paired with an explicit and varied 'Use when' trigger clause. Voice is consistently third person and there is no fluff or over-claiming. The only gaps are a few missing natural synonyms and slight overlap with adjacent scheduling skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'Parses [interval] <prompt>', 'picks a clean cron expression', 'registers the job via the cron tool', 'executes the prompt once immediately' — with comprehensive coverage of the skill's mechanics, matching the top anchor rather than the level-4 'minor gaps' anchor.

5 / 5

Completeness

It explicitly answers both questions: what ('Schedule a prompt to fire on a fixed cadence... parses, picks a cron expression, registers the job, executes the prompt once immediately') and when ('Use when the user asks to... or invokes /loop directly') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Trigger phrases like 'run X every N minutes/hours/days', 'loop X', 'babysit Y', and 'be proactive about Y every N' are natural user phrasings, but common synonyms such as 'recurring', 'on a schedule', or 'keep doing X' are missing, so it falls just short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

The recurring-cadence niche with triggers like 'loop X' and 'babysit Y' is mostly distinct, but 'run X every N' phrasing carries minor overlap risk with closely related one-shot or natural-language scheduling skills.

4 / 5

Total

18

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
XiaomiMiMo/MiMo-Code
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.