
research-start
Research roadmap for a legal issue — statutes to check, case law areas to investigate, regulatory frameworks, Westlaw search terms. Leads and frameworks, NOT authoritative citations; students verify and develop everything. Use when a student asks where to start researching, wants a research roadmap for an issue, or needs gaps identified in existing research.
- Installs
- 687
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/anthropics/claude-for-legal --skill research-start- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads research-start automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
/research-start
- Load
~/.claude/plugins/config/claude-for-legal/legal-clinic/CLAUDE.md→ jurisdiction, practice area. - Use the workflow below.
- Frame the issue specifically. Build roadmap: statutory starting points (unverified), case law areas (not cases), secondary sources, search terms.
- If student has existing research uploaded: synthesize and identify gaps.
- Output with prominent "leads not authorities" header. Everything is a starting point the student verifies.
/legal-clinic:research-start "habitability defense to nonpayment eviction in [State]"
Research Start: Roadmap, Not Research
Purpose
Legal research is essential to clinical education. But the initial phase — figuring out what to research, finding the right statute, understanding the framework — is often the most time-consuming and least educational part. Students spend hours finding the starting point before they can do the actual research.
This skill produces the starting point: statutes to check, case law areas to investigate, search terms for Westlaw and CourtListener. None of it is verified. None of it is authoritative. All of it is a lead for the student to run down.
This is a pedagogical safeguard, not just an ethical one. Students still learn to research. They just start from a better place.
Load context
~/.claude/plugins/config/claude-for-legal/legal-clinic/CLAUDE.md → jurisdiction (state), practice areas.
Workflow
Step 0: Seed documents first
Before building the roadmap, read the clinic's own seed documents. The supervising attorney uploaded them at cold-start (handbook, filing guides, local court rules, intake forms, example case files, prior memos) — they are pre-vetted, jurisdiction-specific, and will beat any Westlaw query on the first 20 minutes of a student's research.
- Read
~/.claude/plugins/config/claude-for-legal/legal-clinic/CLAUDE.md→## Seed documents. Identify any item whose purpose or filename matches the research area (e.g., "Alameda UD filing guide" for a UD habitability question; a redacted sample case file in the same practice area; a prior memo on the same issue). - For each match, surface it as a Seed documents to read first block at the top of the roadmap output. Name the file, say why it matters for this specific question, and say what it likely covers vs. where outside research will still be needed.
- If no seed documents match the issue, say so plainly ("No clinic seed documents match this issue — proceeding straight to primary sources"). Don't fabricate a match.
- If the clinic has the
LIMITED DATAflag set in## Seed documents, add a one-line note: "Clinic has fewer than 10 seed docs; your professor's precedent bank is thin — lean harder on primary sources and flag what's missing for your supervisor."
The roadmap still covers statutes, case law areas, secondary sources, and search terms — seed docs are the first lead, not a replacement for the rest. But surface them above everything else so the student starts where their supervisor's precedent starts.
Step 1: Frame the issue
What's the research question? Be specific. Not "eviction defenses" — "habitability defense to nonpayment eviction in [State], specifically whether a broken heater qualifies and whether the tenant had to give written notice."
If the question is too broad, narrow it with the student: "That's three research questions. Let's take them one at a time. Which first?"
Step 2: Build the roadmap
Statutory starting points: List statutes likely relevant. State explicitly these are likely, not confirmed.
Likely relevant statutes (UNVERIFIED — confirm currency and applicability):
- [State] Landlord-Tenant Act, likely at [State Code Title X] — look for "warranty of habitability" or "repair and deduct"
- Local housing code for [City/County] — may define specific conditions (heat, water) as required
[VERIFY each citation is current and correct — codes get renumbered]
Case law areas to investigate: Not cases — areas. The student finds the cases.
Case law areas:
- [State] Supreme Court or appellate decisions on implied warranty of habitability — look for the leading case establishing the doctrine
- Cases on what conditions qualify — heat specifically, if any
- Cases on procedural prerequisites — did tenant have to give notice? withhold rent? escrow?
- Cases on the remedy — offset against rent owed, or a separate damages claim?
Regulatory / administrative sources: If applicable (immigration especially).
Administrative sources:
- [Agency] regulations at [CFR cite area]
- Agency guidance or policy manuals — often more current than regs
- For immigration: USCIS Policy Manual, BIA precedent decisions
Secondary sources to orient: Where to get the framework before diving into primary.
Secondary sources (for framework, not to cite):
- [State] practice guide on landlord-tenant (check clinic library)
- Relevant CLE materials
- Law review notes on the specific issue if it's contested
Search terms: For Westlaw, or whatever the clinic uses.
Search terms to try:
- Westlaw:
"warranty of habitability" /s heat! & [State]- CourtListener:
implied warranty of habitability AND (heat OR heater) AND [State]- Refine based on what comes back — these are starting queries
Step 3: Flag what's uncertain
If the skill is unsure whether a source is relevant or current:
[UNCERTAIN: whether [State] has a specific statute on this vs. common-law doctrine only — the search will tell you]
Uncertainty is stated, not hidden.
No silent supplement. This skill produces leads, not authoritative citations — by design, students run the citations down themselves. But if a query to a configured research tool (Westlaw, CourtListener) returns few or no results for a specific rule or case, say so and stop. Do NOT manufacture citations from web search or model knowledge to fill a thin result set without asking. Say: "The search returned [N] results from [tool]. Coverage appears thin for [rule]. Options: (1) broaden the search query, (2) try a different research tool, (3) search the web — results will be tagged
[web search — verify]and should be checked against a primary source before relying, or (4) stop here and flag the gap for your supervisor. Which would you like?" The supervising attorney decides whether to accept lower-confidence sources.Source attribution. Tag every suggested citation with where it came from:
[Westlaw],[CourtListener], or the MCP tool name for citations retrieved from a legal research connector;[web search — verify]for web-search citations;[model knowledge — verify]for citations recalled from training data;[user provided]for citations supplied by the supervising attorney or case file. Citations taggedverifycarry higher fabrication risk and should be checked first. Never strip or collapse the tags — they tell the student which leads are raw research and which are model guesses to verify against a primary source.
Step 4: Synthesize uploaded research (if any)
If the student has already done some research and uploads it: read it, identify what's covered and what's missing.
From your research so far:
- You have: [summary of what's covered]
- Gap: [what the roadmap above suggests that you haven't found yet]
[VERIFY: the case you cited — [name] — run through a citator (verify it is good law) it, it may have been distinguished or limited]
Output
═══════════════════════════════════════════════════════════════════════
RESEARCH ROADMAP — LEADS, NOT AUTHORITIES
Nothing below is a verified citation. Every statute, every case area,
every search term is a starting point for YOUR research. You verify
currency, applicability, and accuracy. You find the actual cases.
If something below turns out to be wrong or outdated, that's expected —
this is a map of where to look, not a substitute for looking.
═══════════════════════════════════════════════════════════════════════
# Research Roadmap: [Issue]
**Jurisdiction:** [State] | **Practice area:** [area]
## Seed documents to read first
[Per Step 0. List any clinic seed docs that match the issue with a one-line
"what this likely covers" note. If none matched: "No clinic seed documents
match this issue — proceeding to primary sources."]
## Statutory starting points (UNVERIFIED)
[list with VERIFY flags]
## Case law areas to investigate
[areas, not cases]
## Administrative / regulatory sources
[if applicable]
## Secondary sources (for framework, not citation)
[list]
## Search terms
**Westlaw:** [queries]
## Uncertainty flags
[Everywhere the roadmap is genuinely unsure]
---
## What to do with this
1. Start with a secondary source to get the framework
2. Find and read the primary statutes — confirm the citations above are current
3. Run the searches, find the leading cases
4. run through a citator (verify it is good law) everything before relying on it
5. Come back and run `/memo` to scaffold your analysis once you have the rule
## What this roadmap does NOT do
- **It does not give you citations you can use.** Every cite above is a lead
to verify, not an authority to rely on.
- **It does not do the research.** You do the research. This gets you to the
starting line faster.
- **It does not replace Westlaw.** Those have the actual cases. This
tells you where to point them.
---
**Cite verification — required before use.** Citations above were generated by an AI model and have not been verified. Before relying on any case, statute, or rule — or including it in client work — run it through Westlaw, CourtListener, or your clinic's research platform for accuracy and current good-law status. Flag unverified citations to your supervisor.
What this skill does NOT do
- Provide authoritative citations. Explicitly, by design. The student verifies every cite before using it.
- Replace legal research. Accelerates the "where do I start" phase; the research itself is still the student's.
- Guarantee the roadmap is complete. It's a starting set of leads. The research may reveal sources the roadmap missed — that's fine, that's research.
Close with the next-steps decision tree
End with the next-steps decision tree per CLAUDE.md ## Outputs. Customize the options to what this skill just produced — the five default branches (draft the X, escalate, get more facts, watch and wait, something else) are a starting point, not a lock-in. The tree is the output; the lawyer picks.
FAQ
What does the research-start skill do?
Research roadmap for a legal issue — statutes to check, case law areas to investigate, regulatory frameworks, Westlaw search terms. Leads and frameworks, NOT authoritative citations; students verify and develop everything. Use when a student asks where to start researching, wants a research roadmap for an issue, or needs gaps identified in existing research.
How do I install research-start?
Run npx skills add https://github.com/anthropics/claude-for-legal --skill research-start in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/research-start/ (personal) or .claude/skills/research-start/ (project).
Which AI agents can use research-start?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is research-start safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains research-start?
It is published by anthropics in anthropics/claude-for-legal, and it is an official skill from the maker of the technology it covers. It has 687 recorded installs.
More from anthropics/claude-for-legal
legal-writing
anthropics/claude-for-legal
Structural feedback on a legal writing draft (memo, brief, paper, exam essay) — organization, analysis depth, clarity, citation form. NEVER rewrites the draft. Use when the user says "feedback on my memo", "read my draft", or "critique my brief".
draft
anthropics/claude-for-legal
First draft of a common clinic document — practice-area templates (asylum applications, eviction answers, protective order petitions, demand letters), jurisdiction-aware formatting, explicitly a starting point requiring student analysis and attorney review. Use when a student needs a first draft of a motion, letter, petition, declaration, or other clinic document.
flashcards
anthropics/claude-for-legal
Generate or drill flashcards for black-letter memorization — Leitner-style buckets, per-subject markdown storage, drill mode with self-assessment. Use when the user says "drill flashcards", "make flashcards from", "quiz me on cards", or wants to memorize rules.
saas-msa-review
anthropics/claude-for-legal
Reference: review of SaaS subscription agreements with attention to the terms that matter most in subscription deals — auto-renewal mechanics, price escalation, data portability, uptime SLAs, and subprocessor rights. Loaded by /commercial-legal:review when a SaaS or subscription agreement is detected.
review
anthropics/claude-for-legal
Review a vendor agreement, NDA, or SaaS subscription against your playbook. Identifies the agreement structure from titles, routes to the right review skill (vendor-agreement-review, nda-review, saas-msa-review), and integrates the output into a single memo. Use when the user says "review this contract", "check this MSA", "is this NDA okay", "look at this SaaS agreement", or attaches an inbound agreement for review.
policy-monitor
anthropics/claude-for-legal
Keep the privacy policy current with practice. Two modes: weekly sweep of saved PIAs, DPA reviews, and triage results to find policy drift; or direct query for a proposed new practice. Use when the user asks "does our policy cover this", "we want to start doing X — does the policy need updating", "run the policy monitor", "policy sweep", or wants to find where the privacy policy no longer matches what the team actually does.
Popular productivity & automation skills
agent-browser
vercel-labs/agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
lark-doc
open.feishu.cn
飞书云文档(Docx / Wiki)内容操作:读取、创建、编辑文档,插入或下载图片附件,以及操作思维笔记。用户提供文档 URL/token(包括 doubao.com 的 /docx/、/wiki/)时使用;按 URL 路径/token 而非域名路由;/page/ 是妙搭应用,非飞书云文档。文档内嵌资源按读取参考中的统一规则分流。独立评论操作走 lark-drive;随正文读取评论使用 docs +fetch。表格或 Base 内部数据操作不在本 skill。
lark-base
open.feishu.cn
飞书多维表格(Base)操作:建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、应用模式(BaseApp/AppMode 页面与组件)、Workspace 目录、workflow、角色权限、模板中心(多维表格模板分类/列表/搜索);遇到 Base/多维表格/bitable、BaseApp/AppMode、/base/ 或 /app/ 链接时使用。BaseApp 不走 lark-apps;文件导入/导出转 lark-drive,认证/授权转 lark-shared。
lark-drive
open.feishu.cn
飞书云空间(云盘/云存储):管理 Drive 文件和文件夹,包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、查询权限设置、评论/权限/订阅、标题、版本、飞书文档密级标签(secure labels)和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题,或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sheet/bitable/slides 时使用;doubao.com 云空间 URL/token 也按资源路径和 token 路由,不回退 WebFetch。不负责:文档内容编辑(走 lark-doc)、表格/Base 表内数据操作(走 lark-sheets/lark-base)、知识空间节点/成员管理(走 lark-wiki)、原生 Markdown 文件读写/patch/diff(走 lark-markdown)。
lark-shared
open.feishu.cn
Use for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handling notice JSON.
lark-im
open.feishu.cn
飞书即时通讯:收发消息和管理群聊。发送和回复消息、搜索聊天记录、管理群聊成员、上传下载图片和文件、管理表情回复、发送应用内/短信/电话加急、发送和处理交互卡片(Interactive Card)、监听卡片按钮回调(card.action.trigger)。当用户需要发消息、查看或搜索聊天记录、下载聊天中的文件、查看群成员、搜索群、创建群聊或话题群、管理标记数据、管理 Feed 置顶(添加/移除/查询置顶会话)、管理标签数据、处理卡片回调时使用。