Content
61%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is well structured and unusually strong on non-obvious API specifics (fullname formats, rate limits, flair flows), but it repeats pitfalls across sections, includes filler, and lacks validation checkpoints for its destructive delete workflows. Tightening duplication and adding delete confirmation steps would lift it substantially.
Suggestions
Add a validation step before destructive operations, e.g. "Before deleting, call REDDIT_RETRIEVE_REDDIT_POST/REDDIT_RETRIEVE_SPECIFIC_COMMENT with the thing_id and confirm it is the intended item — deletion is permanent."
Deduplicate pitfalls: consolidate the per-workflow Pitfalls entries that reappear verbatim in Known Pitfalls and Common Patterns, and remove the vacuous "When to Use" closing sentence.
Fill in parameter details for under-specified tools (REDDIT_GET, REDDIT_RETRIEVE_SPECIFIC_COMMENT) and clarify what "Links use `text` format" means, or drop it.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is dense with non-obvious API specifics (fullname prefixes, rate limits, flair requirements) and avoids explaining known concepts, but pitfalls are duplicated across sections (rate limits appear in Create Posts and Known Pitfalls; fullname format in Manage Comments and Common Patterns; pagination twice), and the closing "This skill is applicable to execute the workflow or actions described in the overview" is vacuous filler. It could be meaningfully tightened. | 3 / 5 |
Actionability | Concrete tool slugs, named parameters with example values ('t3_abc123'), and step-by-step procedures for flair resolution and pagination give mostly executable guidance. Not 5: some tools lack parameter detail ("REDDIT_GET - Get posts from a subreddit endpoint", REDDIT_RETRIEVE_SPECIFIC_COMMENT), and "Links use `text` format" is unclear. | 4 / 5 |
Workflow Clarity | The Setup section has real checkpoints (confirm connection ACTIVE before running workflows) and each workflow is numbered, but destructive operations (delete post/comment, with "Deletion is permanent" noted) have no validation-before-delete steps. The destructive-operations guideline caps workflow clarity at 3. | 3 / 5 |
Progressive Disclosure | No bundle files exist, and the single file is well organized: consistent per-workflow template, clear section headers, and a genuinely useful Quick Reference table. Not 5 because at ~215 lines the duplicated Known Pitfalls/Common Patterns material could be consolidated or split out; not 3 because structure and navigation are good. | 4 / 5 |
Total | 14 / 20 Passed |