← ClaudeAtlas

find-angleslisted

Turn a vague research topic or question into a tree of distinct research directions — each with concrete sub-angles, keywords, and ready-to-run academic search queries — so a researcher who has a topic but doesn't know where to focus gets a map of the field's real, separate lines of work. Use this skill WHENEVER the user has a topic and wants to scope or narrow it: "I want to research X but don't know the angle", "help me find research directions / angles / sub-topics for my thesis on ...", "narrow down this topic", "what are the different ways to approach ...", "give me a research question on ...", "break this topic into directions", or pastes a broad area and asks where to focus. Trigger even when the tool isn't named. Every direction stays anchored to the user's own vocabulary (no drifting into unrelated fields) and ships a search query you can paste straight into a database or the paper-search skill. Pure reasoning — no scripts, no web access.
academicatstool-netizen/Cat_find_angles · ★ 0 · AI & Automation · score 72
Install: claude install-skill academicatstool-netizen/Cat_find_angles
# Find Angles Turn one research query into a tree of **distinct research directions**, each with concrete **sub-angles** and a **ready-to-run academic search query**. This is for the researcher who has a topic but is stuck on *where to focus*. Pure reasoning — no scripts, no web needed. The whole value is **anchoring + breadth without drift**: the directions must span the genuinely separate clusters of work on the topic, while every one of them stays tethered to the user's actual words. A direction that wanders into an unrelated discipline ("AR games" → "gamification in healthcare") is the failure mode this skill exists to prevent. ## Input you need Just the **topic or question** — one line is enough ("AR games and player engagement", "spaced repetition for medical students", "transformer interpretability"). Optionally the user may add a **constraint** (a year range, a discipline, a population, a method, a language). That's it — no papers required, nothing to upload. If the query is **empty or a single ambiguous word** where you genuinely can't tell the field (e.g. just "AR" — augmented reality? Arkansas? accounts receivable?), ask ONE short disambiguation question. Otherwise, **produce the directions immediately** — do not gate behind a setup menu. ## How to run it **You are a single Claude running a three-stage pipeline as three sequential reasoning passes in this one turn.** There are no sub-agents and no separate model calls. The Stage 1–2 working-out is **internal