Reminder System Creator - Auto-activating skill for Business Automation. Triggers on: reminder system creator, reminder system creator Part of the Business Automation skill category.
35
3%
Does it follow best practices?
Impact
93%
1.06xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/19-business-automation/reminder-system-creator/SKILL.mdQuality
Discovery
7%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 description is essentially a placeholder with no substantive content. It repeats the skill name as its only trigger term, provides no concrete actions or capabilities, and lacks any explicit guidance on when Claude should select this skill. It fails on nearly every dimension of the rubric.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates automated reminder systems with scheduled notifications, recurring alerts, and deadline tracking for business workflows.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about setting up reminders, scheduling alerts, notification systems, deadline tracking, or recurring task automation.'
Remove the duplicate trigger term and replace with varied natural language terms users would actually say, such as 'reminders', 'alerts', 'notifications', 'schedule', 'deadline', 'follow-up'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Reminder System Creator') and its category ('Business Automation') but provides no concrete actions like creating reminders, scheduling notifications, managing recurring tasks, etc. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no 'Use when...' clause and no description of actual capabilities beyond the skill name. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('reminder system creator, reminder system creator'). No natural user language like 'set a reminder', 'schedule alerts', 'notification system', or 'recurring reminders' is included. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'reminder system' is somewhat specific and wouldn't broadly conflict with many other skills, but the lack of detail about what kind of reminder system (email, calendar, task-based, etc.) leaves some ambiguity. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty shell with no substantive content. It consists entirely of meta-descriptions about what the skill supposedly does without providing any actual instructions, code, examples, or workflows for creating a reminder system. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable code examples showing how to create a reminder system (e.g., using cron jobs, scheduling libraries, or calendar APIs with specific implementation code).
Define a clear multi-step workflow for building a reminder system, including steps like defining reminder triggers, setting up storage, scheduling notifications, and validating the system works.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') and replace them with actual actionable content—specific patterns, configurations, and implementation details.
If the topic is broad, provide a concise quick-start section and link to separate files for advanced topics like recurring reminders, notification channels, or persistence strategies.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual instructions, code, or concrete guidance. Every section restates the same vague information. | 1 / 3 |
Actionability | There is zero actionable content—no code, no commands, no specific steps, no examples of how to actually create a reminder system. The 'Example Triggers' section just shows how to invoke the skill, not how to accomplish anything. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed materials, no links to supporting files, and no structured navigation to deeper content. | 1 / 3 |
Total | 4 / 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 — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
4dee593
Table of Contents
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.