topic-resolver
Pre-search topic resolution. Maps vague queries to concrete entities (GitHub orgs, X handles, subreddits, docs URLs) before searching. Run as first step of any research workflow to dramatically improve search precision.
Profile →npx skills add vibeeval/vibecosystem --skill topic-resolver --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Topic Resolver Before running any web search or research workflow, resolve the topic to concrete, searchable entities. One small LLM call upfront saves 10x the tokens in search noise. ## The Problem Raw topic queries produce noisy results: ``` User: "latest in Next.js" Raw search: "next.js latest" -> news articles, old tutorials, unrelated mentions ``` ## The Solution Resolve first, search second: ``` User: "latest in Next.js" Step 1: Topic -> Entities Framework: Next.js 15 Org: vercel/next.js (GitHub) Docs: https://nextjs.org/blog Community: r/nextjs (Reddit) Maintainer: @timneutkens (X) Release channel: github.com/vercel/next.js/releases Step 2: Parallel searches on resolved entities - GitHub: vercel/next.js latest commits + releases - X: @timneutkens latest posts - Reddit: r/nextjs top this week - Docs: nextjs.org/blog latest entries ``` ## Entity Categories For any topic, resolve to these categories (only if applicable): | Category | Example | |----------|---------| | **Official repo** | GitHub owner/repo | | **Org account** | X/Twitter handle | | **Docs URL** | Authoritative documentation | | **Release channel** | RSS, changelog, release page | | **Community** | Subreddit, D
- The Problem
- The Solution
- Entity Categories
- Resolution Rules
- Output Format
- Integration
- When NOT to Use
- Example Workflow
What does the topic-resolver skill do?
Pre-search topic resolution. Maps vague queries to concrete entities (GitHub orgs, X handles, subreddits, docs URLs) before searching. Run as first step of any research workflow to dramatically improve search precision.
How do I install it?
Run `npx skills add vibeeval/vibecosystem --skill topic-resolver --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From vibeeval/vibecosystem, a repository with 521 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.