The Claude Research Agent
Set it up once and Claude scans your market every morning, then hands you a one-page brief ranked by what matters to your goal. The master prompt, the setup, and the daily formats are all here. Free, no code.
In short: This page contains 26 copy-paste ready prompts, organized into 5 categories with a description and pro tip for each. The first 15 prompts are free instantly โ no signup needed. Hand-curated and tested by the AI Academy team.
Set Up Your Agent
5 promptsSet Up Your Agent in 5 Minutes
1/26I want to turn you into a reusable Daily Research Agent using a Claude Project. Walk me through the fastest setup. <task> Give me the exact steps to: 1) create a new Claude Project named "Daily Research Agent", 2) paste the master agent prompt into the Project's custom instructions, 3) fill in my market profile so I never re-type it, and 4) start each day by opening the Project and saying "run today's brief". Keep it to numbered steps a non-technical person can follow. </task> <format> Return a short numbered checklist, then one line on how I will trigger it each morning. </format>
Step-by-step setup that saves your agent as a reusable Claude Project so it remembers your market.
Pro tip: A Claude Project keeps your <my_world> profile permanently, so every morning is just one line: run today's brief.
Make It Run Every Morning (Easy + Advanced)
2/26I want my Research Agent to run every morning as hands-off as possible. Lay out my options honestly. <context> I have set up the agent as a Claude Project. Now I want a daily brief without re-doing work. </context> <task> Explain three ways to make it recur, from easiest to most automated: 1) a one-click daily trigger I run in 30 seconds, 2) using any scheduled-task or reminder feature available to me so the prompt fires on a schedule, and 3) a fully automated path using the API plus a scheduler or a no-code tool to fetch sources and email me the brief. For each, list the trade-off in effort versus hands-off. </task> <format> Return three options as a short comparison with effort, how-hands-off, and who each is for. </format>
Lays out the easy daily-trigger path through to fully automated, hands-off delivery.
Pro tip: Start with the one-click daily trigger. Only build the automated API path once the brief is clearly worth it.
Tell the Agent About Your Market (Profile)
3/26Help me write the market profile my Research Agent will use on every run, so its briefs are sharp from day one. <task> Interview me with up to eight quick questions to capture: what I do, my category, my ideal customer, my competitors, the topics and keywords to track, my current goal, and the noise to ignore. Then assemble my answers into a clean <my_world> block I can paste into the agent's Project instructions. </task> <format> Ask the questions first. After I answer, return a finished <my_world> block ready to paste. </format>
Interviews you and assembles the reusable market-profile block your agent runs on.
Pro tip: Spend five minutes here; a precise profile is the difference between a generic brief and a useful one.
Choose Your Sources
4/26Help me decide what sources my Research Agent should pull from each morning. <my_world> - My category: [ONE LINE] - My competitors: [LIST] - Topics: [LIST] </my_world> <task> Recommend the highest-signal sources for my market: which newsletters, sites, search queries, social accounts, competitor pages, and communities to check. Rank them by signal-to-noise and tell me which three I should paste in every day versus check weekly. </task> <format> Return a ranked source list grouped into Daily and Weekly, with a one-line reason for each. </format>
Builds a ranked, high-signal source list tailored to your market.
Pro tip: Bookmark the Daily sources in one folder so collecting the morning material takes under a minute.
Test Your Agent Before You Trust It
5/26Before I rely on my Research Agent daily, I want to pressure-test it. <task> Run a sample brief using my market profile and a batch of material I will paste. Then critique your own output: was anything generic, unsupported, or off-goal? Tell me what extra context would make tomorrow's brief sharper. </task> <format> Return the sample brief, then a short "How to make this better" note listing what to add to my profile or sources. </format>
Runs a dry-run brief and has the agent critique itself so you can tune it before relying on it.
Pro tip: Do this twice with real material; the self-critique usually reveals one missing field that fixes most weak briefs.
XML tags are just the start. Learn the full Claude workflow.
A growing library of 300+ hands-on AI tutorials covering Claude, ChatGPT, and 50+ tools. New tutorials added every week.
The Agent Prompt (Master + Variants)
5 promptsThe Research Agent (Master Prompt)
6/26You are my Daily Research Agent. Your job is to scan my market every day and hand me a tight, decision-ready brief I can read in two minutes. <role> Act like a sharp chief-of-staff crossed with a market analyst. You are skeptical, concrete, and you never pad. You surface what changed and what I should do about it. </role> <my_world> - Company / what I do: [ONE LINE] - My market / category: [E.G. B2B EMAIL TOOLS] - My ideal customer: [WHO] - Competitors to watch: [LIST 3 TO 7] - Topics and keywords to track: [LIST] - What I am trying to win at right now: [GOAL THIS QUARTER] - Ignore: [NOISE TO SKIP] </my_world> <inputs_each_run> I will paste fresh material each morning: headlines, newsletter clips, competitor posts, search results, or notes. If I paste nothing, work from what you already know about my market and ask me for one link if needed. </inputs_each_run> <task> From the material, produce my brief. For each item: state what happened in one line, why it matters to MY goal, and the specific move I could make. Rank by impact on my goal. Cut anything that does not change a decision. </task> <format> Return a Markdown artifact titled "Your Market, This Morning": 1. Three to five items, each tagged OPPORTUNITY, SIGNAL, or WATCH, with: what happened, why it matters to me, suggested move. 2. A one-line "If you do one thing today" recommendation. 3. A short "Sources" list. Keep the whole thing under one page. Be specific, not generic. </format>
The core system prompt that turns Claude into your daily research agent, ranked by impact on your goal.
Pro tip: Fill in the <my_world> block once and save the whole prompt as a Claude Project so every run inherits it.
Lite Version (30-Second Brief)
7/26You are my Research Agent in lite mode. I have 30 seconds. <my_world> - What I do: [ONE LINE] - My goal right now: [GOAL] - Competitors: [LIST] </my_world> <task> Scan the material I paste (or your knowledge of my market) and give me ONLY the single most important thing that changed and the one move it suggests. Nothing else. </task> <format> Return three short lines: WHAT, WHY IT MATTERS TO ME, DO THIS. Under 60 words total. </format>
A stripped-down agent run for days when you only want the single most important signal.
Pro tip: Use this on busy mornings; switch back to the master prompt when you have two minutes.
Deep-Dive Version (Weekly)
8/26You are my Research Agent in deep-dive mode. Once a week, go wider and deeper than the daily brief. <my_world> - Company / category: [DETAILS] - Goal this quarter: [GOAL] - Competitors: [LIST] - Topics: [LIST] </my_world> <task> Synthesize the week: the three biggest shifts in my market, what each competitor did, one emerging trend I should not miss, and two concrete bets I could make in the next 30 days. Connect the dots the daily brief was too short to make. </task> <format> Return a Markdown artifact with sections: This Week in My Market, Competitor Moves, Emerging Trend to Watch, Two Bets for the Next 30 Days, and Open Questions. Cite sources. </format>
A weekly synthesis run that connects the daily signals into trends and concrete bets.
Pro tip: Run this every Friday and paste in the week's daily briefs so it builds on what the agent already found.
Competitor-Focused Version
9/26You are my Research Agent, focused only on competitors today. <my_world> - My company: [ONE LINE] - Competitors to watch: [LIST] - What I want to beat them on: [DIMENSION, E.G. PRICING, SPEED, SUPPORT] </my_world> <task> From the material I paste (launches, pricing changes, posts, reviews), tell me per competitor: what they just did, what it signals about their strategy, and how I should respond to protect or grow my position. </task> <format> Return a Markdown table: Competitor, What They Did, What It Signals, My Counter-Move. Then one line: the competitor I should watch most closely this week and why. </format>
Turns the agent into a focused competitive-intelligence brief with counter-moves.
Pro tip: Paste competitor changelogs, pricing pages, or recent LinkedIn posts for the sharpest read.
Customer & Demand Version
10/26You are my Research Agent, focused on what my customers are saying and wanting. <my_world> - Who I serve: [ICP] - My product / category: [ONE LINE] - Goal: [E.G. FIND NEW DEMAND] </my_world> <task> From the material I paste (reviews, forum threads, search trends, support tickets, social posts), surface the top three things my market is asking for or frustrated about, and what each one means for my roadmap or messaging. </task> <format> Return a Markdown artifact: Top Demand Signals (3, each with a verbatim-style quote, why it matters, and a suggested response), then one underserved need worth building for. </format>
Refocuses the agent on customer demand signals and unmet needs for roadmap and messaging.
Pro tip: Feed it raw review text or Reddit threads; ask it to quote the strongest lines back so you keep the voice of the customer.
Customize Your Market
5 promptsDefine Your Ideal Customer (ICP)
11/26Help me write a precise ICP for my Research Agent so it judges every signal against who I actually serve. <inputs> - What I sell: [ONE LINE] - Best current customers: [2 TO 3 EXAMPLES] - Who I want more of: [DESCRIBE] </inputs> <task> Turn this into a tight ICP: segment, company size, role of buyer, their trigger to buy, and the outcome they want. Keep it to a short paragraph the agent can use as a filter. </task> <format> Return a clean ICP paragraph, then three "signals this ICP is moving" the agent should watch for. </format>
Produces a sharp ICP definition the agent uses to filter signals by relevance.
Pro tip: Add the ICP to your <my_world> block so every brief is scored against the customer you actually want.
Build Your Competitor Watchlist
12/26Help me build the competitor watchlist my Research Agent monitors. <inputs> - My category: [ONE LINE] - Competitors I know: [LIST] </inputs> <task> Suggest direct, indirect, and emerging competitors I may be missing, and for each note what to watch (pricing, launches, hiring, messaging). Keep the active watchlist to the seven that matter most. </task> <format> Return three groups (Direct, Indirect, Emerging) with what to watch per competitor, then the final seven-name daily watchlist. </format>
Expands and prioritizes your competitor watchlist, including emerging threats you may have missed.
Pro tip: Re-run this quarterly; emerging competitors graduate to direct ones faster than you expect.
Pick the Topics & Keywords to Track
13/26Help me choose the topics and keywords my Research Agent should track daily. <my_world> - Category: [ONE LINE] - Goal this quarter: [GOAL] - ICP: [SHORT] </my_world> <task> Propose the highest-value topics, keywords, and search queries to monitor for my goal, and flag any that are too broad (noisy) versus precise (high-signal). Tell me which to drop. </task> <format> Return a tight list of topics and exact search queries, marked high-signal or noisy, with the noisy ones removed from the final set. </format>
Selects high-signal topics and search queries to track and prunes the noisy ones.
Pro tip: Precise queries beat broad ones; a few exact phrases will out-signal a long generic keyword list.
Set What to Ignore (Noise Filter)
14/26Help me write a noise filter so my Research Agent stops surfacing things that do not change my decisions. <context> My briefs sometimes include items that are interesting but not actionable for me. </context> <task> Based on my market and goal, list the categories of news to deprioritize or ignore (e.g. funding rounds that do not affect my segment, generic AI hype, far-future predictions). Turn it into an "Ignore" instruction I can paste into the agent. </task> <format> Return a short Ignore list and a one-line instruction the agent should follow to stay decision-relevant. </format>
Builds an explicit ignore-list so the agent only surfaces decision-relevant signals.
Pro tip: A good ignore list is what makes the brief short; tell the agent that brevity is a feature, not a bug.
Tune the Agent's Voice & Length
15/26Help me set the tone and length rules for my Research Agent's briefs. <task> Recommend voice and format defaults for a brief I will read every morning: how blunt, how much hedging, ideal length, whether to lead with the recommendation, and how to present sources. Then write the style instruction to paste into the agent. </task> <format> Return your recommended defaults with a one-line reason each, then the finished style instruction block. </format>
Dials in the agent's tone, bluntness, and length so briefs match how you like to read.
Pro tip: Ask for the recommendation first, evidence second; leading with the move makes a brief feel like a decision, not a digest.
Your Daily Brief
6 promptsThe 1-Page Morning Brief
16/26Run my Daily Research Agent and give me the standard one-page morning brief. <my_world> [PASTE YOUR MARKET PROFILE BLOCK] </my_world> <inputs> Material from this morning: [PASTE HEADLINES, CLIPS, POSTS, OR LEAVE BLANK] </inputs> <task> Produce my brief: three to five ranked items, each tagged OPPORTUNITY, SIGNAL, or WATCH with what happened, why it matters to my goal, and the move it suggests. End with one "if you do one thing today" line and a sources list. </task> <format> Markdown artifact, under one page, titled "Your Market, This Morning". </format>
The everyday run: a ranked, tagged one-page brief with a single top recommendation.
Pro tip: Keep the output as an artifact so you can skim it on your phone in the time it takes coffee to brew.
What Changed Since Yesterday
17/26Run my Research Agent in delta mode: only tell me what is new since yesterday. <context> Yesterday's brief: [PASTE OR SUMMARIZE] Today's material: [PASTE] </context> <task> Compare and report only genuine changes: new moves, reversals, or escalations. Explicitly say if nothing material changed so I can move on. </task> <format> A short list of only-what-is-new items with their suggested moves, or a single line confirming a quiet day. </format>
A delta brief that reports only what is new versus yesterday, including quiet days.
Pro tip: Paste yesterday's brief so the agent does not repeat itself; quiet days are a feature worth knowing.
Opportunity Scan
18/26Run my Research Agent focused only on opportunities I could act on this week. <my_world> [PASTE PROFILE] </my_world> <task> From the material (or your knowledge of my market), surface concrete openings: a competitor stumble, an unmet demand, a timely hook, or a partnership opening. For each, give the specific action and why now. </task> <format> A ranked list of opportunities, each with the action and the window of time it is open. </format>
Filters the day's signals into actionable, time-boxed opportunities.
Pro tip: Ask the agent to flag the single opportunity with the shortest window so you act before it closes.
Competitor Move Alert
19/26Run my Research Agent as a competitor alert. <my_world> Competitors: [LIST] What I want to beat them on: [DIMENSION] </my_world> <inputs> Material: [PASTE COMPETITOR POSTS, PRICING, LAUNCHES] </inputs> <task> Tell me which competitors moved, what it signals, and my counter-move. If a move is a real threat to my goal, mark it URGENT. </task> <format> A short table: Competitor, Move, Signal, My Counter-Move, with any URGENT items at the top. </format>
A focused competitor-alert brief that flags real threats and your counter-moves.
Pro tip: Run this the morning after a competitor's known launch date for the sharpest read.
Team-Ready Exec Summary
20/26Take today's brief and reformat it for my team. <context> Today's brief: [PASTE THE AGENT OUTPUT] Audience: [E.G. MY LEADERSHIP TEAM / SLACK CHANNEL] </context> <task> Turn it into a crisp update my team can read in 60 seconds: the headline, the two things that matter, and what we are doing about each. Drop anything not relevant to them. </task> <format> A short, forward-ready summary with a clear subject line and three bullets. </format>
Reformats your private brief into a 60-second update ready to share with the team.
Pro tip: Ask for a subject line too so you can paste the whole thing straight into Slack or email.
Monthly Trend Report
21/26Run my Research Agent in monthly mode and synthesize the month. <context> The month's briefs: [PASTE OR SUMMARIZE] My goal: [GOAL] </context> <task> Identify the three trends that defined the month in my market, how my competitive position shifted, what I learned, and the two priorities that should shape next month. </task> <format> A Markdown artifact: Trends That Defined the Month, How My Position Shifted, Lessons, Next Month's Two Priorities. </format>
A monthly synthesis that turns daily briefs into trends, position shifts, and next-month priorities.
Pro tip: Feed it the month's daily briefs; the agent is far sharper synthesizing its own past output than starting cold.
Make It Run & Scale
5 promptsTurn Findings Into Action (Chain to a Doer Agent)
22/26Take a finding from today's brief and turn it into finished work. <context> The finding: [PASTE ONE OPPORTUNITY OR SIGNAL FROM THE BRIEF] What I want to produce: [E.G. AN OUTREACH EMAIL / A POST / A ONE-PAGER] </context> <task> Act on the finding: produce the actual deliverable, ready to use, in my voice. If you need one detail from me, ask before drafting. </task> <format> Return the finished deliverable as an artifact, then one line on the best moment to send or publish it. </format>
Chains a research finding straight into a finished deliverable so insight becomes action.
Pro tip: The agent finds the opening; this prompt makes Claude do the work, so the loop ends in shipped output.
Spin Up a Second Agent (New Beat)
23/26Help me clone my Research Agent for a second beat. <context> My first agent covers: [TOPIC] I also want daily coverage of: [NEW BEAT, E.G. HIRING TRENDS / A NEW MARKET / A KEY ACCOUNT] </context> <task> Adapt my master agent prompt for the new beat: rewrite the <my_world> focus, the sources to watch, and the brief format so it fits the new topic. Give me a ready-to-paste Project setup. </task> <format> Return the adapted agent prompt and a one-line name for the new Project. </format>
Adapts your agent into a second specialized agent covering a new beat.
Pro tip: Keep each agent narrow; two focused agents beat one that tries to cover everything.
Build a Weekly Digest From Your Agents
24/26Combine my agents' briefs into one weekly digest. <context> This week's briefs from my agent(s): [PASTE] </context> <task> Merge them into a single weekly digest: the few things that actually mattered across all beats, deduplicated and ranked, with the decisions they point to. </task> <format> A one-page weekly digest: Top 3 Things This Week, Decisions to Make, Watching Next Week. </format>
Rolls multiple daily briefs into a single ranked weekly digest.
Pro tip: Run it Friday afternoon so you start the next week already knowing your top three moves.
Improve the Agent Over Time
25/26Help me make my Research Agent sharper based on how it has been doing. <context> Recent briefs: [PASTE A FEW] What was useful: [NOTE] What was noise or wrong: [NOTE] </context> <task> Diagnose why the weak items slipped through and propose specific edits to my profile, sources, or ignore list to fix it. Then give me the updated instruction blocks. </task> <format> A short diagnosis, then the revised <my_world> and Ignore blocks ready to paste. </format>
A tuning loop that diagnoses weak briefs and rewrites your agent's instructions to fix them.
Pro tip: Do this every couple of weeks; a few rounds of tuning is what turns a decent agent into one you trust.
Share Your Brief Automatically
26/26Help me get my daily brief delivered where I will actually see it. <context> I read things in: [E.G. EMAIL / SLACK / NOTION / MY NOTES APP] My setup: [CLAUDE PROJECT, OR API IF I HAVE IT] </context> <task> Recommend the simplest way to route my agent's brief into my preferred channel each day, from copy-paste habit through to a no-code automation. Note the effort for each. </task> <format> A short ranked list of delivery options with effort and how-hands-off for each. </format>
Maps the simplest ways to get your brief delivered into email, Slack, or your notes daily.
Pro tip: Match delivery to where you already look every morning; a brief you have to go find is a brief you will skip.
Frequently Asked Questions
Prompts are the starting line. Tutorials are the finish.
A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.
7-day free trial. Cancel anytime.