Reminder System Creator - Auto-activating skill for Business Automation. Triggers on: reminder system creator, reminder system creator Part of the Business Automation skill category.
33
Quality
0%
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
0%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 only provides the skill name, a category label, and redundant trigger terms. It completely fails to describe what the skill actually does, what specific capabilities it offers, or when Claude should select it over other skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates automated reminder systems with scheduled notifications, recurring alerts, and deadline tracking'
Include a 'Use when...' clause with natural trigger terms users would say, such as 'remind me', 'set up reminders', 'notification system', 'alert me when', 'deadline reminder'
Specify the types of reminders or automation scenarios this handles to distinguish it from other business automation skills, e.g., 'for email reminders, calendar alerts, task deadlines, or follow-up notifications'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Reminder System Creator') and its category ('Business Automation') without describing any concrete actions. No specific capabilities like 'create scheduled reminders', 'set up notifications', or 'configure recurring alerts' are mentioned. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no meaningful 'when to use' guidance. The 'Triggers on' section just repeats the skill name rather than describing actual use cases or scenarios. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'reminder system creator' repeated twice, which is the skill name itself rather than natural user language. Missing obvious terms users would say like 'remind me', 'set reminder', 'notification', 'alert', 'schedule', 'recurring'. | 1 / 3 |
Distinctiveness Conflict Risk | The vague 'Business Automation' category and lack of specific capabilities means this could easily conflict with any automation, scheduling, or notification-related skills. Nothing distinguishes it from other potential reminder or automation tools. | 1 / 3 |
Total | 4 / 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 content is essentially a placeholder template with no actual instructional value. It contains only meta-descriptions of what a skill should do without providing any concrete guidance, code examples, or workflows for creating reminder systems. The content fails all dimensions by being verbose yet empty of actionable information.
Suggestions
Add concrete code examples showing how to create reminder systems (e.g., cron jobs, scheduled tasks, notification APIs)
Define a clear workflow with steps: 1) Define reminder triggers, 2) Set up storage, 3) Implement notification delivery, 4) Validate scheduling
Include specific examples of reminder system patterns (time-based, event-based, recurring) with executable code
Remove all generic boilerplate text and replace with actual implementation guidance specific to reminder systems
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about reminder systems. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific steps for creating a reminder system. The content only describes what the skill supposedly does without actually instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. There are no steps, no sequence, and no validation checkpoints for creating a reminder system. The 'Capabilities' section mentions 'step-by-step guidance' but provides none. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative document with no meaningful structure. There are no references to detailed materials, examples, or related documentation that would help Claude actually implement reminder systems. | 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 | |
0c08951
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.