Content
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a comprehensive catalog of Reddit operations via Rube MCP with clear tool names, parameter lists, and useful pitfall warnings. However, it suffers from redundancy (fullname format and pitfalls repeated multiple times), lacks concrete executable examples showing actual MCP tool invocations, and is missing validation/confirmation steps for destructive operations like deletion. The content would benefit from being more concise and splitting detailed reference material into separate files.
Suggestions
Add concrete MCP call examples with sample arguments and expected response structures for at least the most common workflows (search, create post, add comment).
Add explicit validation/confirmation steps before destructive operations (delete post, delete comment) — e.g., 'Retrieve the post first to confirm it's the correct one before deleting.'
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.
Remove information Claude already knows (Reddit Markdown formatting, basic link syntax) to improve conciseness.
| 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 workflow sections. | 2 / 3 |
Actionability | The skill provides specific tool names and parameter lists, which is helpful, but lacks executable code examples or concrete MCP call examples with actual payloads. The tool sequences are described but never shown as concrete invocations with sample arguments and expected responses, making it more descriptive than copy-paste ready. | 2 / 3 |
Workflow Clarity | Multi-step 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—particularly important for destructive operations like delete, where the skill notes deletion is permanent but doesn't include a confirmation/verification step before proceeding. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and headers, but it's a monolithic document (~180 lines) with no bundle files to offload detailed content. The pitfalls, common patterns, and quick reference sections could be split into separate reference files, with the main SKILL.md serving as a leaner overview pointing to them. | 2 / 3 |
Total | 8 / 12 Passed |