auto-reply
Automatic response rules, patterns, and scheduled messages
48
36%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./src/skills/bundled/auto-reply/SKILL.mdQuality
Discovery
14%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 too vague and noun-heavy, lacking concrete actions, explicit trigger guidance, and domain specificity. It reads more like a category label than a functional skill description, making it difficult for Claude to reliably select it over competing skills.
Suggestions
Add specific verbs describing concrete actions, e.g., 'Creates and configures auto-reply rules, sets up scheduled message delivery, and defines response templates.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about auto-replies, autoresponders, canned responses, message scheduling, or automated messaging rules.'
Clarify the platform or domain context (e.g., email, chat, CRM) to reduce conflict risk with other automation-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists abstract nouns ('rules', 'patterns', 'scheduled messages') rather than concrete actions. There are no verbs describing what the skill actually does—no 'create', 'configure', 'send', etc. | 1 / 3 |
Completeness | The description only vaguely hints at 'what' (automatic responses, patterns, scheduled messages) without any specificity, and completely lacks a 'when' clause or explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | Terms like 'automatic response', 'scheduled messages', and 'rules' are somewhat relevant keywords a user might mention, but common variations like 'auto-reply', 'autoresponder', 'canned responses', 'templates', or 'triggers' are missing. | 2 / 3 |
Distinctiveness Conflict Risk | 'Response rules' and 'patterns' are extremely generic terms that could overlap with many skills involving automation, messaging, chatbots, email, or workflow configuration. There is no clear niche established. | 1 / 3 |
Total | 5 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides highly actionable, executable TypeScript examples and clear chat commands, which is its main strength. However, it suffers from being a monolithic reference document that packs too much into a single file without progressive disclosure. It also lacks a clear workflow sequence that ties together rule creation, testing, and enabling with explicit validation steps.
Suggestions
Split the detailed TypeScript API reference and reference tables into a separate API_REFERENCE.md file, keeping SKILL.md as a concise overview with quick-start examples and links to detailed docs.
Add an explicit workflow sequence: 1. Create rule → 2. Test with `/autoreply test` → 3. Verify response with `/autoreply simulate` → 4. Only then enable the rule — to provide validation checkpoints.
Remove the Best Practices section or integrate its points directly into the relevant code examples (e.g., show cooldown usage inline rather than listing 'Set cooldowns' as a tip).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is fairly well-organized but includes a lot of API surface area that could be split into a separate reference file. The reference tables at the end (pattern types, condition types, response variables) add bulk, and the best practices section is generic advice Claude already knows. | 2 / 3 |
Actionability | The skill provides fully executable TypeScript code examples covering simple rules, regex rules, conditional rules, cooldowns, dynamic responses, testing, and CRUD operations. The chat commands are also concrete and copy-paste ready. | 3 / 3 |
Workflow Clarity | While individual operations are clear, there's no explicit workflow for the full lifecycle of creating, testing, and deploying rules. The test/simulate commands exist but aren't integrated into a recommended sequence with validation checkpoints (e.g., 'always test before enabling'). | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of content — chat commands, full TypeScript API reference, pattern types, condition types, response variables, and best practices all in one file. The detailed API reference and tables should be split into separate files with clear navigation from a concise overview. | 1 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- alsk1992/CloddsBot
- Commit
e71a5f6
- 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.