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.
72
58%
Does it follow best practices?
Impact
98%
1.68xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/reddit-automation/SKILL.mdQuality
Discovery
67%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 does a good job listing specific Reddit-related actions and naming the integration tool, making it distinctive and specific. However, it lacks an explicit 'Use when...' clause, which limits its completeness score, and could benefit from broader natural trigger terms that users would actually say when requesting Reddit-related help.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Reddit, wants to post on Reddit, search subreddits, or interact with Reddit content.'
Include additional natural trigger terms users might say, such as 'Reddit API', 'r/', 'upvote', 'submission', or 'Reddit automation'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'search subreddits, create posts, manage comments, and browse top content.' Also includes a procedural note about searching tools first for current schemas. | 3 / 3 |
Completeness | Clearly answers 'what does this do' (automate Reddit tasks with specific actions listed), but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied by the nature of the actions described. | 2 / 3 |
Trigger Term Quality | Includes natural terms like 'Reddit', 'subreddits', 'posts', 'comments', and 'top content', which users would say. However, it misses common variations like 'upvote', 'downvote', 'Reddit API', 'submission', or 'r/' prefix references. The mention of 'Rube MCP (Composio)' is technical jargon that users wouldn't naturally use. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Reddit tasks via a specific tool (Rube MCP/Composio), making it highly distinctive. Unlikely to conflict with other skills given the Reddit-specific domain and named integration. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a competent but verbose skill that covers Reddit automation workflows comprehensively. Its main strengths are clear workflow sequencing with Required/Optional labels and a useful quick reference table. Its weaknesses are redundant information across sections, lack of concrete executable examples with actual parameter values, missing validation/feedback loops for destructive operations, and too much detail inline that could benefit from progressive disclosure into separate files.
Suggestions
Add concrete, copy-paste-ready examples of actual MCP tool calls with realistic parameter values and expected response structures for at least the most common workflows (search, create post, add comment).
Add explicit validation/confirmation steps after destructive operations (delete post/comment) and after post creation—e.g., 'Verify the post was created by retrieving it with REDDIT_RETRIEVE_REDDIT_POST'.
Remove redundant content: the fullname format explanation appears in multiple workflow pitfalls AND in Common Patterns AND in Known Pitfalls—consolidate to one location and reference it.
Remove information Claude already knows (Reddit Markdown formatting, what code blocks are) to reduce token usage.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-organized but includes some redundancy—pitfalls are repeated across sections (e.g., fullname format mentioned in multiple workflows and again in Known Pitfalls), and some information like Reddit Markdown formatting is something Claude already knows well. The quick reference table at the end duplicates information from the workflows above. | 2 / 3 |
Actionability | The skill provides tool names, parameter lists, and tool sequences, which is helpful. However, there are no concrete executable examples showing actual MCP tool calls with real parameter values—everything is described abstractly (e.g., 'Call REDDIT_LIST_SUBREDDIT_POST_FLAIRS with subreddit name') rather than showing a concrete invocation with example inputs and outputs. | 2 / 3 |
Workflow Clarity | Workflows are clearly sequenced with numbered steps and labeled as Required/Optional, which is good. However, there are no explicit validation checkpoints or error recovery loops—for destructive operations like delete, there's no confirmation step or verification that the deletion succeeded. The setup section has a good validation flow, but the core workflows lack feedback loops. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and headers, but it's quite long (~180 lines of substantive content) with no bundle files to offload detail into. The Common Patterns, Known Pitfalls, and Quick Reference sections could be separate reference files, keeping the main SKILL.md leaner. The single external link to Composio docs is appropriate but insufficient for the volume of inline detail. | 2 / 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
- davepoon/buildwithclaude
- Commit
d065ead
- 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.