Content
65%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 highly actionable with complete, executable examples across PRAW, Snoowrap, and the raw API, and it is largely free of concept-explanation filler. Its weaknesses are structural: everything is inlined in one ~580-line file with no progressive disclosure, and write operations lack validation and error-recovery checkpoints.
Suggestions
Split bulky reference material (Available Scopes table, OAuth2 web flow, Pydantic models, direct-API clients) into files under references/ and link to them from SKILL.md so the main file is a lean overview.
Add validation and error-recovery steps for write operations — e.g., check 429/403/404 responses after submit/vote calls and retry or surface errors — instead of only listing error handling as an anti-pattern.
Remove the duplicated 'Quick Reference' installation commands and the generic Pydantic-model boilerplate that Claude can already produce, to tighten token usage.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly code and tables with little prose padding, but includes content Claude could derive itself — generic Pydantic model classes, a full FastAPI OAuth callback app, and a 'Quick Reference' that repeats installation commands already shown above. This fits anchor 3 ('Mostly efficient but includes some unnecessary explanation or could be tightened'), above 2 because there is no concept-explaining filler. | 3 / 5 |
Actionability | The skill provides copy-paste-ready executable code throughout: PRAW auth with a verification print, hot/new/search listing, submit/vote/reply, streaming, Snoowrap equivalents, and direct httpx/fetch OAuth clients. Specific examples cover the common cases, matching anchor 5 ('Fully executable; copy-paste ready...'). | 5 / 5 |
Workflow Clarity | Setup is a clear numbered sequence (create app → env vars → client init) with a verify-auth checkpoint, but the outward-facing write operations (submit, vote, comment) include no validation or error-recovery steps, and error handling appears only as an anti-pattern bullet rather than in the code. Anchor 3 fits, and the destructive-operation cap applies since posting/voting mutate external state without verification. | 3 / 5 |
Progressive Disclosure | There are no bundle files and the body references none; ~580 lines are inlined monolithically, including content that clearly belongs in separate files (scope tables, the OAuth2 web flow, Pydantic models, direct-API clients). Section structure is good with clear headers — above anchor 2's 'minimal structure' — but nothing is split out or navigable via references, matching anchor 3. | 3 / 5 |
Total | 14 / 20 Passed |