auto-reply
Automatic response rules, patterns, and scheduled messages
62
47%
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 incomplete to effectively guide skill selection. It lacks concrete actions, explicit trigger conditions, and distinctive terminology. The generic terms used ('rules', 'patterns', 'messages') would likely cause conflicts with other automation or messaging-related skills.
Suggestions
Add specific concrete actions like 'Create auto-reply rules, configure message scheduling, set up pattern-based triggers' to clarify what the skill actually does.
Include a 'Use when...' clause with explicit triggers such as 'Use when the user asks about auto-replies, scheduled messages, email rules, or automated responses.'
Add distinctive context about the platform or system this applies to (e.g., email, chat, notifications) to reduce conflict risk with other automation skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract language ('rules', 'patterns', 'messages') without specifying concrete actions. It doesn't explain what actions can be performed with these concepts. | 1 / 3 |
Completeness | The description only vaguely hints at 'what' (automatic responses and scheduling) but provides no 'when' clause or explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords ('automatic', 'response', 'scheduled messages') but lacks common variations users might say like 'auto-reply', 'cron', 'automation', 'triggers', or specific platform terms. | 2 / 3 |
Distinctiveness Conflict Risk | 'Response rules' and 'patterns' are extremely generic terms that could overlap with many skills involving automation, messaging, regex patterns, or rule-based systems. | 1 / 3 |
Total | 5 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured API reference with excellent actionability and conciseness. The code examples are complete and executable, and the tables provide quick lookup for pattern and condition types. However, it lacks explicit workflow guidance for the recommended create-test-enable cycle and could benefit from progressive disclosure by splitting into overview and detailed reference files.
Suggestions
Add a workflow section showing the recommended sequence: create rule -> test with `/autoreply test` -> verify response -> enable rule
Consider splitting into SKILL.md (quick start + common patterns) and REFERENCE.md (full API details) to improve progressive disclosure
Add a validation step or warning about testing regex patterns before enabling rules that could match unintended messages
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presenting commands and code without unnecessary explanation. It assumes Claude understands TypeScript, regex, and API patterns without explaining basic concepts. | 3 / 3 |
Actionability | Provides fully executable TypeScript code examples that are copy-paste ready. Commands are specific with clear syntax, and code examples include complete import statements and configuration objects. | 3 / 3 |
Workflow Clarity | While individual operations are clear, there's no explicit workflow for creating and validating rules. The 'Test Rule' section exists but isn't integrated into a recommended workflow (create -> test -> enable). Missing validation checkpoints for rule creation. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and tables, but it's a monolithic reference document. Could benefit from splitting detailed API reference into a separate file, keeping SKILL.md as a quick-start overview with links to full reference. | 2 / 3 |
Total | 10 / 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
2a8c94e
- 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.