Content
44%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides a comprehensive catalog of Reddit operations via Rube MCP with clear workflow sequences and useful pitfall documentation. However, it suffers from significant verbosity and redundancy—the same information (fullname formats, rate limits, NSFW filtering) appears in multiple places. The lack of executable examples (actual MCP call syntax) and the monolithic structure weaken its effectiveness.
Suggestions
Consolidate redundant information: fullname format, rate limits, and NSFW filtering are each mentioned 2-3 times across sections. Keep one authoritative location for each.
Add at least one concrete MCP call example showing actual invocation syntax (e.g., a complete search-then-comment workflow with real tool call format).
Split detailed pitfalls and the quick reference table into a separate reference file, keeping SKILL.md focused on core workflows and setup.
Add explicit confirmation/validation steps before destructive operations (delete post/comment), e.g., 'Retrieve the post first to confirm it matches before deleting.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is noticeably verbose with significant redundancy. Pitfalls are repeated across sections (e.g., fullname format explained in multiple workflows AND in Common Patterns AND in Known Pitfalls). The 'When to use' labels, explanations of Reddit markdown formatting, and the final 'When to Use' section add little value for Claude. The quick reference table largely duplicates information already covered in each workflow section. | 2 / 5 |
Actionability | The skill provides tool names, parameter lists, and tool sequences, which is useful concrete guidance. However, there are no executable code examples or actual MCP call syntax shown—just tool slug names and parameter descriptions. The flair resolution and pagination patterns use pseudocode-style numbered steps rather than actual invocation examples. It's between vague and fully executable. | 3 / 5 |
Workflow Clarity | Workflows are clearly sequenced with numbered steps, labeled as Required/Optional, and include pitfalls for each. The setup section has a clear 4-step verification process. However, for destructive operations (delete post, delete comment), there are no explicit validation/confirmation checkpoints—just listing the tool as optional. The rate limit section mentions backoff but doesn't provide a concrete retry workflow. | 4 / 5 |
Progressive Disclosure | All content is inlined in a single monolithic file with no bundle files or references to external documents. The Known Pitfalls, Common Patterns, and Quick Reference sections could be separate files. The document is quite long and would benefit from splitting detailed parameter documentation and pitfalls into referenced files, keeping SKILL.md as a concise overview. | 2 / 5 |
Total | 11 / 20 Passed |