reddit-automation
Automate Reddit tasks via Rube MCP (Composio): search subreddits, create posts, manage comments, and browse top content. Always search tools first for current schemas.
Install with Tessl CLI
npx tessl i github:davepoon/buildwithclaude --skill reddit-automation70
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
50%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 effectively communicates specific Reddit automation capabilities and is clearly distinguishable from other skills. However, it critically lacks explicit 'Use when...' guidance, which is essential for Claude to know when to select this skill from a large pool. The trigger terms are adequate but could include more natural user language variations.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about Reddit, wants to post to subreddits, browse r/ communities, or automate Reddit interactions'
Include additional natural trigger terms users might say: 'r/', 'subreddit', 'reddit post', 'upvote', 'reddit comments', 'reddit search'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'search subreddits, create posts, manage comments, and browse top content'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly describes WHAT it does but completely lacks a 'Use when...' clause or any explicit trigger guidance for WHEN Claude should select this skill. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2, and this has none at all. | 1 / 3 |
Trigger Term Quality | Includes 'Reddit', 'subreddits', 'posts', 'comments' which are natural terms, but missing common variations like 'reddit post', 'upvote', 'karma', 'r/', or specific subreddit references users might mention. | 2 / 3 |
Distinctiveness Conflict Risk | Very clear niche - Reddit-specific automation via a named MCP (Rube/Composio). Unlikely to conflict with other skills due to the specific platform focus and tool reference. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with clear workflows and good structure. The main weakness is verbosity - pitfalls and format explanations are repeated across sections, and the document could benefit from moving detailed reference material to separate files while keeping SKILL.md as a leaner overview.
Suggestions
Consolidate repeated information (fullname format, rate limits) into single sections rather than repeating in each workflow's pitfalls
Consider moving the detailed 'Known Pitfalls' and 'Common Patterns' sections to a separate REFERENCE.md file, keeping only critical warnings inline
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy - pitfalls are repeated across sections (e.g., fullname format mentioned multiple times), and explanations like 'When to use' headers add tokens without much value since the workflow names are self-explanatory. | 2 / 3 |
Actionability | Provides concrete tool names, specific parameter lists, and clear tool sequences for each workflow. The quick reference table and fullname format examples are immediately usable without additional lookup. | 3 / 3 |
Workflow Clarity | Each workflow has a clear numbered sequence with required vs optional steps marked. The setup section includes explicit validation steps (verify connection, confirm ACTIVE status before proceeding). Flair resolution pattern shows a complete feedback loop. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the document is quite long (~200 lines) with detailed pitfalls that could be split into a separate reference file. The quick reference table at the end is good, but the inline detail level is high for a SKILL.md overview. | 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 | |
- 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.