auto-reply

Automatic response rules, patterns, and scheduled messages

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./src/skills/bundled/auto-reply/SKILL.md

Quality

Content

72%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with comprehensive executable examples, but it is a monolithic API reference that should be split into reference files, and it lacks an explicit create-test-enable workflow with validation checkpoints. Splitting the API reference and adding a quick-start workflow would markedly improve it.

Suggestions

Move the full TypeScript API reference and the Pattern/Condition/Variable tables into a separate REFERENCE.md and keep only a concise quick-start in SKILL.md.

Add an explicit workflow with a validation checkpoint, e.g. 1) addRule 2) test/simulate 3) only enable when the match is confirmed, especially before destructive ops (remove, clear-cooldowns, reload).

Trim redundant inline comments (e.g. "// Keyword match" above a keyword block) to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	Mostly lean code blocks and tables with little explanation of concepts Claude already knows; only minor padding in inline comments like "// Prevent spam" and "// Keyword match".	4 / 5
Actionability	Fully executable, copy-paste-ready TypeScript examples and chat commands covering the common cases (keyword, regex, conditional, cooldown, dynamic responses, list, test, enable/disable, delete).	5 / 5
Workflow Clarity	No sequenced multi-step workflow with validation checkpoints; testing/simulation is offered as commands and loosely mentioned in Best Practices ("Test patterns — Verify before enabling") but never enforced as a checkpoint before destructive operations like remove or reload.	3 / 5
Progressive Disclosure	Good section headers provide structure, but the file is a monolithic ~280-line API reference with everything inlined and no bundle files or one-level-deep references to split out the full API and type tables.	3 / 5
	Total	15 / 20 Passed

Description

61%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise and names a distinct niche with a couple of concrete concepts, but it omits any explicit "Use when..." trigger guidance and lists nouns rather than concrete actions. Adding a when-clause and action verbs would raise specificity and completeness.

Suggestions

Add an explicit trigger clause, e.g. "Use when setting up automatic replies, auto-responses, or scheduled messages."

Replace noun lists with concrete actions, e.g. "Create, enable, and schedule automatic response rules based on keywords, regex, and conditions."

Include natural synonyms users say ("auto-reply", "autoresponder") to broaden trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ("Automatic response") plus a few concrete items ("rules, patterns, and scheduled messages"), but these are nouns rather than enumerated actions and coverage is not comprehensive.	3 / 5
Completeness	Provides a clear "what" but no "when"/"Use when" clause, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Good natural keywords a user would say — "automatic response", "rules", "scheduled messages" — though a few synonyms like "auto-reply" or "autoresponder" are absent.	4 / 5
Distinctiveness Conflict Risk	The auto-reply niche is fairly distinct with specific triggers, with only minor overlap risk against general messaging or scheduling skills.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: alsk1992/CloddsBot
Path: src/skills/bundled/auto-reply/SKILL.md
Commit: 715fd4a

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.