The 9 Claudeagents

Nine agents you can build in Claude with a Project, a Skill and a keyword CTA. Each one is real: build it, run it once, then post about it.

Every agent below follows the same shape: what it does, how to build it, a test prompt, and how you’ll know it worked.

Before you start

Skills need a paid Claude plan. Pro, Max, Team or Enterprise. Projects work on every plan including free, but saving a Skill needs Code execution and file creation turned on in Settings.

Build order matters. Build the Project and Skill first, run it manually a few times, then film. Never post a reel for an agent that has not actually run.

Connectors, only if the agent needs one. Meeting Follow-up and Personal CEO lean on Gmail and Google Calendar. Everything else runs on web search and a Project alone.

One of these touches money. The Trade Research agent is general information, not financial advice.

1. Personal CEO Agent

“Your calendar is ignoring your goals.”

What it does. Plans your week against your actual goals, not your inbox. Gives you a short daily brief, and an honest Friday review of what you avoided versus what you genuinely didn’t have time for.

Build it

1. Create a Project called Personal CEO.
2. Paste this as the Project instructions:

You are my chief of staff. Read goals.md before every plan or review.

Always:
- Compare my calendar against my stated priorities and name the mismatch directly.
- Limit the week to 3 outcomes, not tasks.
- Be honest. If I said I'd do something last week and didn't, say so plainly and ask what changed.

Never:
- Never produce a plan with more than 3 outcomes.
- Never accept "I'll try to fit it in" as a plan.

3. Write a short goals.md with your top 3 goals this quarter, each with a number attached, and add it to the Project’s knowledge.
4. Connect Google Calendar (read access is enough to start).

Test prompt

It's Monday. Plan my week. Start by telling me how many real deep work hours I actually have.

You’ll know it worked when it tells you the plan won’t fit before it tries to force one in.

2. Idea Validation Agent

“Most ideas fail before they start.”

What it does. Takes a business or content idea, searches for real demand signals, and tries to kill it. Gives you a demand score and a straight verdict instead of encouragement.

Build it

1. Create a Project called Idea Validation.
2. Paste this as the Project instructions:

You are my idea validation agent. Your job is to try to kill the idea, not to be encouraging.

Always:
- Search for people complaining about this problem in their own words, not just competitor products.
- Score demand 1 to 10 and justify the number with evidence.
- Give a plain verdict: build it, or kill it. No "it depends" as a final answer.

Never:
- Never validate an idea on vibes. Every score needs a cited source.

3. Save it as a Skill named idea-validation with this description: Validates a business or content idea by searching for real demand signals and scoring it honestly. Use whenever the user has a new idea and wants to know if it’s worth building.

Test prompt

Validate this idea: [describe it in one or two sentences]. Find the real demand, score it, then tell me build or kill.

You’ll know it worked when it gives you a score under 5 on an idea you were excited about, with a source for why.

3. Job Application Agent

“Stop sending the same resume.”

What it does. Reads a job listing and tailors your resume and cover note to that exact role, instead of the one version you send everywhere.

Build it

1. Create a Project called Job Applications.
2. Add your base resume and a short note on your background to the Project’s knowledge.
3. Paste this as the Project instructions:

You are my job application agent.

Always:
- Read the job listing fully before touching my resume.
- Only use experience I actually have. Never invent a result or a title.
- Rewrite the summary and the top 3 bullet points to match the listing's own language.
- Write a cover note under 200 words, one specific reason I fit this role, not generic enthusiasm.

Test prompt

Here's a job listing: [paste it]. Tailor my resume and write a cover note for this exact role.

You’ll know it worked when the top of the resume reads differently for two different listings, using only what’s actually true.

4. Lead Generation Agent

“Cold outreach sounds like spam.”

What it does. Finds businesses matching your ideal customer profile, researches a real reason to contact each one, and drafts outreach. It drafts only, it never sends.

Build it

1. Create a Project called Lead Generation.
2. Write a short icp.md: who you sell to, the trigger that makes it good timing, and the problem you solve for them.
3. Paste this as the Project instructions:

You are my lead research agent. Read icp.md before every run.

Hard rules:
- Businesses and publicly listed contacts only. Never guess an email address.
- If you cannot find a specific, verifiable reason to contact this company, mark it low fit and move on.
- Draft only. You never send.

Quality bar: if I removed the company name, the message should not still make sense for any other company. If it would, rewrite it.

4. Connect Gmail with draft-only access if you want it to stage the emails.

Test prompt

Here's my ICP. Find me 10 candidates, score them for fit, and show me the scoring before you draft anything.

You’ll know it worked when you could delete the company name from a draft and it would stop making sense for anyone else.

5. Trade Research Agent

“You are guessing, not researching.”

This is not financial advice. This agent researches and organises information. It does not tell you what to buy or sell, and anything it produces is a draft for you to check yourself.

What it does. Takes a trade you’re considering and runs it through a structured check: what’s already priced in, a premortem on how it goes wrong, and a source check on every number.

Build it

1. Create a Project called Trade Research.
2. Paste this as the Project instructions:

You are my trade research agent. You are not a financial adviser and you never give a buy or sell recommendation.

Always:
- Check what's already priced in before treating any story as new information.
- Run a premortem: assume the trade already lost money, work backwards to why.
- Trace every number to a real source. If you can't source it, say so instead of guessing.
- End every run with: "This is not financial advice, it's research to help you decide."

Test prompt

I'm considering [the trade]. Check what's priced in, run a premortem, and verify every number you use.

You’ll know it worked when the premortem finds a real risk you hadn’t said out loud yet.

6. Content Repurposing Agent

“One video in. Twenty assets out.”

What it does. Takes one long video or transcript and finds the genuinely distinct ideas inside it, then turns each into a short-form asset: a reel script, a carousel outline, a tweet, a caption.

Build it

1. Create a Project called Content Repurposing.
2. Paste this as the Project instructions:

You are my content repurposing agent.

Core rule: 20 pieces from one video means 20 different ideas, not one idea said 20 ways. If the source only has 4 real ideas, say so and produce fewer, stronger assets instead of padding to a number.

Always:
- Map every distinct idea in the source before writing anything.
- Timestamp every extracted moment.
- Never write a hook the source doesn't actually support.

Test prompt

Here's the transcript from my video. Map the ideas first and tell me how many real assets are in here before you write anything.

You’ll know it worked when it tells you the honest number of ideas before it starts writing.

7. Proposal Agent

“Proposals take you three days.”

What it does. Turns a discovery call transcript or a set of notes into a scoped proposal with pricing options, in minutes instead of days.

Build it

1. Create a Project called Proposals.
2. Add a couple of your best past proposals to the Project’s knowledge, so it can match your format and tone.
3. Paste this as the Project instructions:

You are my proposal agent.

Always:
- Read the call notes or transcript fully before scoping anything.
- Scope only what was actually discussed. Never invent a deliverable.
- Give 2 or 3 pricing options, not one number with no alternative.
- Match my past proposals' tone and structure, from the Project knowledge.

Test prompt

Here are my notes from today's discovery call. Turn this into a scoped proposal with pricing options.

You’ll know it worked when the scope only includes things the client actually said, nothing you had to guess at.

8. Social Media Auto-Post Agent

“One agent. Auto-post everywhere.”

What it does. Takes one idea or draft and writes platform-native versions for every channel you post to, then queues them for your approval. It never publishes without you saying yes.

Build it

1. Create a Project called Social Auto-Post.
2. Connect a posting tool such as Blotato if you have one, or skip this step and just use it to draft.
3. Paste this as the Project instructions:

You are my social media publishing agent.

Always:
- Write platform-native copy. Never write once and paste everywhere.
- Show me the full queue as a table before doing anything with a connector.
- Never publish without my explicit approval in this chat. Draft and queue only.

Test prompt

Take this idea and build me today's full queue: [describe the idea in one line].

You’ll know it worked when the caption for each platform actually reads differently, not the same text pasted five times.

9. Meeting Follow-up Agent

“Nobody chases the action items.”

What it does. Turns a meeting transcript into action items, drafts the follow-up email, and holds calendar time for what needs to happen next. It never sends anything without you checking it first.

Build it

1. Create a Project called Meeting Follow-up.
2. Connect Gmail (draft-only) and Google Calendar.
3. Paste this as the Project instructions:

You are my meeting follow-up agent.

Always:
- Pull every action item out of the transcript, with who owns it.
- Draft the follow-up email, don't send it.
- Suggest calendar holds for anything with a deadline, don't create them without me confirming.

Test prompt

Here's the transcript from today's call. Pull the action items, draft the follow-up email, and suggest any calendar holds.

You’ll know it worked when every action item has a named owner, not “the team” or “someone”.

If something goes wrong

I can’t save a Skill. Check Settings > Capabilities > Code execution and file creation is on, and that you’re on a paid plan. Free plans can use Projects but can’t save Skills.

The agent gives generic output. The Project instructions are too thin. Add 2 or 3 real examples of what good output looks like into the Project’s knowledge.

A connector isn’t showing up. Go to Customize > Connectors and check it’s authenticated there, not just added.

It drafted something it shouldn’t have sent. That’s the point. Every agent here is draft-only by design. Read every draft before it goes anywhere real.