Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →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.
.claude/skills/topic-resolver/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-03 | ✗→✓ | ▲ Improved | — | — |
| case-22 | ✗→✓ | ▲ Improved | — | — |
| case-02 | ✗→✓ | ▲ Improved | — | — |
| case-09 | ✗→✓ | ▲ Improved | — | — |
| case-20 | ✗→✓ | ▲ Improved | — | — |
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.
Raw topic queries produce noisy results:
User: "latest in Next.js"
Raw search: "next.js latest" -> news articles, old tutorials, unrelated mentionsResolve 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 entriesFor 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, Discord, forum | | Key maintainers | Individual accounts (up to 3) | | Related packages | npm, pip, cargo names | | Benchmarks | Known comparison sites |
~/.claude/topic-cache.jsonljson{ "topic": "Next.js 15", "entities": { "repo": "vercel/next.js", "docs": "https://nextjs.org/docs", "blog": "https://nextjs.org/blog", "x_handles": ["@timneutkens", "@rauchg"], "subreddit": "r/nextjs", "npm": "next" }, "confidence": 0.95, "resolved_at": "2026-04-12T04:00:00Z" }
1. User: "whats happening with Astro framework"
2. topic-resolver:
- repo: withastro/astro
- docs: https://astro.build/blog
- x: @astrodotbuild
- subreddit: r/astrojs
3. oracle parallel search:
- Latest commits on withastro/astro
- Recent @astrodotbuild posts
- r/astrojs top this week
- Astro blog last 10 posts
4. Cluster results, return coherent update| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-04 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-03 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-22 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-02 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-09 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-06 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-14 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-07 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-20 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-17 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-19 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-13 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-10 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-01 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-05 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-08 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-11 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-12 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-15 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-16 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-18 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-21 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted. The headline lift of +59 percentage points is the difference between those two pass rates over the 22 comparable cases.
The per-case answers from this run were removed by the retention sweep, so the case table below shows the verdicts without the text either arm produced. The counts above were recorded at the time and are unaffected. Answers are now kept for 180 days.
Other measured skills in the registry, with their headline benchmark lift.