reddit-api

Reddit API with PRAW (Python) and Snoowrap (Node.js)

Quality

56%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/reddit-api/SKILL.md

Quality

Content

65%Weight 40%Scale 1-5

Reviews 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 comprehensive executable code, but pays for it in conciseness and monolithic structure, and its write/batch operations lack validation checkpoints that the rubric requires. It scores well on doing the work, less well on token efficiency and progressive disclosure.

Suggestions

Consolidate the four near-duplicate operation demonstrations: keep PRAW as the primary path and move the Snoowrap and direct-API variants into separate reference files linked from the main body.

Add validation checkpoints for write operations, e.g. after submit/vote verify the response status and after starting a stream note how to verify it is receiving events before processing.

Move the OAuth2 web flow, scopes table, and Pydantic models into dedicated reference files (e.g. references/oauth.md, references/scopes.md) to shorten the core SKILL.md and enable progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The ~580-line body is code-forward and avoids explaining concepts Claude already knows, but the same fetch/post/vote/comment operations are demonstrated four times (PRAW, Snoowrap, direct Python httpx, direct TS fetch) and the Quick Reference repeats install commands, leaving clear tightening opportunities.	3 / 5
Actionability	It provides copy-paste-ready, executable code for authentication, fetching, posting, voting, streaming, and user data in both Python and TypeScript, plus concrete env vars, a scopes table, and an endpoints table covering the common cases.	5 / 5
Workflow Clarity	Setup is sequenced (create app, env vars, install, auth) and OAuth has state validation, but the write/batch operations (posting, voting, streaming) lack any verify-or-rollback checkpoint, triggering the cap that destructive/batch workflows without validation cannot exceed 3.	3 / 5
Progressive Disclosure	The body has clear section headers and external doc links, but all 580 lines are monolithically inlined — the OAuth2 web flow, scopes table, Pydantic models, and direct-API reference are content that belongs in separate reference files, and no skill-internal references exist.	3 / 5
	Total	14 / 20 Passed

Description

48%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is niche-specific and names concrete tooling but is thin on actions and trigger phrases, with no "Use when" clause inside the description field itself. Most dimensions land at the midpoint, reflecting a recognizable but under-specified activation signal.

Suggestions

Add concrete actions to the description, e.g. "Fetch Reddit posts, comments, and subreddit data, submit posts, and vote via PRAW (Python) or Snoowrap (Node.js)."

Fold the trigger guidance into the description with a "Use when..." clause (e.g. "Use when building Reddit integrations, bots, or fetching Reddit data") rather than relying on a separate when-to-use field.

Include natural user phrasings like "Reddit bot", "Reddit posts", or "Reddit comments" alongside the library names to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description "Reddit API with PRAW (Python) and Snoowrap (Node.js)" names the domain and two concrete libraries/languages but lists no concrete actions (fetch, post, vote, stream), so it falls below the 3-anchor that requires 1-2 concrete actions.	2 / 5
Completeness	It gives a clear "what" (Reddit API integration via PRAW/Snoowrap) but the description field itself contains no "Use when..." trigger; the when-guidance lives in a separate `when-to-use` field, so per the guideline a missing explicit trigger caps completeness at 3.	3 / 5
Trigger Term Quality	"Reddit" is a natural term users would say, but the only other keywords are the technical library names "PRAW" and "Snoowrap", missing common variations users actually voice like "Reddit bot", "Reddit posts", or "fetch Reddit comments".	3 / 5
Distinctiveness Conflict Risk	"Reddit API" is a clear, mostly-distinct niche unlikely to overlap with unrelated skills, matching the 4-anchor (mostly distinct, minor overlap risk with closely related skills) rather than the 5-anchor which expects explicit distinct trigger phrases.	4 / 5
	Total	12 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (592 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: alinaqi/claude-bootstrap
Path: skills/reddit-api/SKILL.md
Commit: abc600e

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

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.