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.

1.68x

Quality

58%

Does it follow best practices?

Impact

98%

1.68x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.trae/skills/reddit-automation/SKILL.md

Quality

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 is strong in specificity and distinctiveness, clearly identifying Reddit as the domain and listing concrete actions. Its main weaknesses are the lack of an explicit 'Use when...' clause and missing some natural trigger term variations that users might employ when requesting Reddit-related tasks.

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 comments and content.'

Include additional natural trigger terms users might say, such as 'upvote', 'Reddit API', 'r/', 'submission', or 'Reddit thread'.

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 via a specific tool (Rube MCP/Composio), making it highly distinctive. Unlikely to conflict with other skills since Reddit automation is a well-defined niche.	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 provides good structural organization and clear tool sequences for Reddit automation. Its main weaknesses are redundancy across sections (fullname format, pitfalls repeated), lack of concrete executable examples showing actual MCP calls with inputs/outputs, and missing validation checkpoints for destructive operations like deletion. Trimming redundancy and adding concrete call examples would significantly improve it.

Suggestions

Add at least one concrete MCP call example showing actual input parameters and expected response structure (e.g., a complete RUBE_SEARCH_TOOLS call followed by a REDDIT_SEARCH_ACROSS_SUBREDDITS call with real parameter values).

Consolidate the repeated pitfalls (fullname format, rate limits, NSFW filtering) into the single 'Known Pitfalls' section and remove duplicates from individual workflow sections to reduce token usage.

Add explicit validation/confirmation steps before destructive operations (delete post/comment), e.g., 'Retrieve the post first to confirm it's the correct one before deleting'.

Move the detailed 'Common Patterns' and 'Known Pitfalls' sections to a separate reference file and link to it from the main skill to improve progressive disclosure.

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 explanations like text formatting basics (Markdown syntax) are things Claude already knows. The quick reference table at the end duplicates information from the workflows above.	2 / 3
Actionability	The skill provides specific tool names, parameter lists, and tool sequences, which is helpful. However, there are no executable code examples or concrete input/output demonstrations—everything is described rather than shown with actual MCP call examples. The guidance is specific but not copy-paste ready.	2 / 3
Workflow Clarity	Multi-step workflows are clearly sequenced with numbered steps and labeled as Required/Optional. However, for destructive operations (delete post, delete comment), there are no validation or confirmation checkpoints. The setup flow has a good verification step, but the core workflows lack feedback loops for error recovery (e.g., what to do on rate limit errors or failed posts).	2 / 3
Progressive Disclosure	The content is well-structured with clear sections and a quick reference table, but it's quite long (~180 lines of substantive content) with everything inline. The common patterns and known pitfalls sections could be split into separate reference files, with the main SKILL.md providing a leaner overview. The single external link to Composio docs is good but insufficient for the volume of detail present.	2 / 3
	Total	8 / 12 Passed

Validation

90%

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 — 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: Lingjie-chen/MT5
Commit: 3069d33

Reviewed: 26 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.