CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

scheduling-tasks

Advanced scheduling through the letta cron CLI for other conversations, computers, run history, and schedule replacement. Use Wake for ordinary create/list/cancel operations in the current conversation.

Quality

84%

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

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

A highly actionable, well-organized CLI reference whose commands and worked examples are copy-paste ready and whose risky operations (binding, replacement, deletion) carry explicit verification steps. The main improvements are trimming repeated binding explanations and generic cron background, and offloading the cron reference or examples into separate files.

Suggestions

Consolidate the --conversation/--agent binding semantics into the 'Binding a Task to the Right Conversation' section and reference it from the flag table and Important Notes instead of restating it three times.

Move the cron expression reference (and optionally the extended examples) into a references/ file linked from a short inline summary, keeping SKILL.md as a leaner overview.

Add a general post-create verification step (e.g. confirm the task via 'letta cron get <name>') to the main creation flow and examples.

DimensionReasoningScore

Conciseness

Mostly tight, tool-specific content with minor over-explanation: the standard cron field diagram and 'common patterns' list partially re-teach concepts Claude already knows, and the --conversation binding defaults are explained in three places (flag table, binding section, Important Notes). Not 3 because there is no conceptual padding about scheduling itself; not 5 because roughly 15% of the body could be trimmed without loss.

4 / 5

Actionability

Fully executable, copy-paste-ready commands throughout, with complete flag tables and five worked examples covering the common cases (recurring reminder, one-shot check, weekday-shifted timesheet, list, cancel). This matches the 5 anchor: specific examples cover the common cases with concrete values.

5 / 5

Workflow Clarity

Explicit checkpoints exist for the risky flows ('Then verify the binding explicitly', 'create and verify the replacement before deleting the old one') and failure modes are surfaced (TARGET_DEVICE_UNAVAILABLE, bare --at rolling to tomorrow), so the destructive-operation cap does not apply. Not 5 because there is no validate-fix-retry feedback loop and the main creation examples omit a verification step.

4 / 5

Progressive Disclosure

A well-sectioned, navigable single file with no nested references and every section clearly signaled. Not 3 because organization is genuinely good and nothing is buried; not 5 because at 214 lines with an inlined cron expression reference and extended examples, some content could be split into one-level-deep reference files.

4 / 5

Total

17

/

20

Passed

Description

78%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 with a specific tool niche, multiple concrete capability targets, and excellent boundary guidance against a conflicting sibling skill. Its main weaknesses are the absence of natural trigger synonyms like 'reminder' or 'recurring' and the lack of a direct 'Use when...' clause for this skill.

Suggestions

Add a direct trigger clause, e.g. 'Use when the task must run in another conversation, on a connected computer, or when you need run history or schedule replacement.'

Include natural synonyms users actually say, such as 'reminders', 'recurring tasks', or 'one-shot scheduled prompts', to improve trigger matching.

DimensionReasoningScore

Specificity

Names the tool ('letta cron CLI') and several concrete capability targets ('other conversations, computers, run history, and schedule replacement') with minor gaps. It falls short of 5 because the core verbs (create, list, manage) are only implied by 'scheduling', and above 3 because it enumerates multiple distinct capabilities rather than 1-2 actions.

4 / 5

Completeness

A clear 'what' is paired with explicit routing guidance via the Wake boundary sentence, which implies when this skill applies. Not 5 because there is no direct 'Use when...' trigger phrasing for this skill itself; not 3 because the 'when' is explicitly disambiguated rather than only weakly implied.

4 / 5

Trigger Term Quality

Good natural keyword coverage ('scheduling', 'cron', 'create/list/cancel'), but misses common user phrasings such as 'reminder', 'recurring', or 'timer'. Not 3 since coverage is genuinely good rather than partial; not 5 because key synonyms users naturally say for this use case are absent.

4 / 5

Distinctiveness Conflict Risk

'letta cron CLI' carves a clear niche and the second sentence explicitly resolves the overlap with the sibling Wake skill ('Use Wake for ordinary create/list/cancel operations in the current conversation'), giving minimal conflict risk. This matches the 5 anchor's clear niche with distinct triggers.

5 / 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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

letta-ai/letta-code

Path

src/skills/builtin/scheduling-tasks/SKILL.md

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.