scheduler
Schedule on-device reminders and local actions only. Use this skill to set personal reminders or run lightweight, local tasks at a specific time or interval (e.g., notifications, local scripts), on the user's computer or with platforms like Slack. Do NOT use for scheduling cloud agents, background agentic jobs, or Oz-managed workflows.
67
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
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.
This is an excellent skill description that clearly defines its scope, provides concrete examples of use cases, and explicitly distinguishes itself from related but different skills through negative guidance. The description uses proper third-person voice and includes natural trigger terms users would actually say.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'set personal reminders', 'run lightweight, local tasks', 'notifications', 'local scripts'. Also specifies platforms like 'user's computer' and 'Slack'. | 3 / 3 |
Completeness | Clearly answers both what ('schedule on-device reminders and local actions') and when ('Use this skill to set personal reminders or run lightweight, local tasks at a specific time or interval'). Also includes explicit negative guidance on when NOT to use it. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'reminders', 'notifications', 'local scripts', 'specific time', 'interval', 'Slack'. These are terms users naturally use when requesting scheduling functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear boundaries: explicitly scoped to 'on-device', 'local', and includes explicit exclusions ('Do NOT use for scheduling cloud agents, background agentic jobs, or Oz-managed workflows') that prevent conflicts with cloud scheduling skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a well-structured conceptual framework for scheduling but falls short on actionability—it describes capabilities without providing executable code or commands. The content is verbose with OS explanations Claude already knows, and the workflow lacks validation steps for system-modifying operations.
Suggestions
Add concrete, executable code examples for each OS: a complete launchd plist for macOS, a cron entry command for Linux, and a PowerShell Task Scheduler command for Windows
Add a validation step after creating scheduled items (e.g., 'Verify the schedule was created: `crontab -l | grep <name>`')
Move the detailed OS-specific sections to a separate BACKENDS.md file and keep only a brief summary in the main skill
Remove explanatory text about what cron, launchd, and Task Scheduler are—Claude knows these tools
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably organized but includes unnecessary explanations Claude would know (e.g., what cron is, what launchd does, basic OS concepts). The OS-specific sections are verbose and could be condensed significantly. | 2 / 3 |
Actionability | The skill describes what to do conceptually but provides no executable code examples. There are no actual commands for creating launchd plists, cron entries, or Windows scheduled tasks—only descriptions of capabilities. | 1 / 3 |
Workflow Clarity | The 6-step workflow is clearly sequenced and logical, but lacks validation checkpoints. For scheduling operations that modify system state, there's no verify-after-create step or error recovery guidance. | 2 / 3 |
Progressive Disclosure | Content is organized with clear sections and headers, but everything is inline in one large file. The OS-specific details and Slack configuration could be split into separate reference files to keep the main skill leaner. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 13 / 16 Passed | |
- 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.