reddit-research-skills: Claude Code skills that query Reddit through reddapi.dev
Reddit research skills for Claude Code and AI agents
At a glance
- What is it?
- A set of agent skills that wrap a third-party Reddit search API, with a canonical research skill, a legacy alias, an API reference, and a paid lead-discovery skill. Useful if you already work inside Claude Code or a similar agent, and you accept that the data path runs through reddapi.dev rather than Reddit itself.
- Who is it for?
- Adopt it if your research workflow already lives inside Claude Code or a comparable agent and you want the API surface described in prose rather than in a client library. Do not adopt it if you need Reddit's official API, if you cannot accept a third-party intermediary for the queries you are running, or if your budget cannot absorb a paid reddapi.dev plan for the lead skill.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 1 day ago.
- What is it written in?
- Mainly Python, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on September 15, 2026, and from our analysis. They are not legal advice.
DEEP OPEN-SOURCE ANALYSIS
The gap these skills fill, and the gap they do not
Reddit is a common place to look for unfiltered user complaints, competitor mentions, and niche validation signals. The friction is not finding Reddit, it is getting an agent to query it in a structured way. The official route involves Reddit OAuth and app registration, which is a setup step before any research begins. This repository takes a different route: it packages instructions that tell an agent how to call reddapi.dev, a third-party service, and the README states plainly that no Reddit OAuth or app registration is needed. That is the specific problem being solved. It is not a Reddit client library, and it is not a data dump. It is a set of skill definitions that an agent reads and then executes against an external HTTP API.
The audience follows from that. These skills are for people working inside Claude Code, Gemini CLI, or another agent that supports the skill format, and who want to ask research questions in natural language rather than write HTTP calls. The README's usage examples are all conversational: find discussions about iPhone problems, search for frustrations with productivity tools, find competitor pain points for a named tool. If your workflow is a Python script or a scheduled job, this repository is the wrong shape. The Python listed as the primary language is the implementation behind the skills, not a library you import.
Four skills, three of which are the same engine
The repository ships four skills, and the naming is the first thing to get right. reddit-research is the canonical skill and the one new installs should use. It covers market research, user research, and product validation, and it carries query playbooks for competitor research, niche validation, and trend tracking. reddapi is the legacy name for the same engine, kept live so existing installs do not break. The README says it is fully functional standalone, and that new installs should prefer reddit-research for the expanded playbooks. So the difference between the two is documentation and playbook coverage, not capability.
reddit-search-api is a third skill and a different kind of artifact. It is described as a pure API reference for the same engine: endpoints, parameters, response schemas, error codes, with no research-workflow framing. That is the one to read if you want to understand what the API actually returns before you let an agent loose on it.
reddit-leads is the outlier. It does B2B lead discovery, finds posts with buying intent, scores them 0 to 100, and classifies each by lead type: pain_point, solution_request, complaint, feature_request, comparison. The README states it requires a paid reddapi.dev plan. That single sentence changes the cost profile of the whole repository, because three skills are usable on whatever free tier exists and one of them is not.
What the engine actually exposes
The README lists four capabilities. Vector Search does full-archive embedding similarity and returns a similarity_score, supports working date filters, and returns exact result counts up to limit: 100. Semantic Search is natural-language search at comparable speed, adds LLM keyword extraction, and offers an optional AI summary, but the README notes it has no date filter. Trends API reports topic momentum over a required date range. Subreddit Discovery lists and looks up subreddits.
The scale claim in the description is 50K+ subreddits, 20M+ posts, and 40M+ comments. Treat that as a vendor figure from the README rather than something independently verified here.
The constraint worth internalising is the date filter split. Vector Search has working date filters and Semantic Search does not. If your research question is time-bounded, for example what people said about a product in the three months after a launch, the endpoint choice is forced. Semantic Search gives you keyword extraction and an optional summary, which is convenient for open-ended exploration, but it will not respect a date window. Trends API is the opposite: the date range is required, not optional. Three endpoints, three different rules about time, and the README does not explain why. That is a design wrinkle you plan around rather than a bug you report.
Installing it and asking the first question
The README gives one install command:
npx skills add https://github.com/lignertys/reddit-research-skills --skill reddit-research
The --skill flag selects the canonical skill by name. Given that reddapi is a live alias for the same engine, the flag value is the part to check carefully on a fresh install, since the two names resolve to the same underlying capability with different playbook coverage.
After installing, usage is conversational. The README's examples are of the form: find discussions about iPhone problems and complaints on Reddit; what are people saying about AI agent limitations; analyze trends in remote work discussions. The skill then calls reddapi.dev and returns discussions with engagement metrics.
There is one required piece of setup the README handles by pointing elsewhere rather than documenting: the API key. The Get API Key section is a single link to reddapi.dev. There is no environment variable name, no config file path, and no example of where the key is stored in the material provided. If you are evaluating this for a team, that is a real gap. You will be reading the reddapi.dev developer documentation before you can answer basic questions about secret handling. The homepage field points at reddapi.dev/developers, which is presumably where that lives, but the repository itself does not say.
Rate limits, HTTP 429, and what happens when the key runs out
The README is direct about the limits, which is a point in its favour. It states that access is gated by plan-based rate limits and points at skills/reddit-leads/SKILL.md for the plan and quota table. An invalid or exhausted key returns HTTP 429.
That is the failure mode to design around. A 429 is not a transient network error you retry your way out of; it is the service telling you that the key is invalid or the plan quota is spent. The README does not describe retry semantics, backoff behaviour, or how the skills surface a 429 to the agent mid-conversation. If your agent is halfway through a multi-query research task and hits the ceiling, the material does not say what the user sees. For a one-off exploratory question that is fine. For a research pipeline that fans out across many subreddits, it is the thing that will interrupt you, and you should read the plan table in skills/reddit-leads/SKILL.md before sizing the work.
The second failure mode is subtler and comes from the architecture itself. Because this is a third-party service rather than Reddit's own API, the results depend on reddapi.dev's index and its embedding model. The README's own framing calls it a third-party service, not Reddit official. That is not a criticism, but it does mean the corpus is a snapshot maintained by someone else, and questions about coverage, recency, or deletion handling are answered by reddapi.dev's documentation, not by this repository.
When a direct API client beats a skill definition
The obvious alternative is to call the reddapi.dev HTTP API yourself from a Python script, using the reddit-search-api skill as the reference, or to use Reddit's official API with OAuth and app registration. The difference in approach is not the data source in the first case; it is where the logic lives. A skill definition is prose that an agent interprets at runtime, which is what makes natural-language queries work and also what makes behaviour less predictable across agent versions. A direct client is code you control: you decide the retry policy on 429, you decide whether to fall back from Semantic Search to Vector Search when a date filter is required, and you can run it in CI without an agent in the loop.
The official Reddit API is the other real alternative and it differs at the root. It removes the third-party intermediary and the plan-based quota, at the cost of OAuth setup and app registration that this repository exists to avoid. If your queries are high-volume, or if the data is going into something with compliance requirements, that trade is worth re-examining rather than defaulting to convenience.
A reasonable split: use the skill for interactive exploration where you are refining a question in conversation, and write a direct client once the question has stabilised and you need it to run repeatedly. The reddit-search-api skill exists precisely so you can do the second half without reverse-engineering the first.
Maintenance surface and the MIT licence
The repository is MIT licensed, which permits commercial use, modification, and redistribution provided the copyright notice and permission notice are included. That covers the skill definitions and any Python in the repository. It does not cover reddapi.dev itself, which is a separate service with its own terms and its own paid tier for the lead skill. A permissive licence on the client-side instructions tells you nothing about what you may do with the data you retrieve. That question belongs to reddapi.dev's terms, and the README does not address it.
On maintenance, the material supports only a narrow statement. There is one release, 1.0.0, dated 2026-02-06, and the last push to main is 2026-08-06, six months later. So there has been activity after the tagged release, but no second release tag. The README does not publish a versioning policy, a deprecation timeline for the legacy reddapi skill name, or a compatibility matrix against agent versions. The legacy name existing at all is a maintenance cost: two skill names, one engine, and a note that new installs should prefer the canonical one. That is cheap to carry and easy to get wrong in documentation.
What to verify before depending on this: read skills/reddit-leads/SKILL.md for the plan and quota table, confirm from reddapi.dev/developers where the API key is configured and how it is stored, and check whether the date-filter gap on Semantic Search affects your intended queries. Those three checks are answerable from the repository and the linked developer documentation, and they determine whether the rest of the setup is worth doing.
Editorial conclusion
Adopt it if your research workflow already lives inside Claude Code or a comparable agent and you want the API surface described in prose rather than in a client library. Do not adopt it if you need Reddit's official API, if you cannot accept a third-party intermediary for the queries you are running, or if your budget cannot absorb a paid reddapi.dev plan for the lead skill. Before committing, verify three things: which reddapi.dev plan your key maps to and what quota that plan carries, whether the date filter your research depends on exists on the endpoint you intend to use, and whether the install command resolves the canonical reddit-research skill rather than the legacy reddapi name. The plan table in skills/reddit-leads/SKILL.md is the document to read first, because it is the one that decides whether the workflow you have in mind is affordable at your query volume.
Community notes