Reddit API with PRAW (Python) and Snoowrap (Node.js)
44
32%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/reddit-api/SKILL.mdQuality
Discovery
22%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a title rather than a functional skill description. It names the technology stack (Reddit API, PRAW, Snoowrap) but fails to describe any concrete capabilities or provide trigger guidance for when Claude should select this skill. It needs substantial expansion to be useful for skill selection.
Suggestions
Add concrete actions the skill enables, e.g., 'Fetch posts and comments from subreddits, submit posts, manage Reddit bots, scrape user data, and monitor subreddit activity.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about Reddit automation, building Reddit bots, scraping Reddit data, posting to subreddits, or working with the Reddit API, PRAW, or Snoowrap.'
Include common user-facing terms like 'Reddit bot', 'scrape Reddit', 'subreddit', 'Reddit posts', 'upvotes', and 'Reddit comments' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the domain (Reddit API) and the libraries (PRAW, Snoowrap) but lists no concrete actions like 'fetch posts', 'submit comments', 'scrape subreddits', etc. It reads more like a title than a capability description. | 1 / 3 |
Completeness | The description answers neither 'what does this do' (no actions described) nor 'when should Claude use it' (no 'Use when...' clause or equivalent trigger guidance). It is essentially just a label. | 1 / 3 |
Trigger Term Quality | It includes some relevant keywords like 'Reddit', 'PRAW', 'Snoowrap', 'Python', and 'Node.js' that users might mention. However, it misses natural user phrases like 'scrape Reddit', 'post to Reddit', 'Reddit bot', or 'subreddit data'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of Reddit API and specific libraries (PRAW, Snoowrap) provides some distinctiveness, but without concrete actions it could overlap with general Python/Node.js API skills or web scraping skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides highly actionable, executable code examples across multiple languages and use cases, which is its primary strength. However, it is severely over-long and monolithic—it tries to be a comprehensive Reddit API reference rather than a focused skill document. The content contradicts its own header instruction to split across files, and lacks validation/error-handling workflows despite dealing with authentication and API rate limits.
Suggestions
Split content into separate files as the header suggests: base.md (setup, rate limits, anti-patterns), python.md (PRAW + direct API), typescript.md (Snoowrap + fetch), and oauth.md (web flow). Keep SKILL.md as a concise overview with references.
Move the scopes table, Pydantic models, project structure, and endpoint reference into separate reference files linked from the main skill.
Add explicit validation steps after authentication (e.g., verify token works before proceeding) and error handling examples for common failures (429, 403) rather than just listing them as anti-patterns.
Remove explanatory text Claude already knows (e.g., what app types mean, that environment variables store credentials) and trim redundant examples that show the same pattern in slightly different ways.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~400+ lines, covering Python PRAW, Snoowrap, direct API for both Python and TypeScript, OAuth2 web flow, Pydantic models, project structure, and scopes tables. Much of this is reference material Claude already knows or could derive. The header even says 'Load with: base.md + [language].md' suggesting it should be split, yet everything is inline. | 1 / 3 |
Actionability | The code examples are concrete, executable, and copy-paste ready across multiple languages and approaches. Setup steps include specific URLs, environment variable formats, and complete working code for authentication, fetching posts, streaming, and OAuth2 flows. | 3 / 3 |
Workflow Clarity | The setup flow (create app → set env vars → authenticate → use API) is reasonably clear, but there are no explicit validation checkpoints or error recovery steps. The anti-patterns section mentions error handling but doesn't show how to implement it. No verification step after authentication setup. | 2 / 3 |
Progressive Disclosure | Despite the header suggesting content should be split across base.md and language-specific files, everything is crammed into one monolithic document. The scopes table, Pydantic models, project structure, OAuth2 web flow, and direct API implementations should all be in separate referenced files. This is a textbook case of content that should be split but isn't. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (593 lines); consider splitting into references/ and linking | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
d4ddb03
Table of Contents
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.