Library / Research brief
Research brief
Synthesize sources into a brief with claims, confidence, and open questions — no invented citations.
Install in Claude Code
Create a folder whose name matches the skill name field (research-brief/). Save the text below as SKILL.md inside it. Personal skills go in ~/.claude/skills/research-brief/. Project skills go in .claude/skills/research-brief/. Claude Code discovers them from the filesystem.
Upload on claude.ai
Zip the skill folder (the zip should contain the folder, which contains SKILL.md) and upload it in Claude’s Skills settings. Anthropic’s current platform docs list custom uploads on Pro, Max, Ultra, Team, and Enterprise plans when code execution is enabled. Check the Claude Help Center for the latest plan details. Read the files before you turn a skill on.
Use with the Claude API
Custom API Skills are uploaded through the Skills API and referenced with the code execution tool. Skills do not sync automatically from Claude Code or claude.ai — install this folder again on the surface where you need it. See Anthropic’s Agent Skills overview.
--- name: research-brief description: Synthesizes supplied sources or search results into a structured research brief with claims, confidence, disagreements, and open questions. Use when the user asks for a research brief, literature note, competitive readout, or source-grounded summary. --- # Research brief ## Goal Help the user make a decision or understand a topic using the sources they provided or that you were allowed to retrieve. Separate fact, inference, and opinion. ## Workflow 1. Restate the question in one sentence so the user can correct it. 2. Inventory sources: title, author or publisher, date, and URL if present. 3. Extract claims that answer the question. Pair each important claim with a source. 4. Note where sources agree, disagree, or are silent. 5. Mark confidence: - High: multiple independent, dated, primary or official sources agree. - Medium: one solid source, or several weaker ones. - Low: single secondary source, undated material, or extrapolation. 6. List what you could not verify. ## Output template ```markdown # Research brief: [question] ## Bottom line [4–8 sentences. Lead with the answer, then the main caveat.] ## Key findings 1. Finding — source — confidence 2. Finding — source — confidence ## Agreements and conflicts - ## Implications - What this suggests for the user's decision, labeled as inference. ## Open questions - ## Sources 1. Title — publisher — date — URL or file name ``` ## Rules - Never invent a citation, quotation, statistic, or URL. - If you cannot access a live source, say you are working only from what was provided. - Quotes must be short and exact. If you are unsure of wording, paraphrase and say so. - Dates matter. Prefer newer official documents over undated blog posts, and say when a source may be stale. - Do not treat marketing pages as independent confirmation of a vendor's own claims.
You may copy and adapt this free skill for personal or commercial use. If you republish it, please credit Skillory with a link. Audit any skill — including this one — before enabling it in an environment with access to private data.
Related skills
Changelog writer
Turn commits and merged PRs into a readable changelog grouped the way users scan it.
Open skill →Code review
Review a diff like a careful teammate: correctness first, then security, then clarity.
Open skill →Git commit messages
Write conventional commit messages from a staged diff, without fluff or invented ticket IDs.
Open skill →