CtrlK
BlogDocsLog inGet started
Tessl Logo

scheduling-tasks

Schedules reminders and recurring tasks via the letta cron CLI. Use when the user asks to be reminded of something, wants periodic work or check-ins, or needs to list, inspect, replace, or cancel scheduled tasks.

72

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 high-quality, actionable body: executable commands, real worked examples, and explicit validation steps for fragile operations, organized into clear navigable sections. Minor conciseness redundancy and a missing pre-delete verification step keep it just short of top marks.

Suggestions

Add an explicit verification step before destructive deletes, e.g. 'list/get the task first to confirm the target, then run letta cron delete', since delete and delete --all are irreversible.

De-duplicate the --agent / --conversation default guidance that recurs across 'Where Schedules Run', 'Binding a Task to the Right Conversation', and 'Important Notes' to tighten conciseness.

DimensionReasoningScore

Conciseness

Lean and well-organized, assuming Claude's competence (no padding about what cron or a CLI is); some redundancy across 'Where Schedules Run', 'Binding', and 'Important Notes' on agent/conversation defaults could be tightened further.

4 / 5

Actionability

Fully executable, copy-paste-ready `letta cron` commands with concrete flag values and worked examples (dog-walk, deploy-check, timesheet) covering the common cases, plus a cron reference table.

5 / 5

Workflow Clarity

Clear sequencing with explicit validation for bindings ('Then verify the binding explicitly') and replacement-before-delete guidance; the destructive `delete`/`delete --all` path lacks an explicit pre-delete verification checkpoint, so it sits just below a 5.

4 / 5

Progressive Disclosure

No bundle files are present; the single SKILL.md is cleanly sectioned (When to Use, Where Schedules Run, CLI Usage, Examples, Notes, Cron Reference), meeting the simple-skill bar of well-organized sections without external references.

5 / 5

Total

18

/

20

Passed

Description

92%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, third-person description that states a clear what and an explicit when with concrete, natural trigger phrases. It covers the task lifecycle comprehensively and occupies a well-delineated niche.

DimensionReasoningScore

Specificity

Lists multiple concrete actions spanning the full lifecycle — 'Schedules reminders and recurring tasks' plus 'list, inspect, replace, or cancel scheduled tasks' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both what ('Schedules reminders and recurring tasks via the letta cron CLI') and when ('Use when the user asks to be reminded of something, wants periodic work or check-ins, or needs to list, inspect, replace, or cancel scheduled tasks') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural user phrases such as 'reminded of something', 'periodic work or check-ins', and 'list, inspect, replace, or cancel scheduled tasks'; strong coverage though a few synonyms/extensions (e.g. 'cron', 'timers') are absent.

4 / 5

Distinctiveness Conflict Risk

The letta cron CLI / scheduled-task niche and its reminder-and-check-in triggers are distinct from generic file or document skills, yielding minimal conflict risk.

5 / 5

Total

19

/

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
letta-ai/letta-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.