Guide · Agent skill
How to use the GEO Prospect Manager agent skill (geo-prospect)
Updated · written with AI from the project's own documentation and checked against our catalogue data
GEO Prospect Manager is an agent skill that turns your AI agent into a simple sales tracker for an agency selling GEO (generative engine optimisation, which means improving how a website appears in AI search answers). This guide explains what the skill does, how to install it, how to trigger it with plain requests, and what to watch for before you store client data in it. By the end you will be able to add prospects, move them through a pipeline, and print a revenue summary from chat.
GEO Prospect Managerzubair-trabzada/geo-seo-claude · MIT Download the skill Quick start
- 1Download and unzip. Download the skill ZIP from this page and unzip it so the geo-prospect folder with SKILL.md is in place.
- 2Choose the install location. Place the folder in ~/.claude/skills/ for personal use, or in a project's .claude/skills/ folder, or upload it under Settings → Capabilities → Skills in the Claude apps.
- 3Confirm write access. Make sure your user can write to your home directory, since data is stored in ~/.geo-prospects/.
- 4Add your first prospect. Run /geo prospect new with a domain and answer the prompts for contact details and an optional monthly value.
- 5Audit and qualify. Run /geo prospect audit if the companion /geo quick command is available, then move the prospect to qualified.
- 6Record outcomes. Use the won or lost commands with a monthly value or a reason, then check /geo prospect pipeline.
What is an agent skill, and what does geo-prospect do?
An agent skill is a folder containing a SKILL.md instruction file that tells an AI agent how to handle a particular task. When the skill is installed and your request matches its description, the agent follows those instructions.
The geo-prospect skill keeps a local JSON file of prospective clients. Each prospect moves through the stages Lead, Qualified, Proposal Sent, Won or Lost, and the record can hold notes, audit scores, and expected monthly contract values. The skill can also print a pipeline table with a revenue forecast and suggest the next action for each prospect.
- Stores prospects in ~/.geo-prospects/prospects.json
- Tracks status through lead, qualified, proposal, won and lost
- Keeps timestamped notes, GEO audit scores and monthly contract values
- Prints a pipeline summary with committed MRR and pipeline value
What you need before installing
The skill is written for Claude Code or another agent that can read and write files and run shell commands. Its allowed tools are Read, Write, Bash and Glob. You also need write access to your home directory, because data is saved under ~/.geo-prospects/.
The audit feature depends on a companion /geo quick command from the same repository. The SKILL.md refers to it, but that command is not included in the files for this skill, so audits will not run on their own.
- An agent that can read/write files and run shell commands (Claude Code or similar)
- Write access to ~/.geo-prospects/
- The companion /geo quick audit command from the same repository, if you want the audit feature
Install the geo-prospect skill
Download the ZIP for this skill from this page and unzip it. For a personal install, place the skill folder in ~/.claude/skills/. To scope it to one project, place it in that project's .claude/skills/ folder instead.
If you use the Claude apps rather than Claude Code, you can upload the skill under Settings → Capabilities → Skills.
- Personal install: unzip into ~/.claude/skills/
- Project install: unzip into your project's .claude/skills/
- Claude apps: Settings → Capabilities → Skills, then upload
~/.claude/skills/geo-prospect/SKILL.mdTrigger the skill with natural requests
You can use the slash commands directly, or describe what you want. The SKILL.md lists trigger words including "prospect", "lead", "client", "pipeline" and "crm", and also "nuovo prospect" and "aggiungi cliente". Using one of these words in a clear request should lead the agent to use the skill.
The commands below are the ones defined in the skill. Replace the placeholders with your own domain or prospect ID.
- Add a prospect: /geo prospect new <domain>
- List everyone: /geo prospect list
- Filter by stage: /geo prospect list qualified
- Show one prospect: /geo prospect show PRO-001
- Add a note: /geo prospect note <id-or-domain> "<text>"
- Change stage: /geo prospect status <id-or-domain> proposal
- Mark won with value: /geo prospect won <id-or-domain> <monthly-value>
- Mark lost with reason: /geo prospect lost <id-or-domain> "<reason>"
- Show pipeline summary: /geo prospect pipeline
/geo prospect new electron-srl.comExample workflow from first lead to won client
A typical flow starts with /geo prospect new for a domain. The skill auto-detects a company name from the domain, assigns the next ID such as PRO-001, asks for an optional contact name, a contact email and an optional monthly value estimate, then sets the status to lead.
Next, run the audit command for that domain. The skill saves the score, the audit date and a snapshot file under ~/.geo-prospects/audits/. If the score is below 55, the skill suggests generating a proposal. Once a deal is signed, mark it won with the monthly value, and check the pipeline view for the revenue summary.
- Create: /geo prospect new electron-srl.com
- Audit: /geo prospect audit electron-srl.com (needs the companion /geo quick command)
- Qualify: /geo prospect status electron-srl.com qualified
- Win: /geo prospect won electron-srl.com 4500
- Review: /geo prospect pipeline
/geo prospect audit electron-srl.comWhere your data is stored and how it is organised
Everything lives in ~/.geo-prospects/. The main database is prospects.json, and the folders audits/ and proposals/ hold snapshot files. The skill says to create these folders if they do not exist. The JSON file is the single source of truth, so backing it up is the simplest way to protect your pipeline.
Each prospect record includes fields such as id, company, domain, contact_email, status, geo_score, audit_date, monthly_value, notes and timestamps.
- ~/.geo-prospects/prospects.json: main database
- ~/.geo-prospects/audits/: audit snapshots
- ~/.geo-prospects/proposals/: generated proposal files
mkdir -p ~/.geo-prospects/audits ~/.geo-prospects/proposalsSafety notes: scripts, network and personal data
The skill is listed as running scripts, and it allows Bash. It is listed as not using the network. Because it writes files and runs shell commands, review the SKILL.md and any scripts before installing, especially in a shared environment.
Contact names and emails are stored in plain JSON on disk without encryption. Store only what you need, keep the file out of shared folders and synced locations you do not trust, and remove records you no longer need.
- Runs scripts (Bash is an allowed tool), so review before installing
- Listed as not using the network
- Contact data is plain text in prospects.json
- Data is local to one user's home folder, so it is not shared between team members
Tips for getting the most from it
Use consistent domains as identifiers, because the commands accept either an ID or a domain. Add a note after every call or message so the history in show makes sense later. Run the pipeline view weekly to see which next actions are due.
Treat the revenue figures as estimates. The monthly value is whatever you enter, and the forecast is only as good as those inputs.
- Accept either an ID (PRO-001) or a domain in every command
- Log a note after each interaction
- Keep monthly values realistic, since the forecast uses what you enter
What people use it for
- Tracking a handful of freelance SEO or GEO prospects without a paid CRM
- Logging call notes and next steps against each prospect's domain
- Estimating committed monthly recurring revenue from won clients and qualified pipeline
- Recording why deals were lost so you can review them later
- Using the file structure as a starting template for your own local sales pipeline skill
Frequently asked questions
Is the geo-prospect skill free?
The source material does not state a licence fee, but the repository is listed under the MIT licence, which is a permissive open source licence. Check the licence file in the repository for the full terms before you rely on it commercially.
What do I need to install geo-prospect?
You need an agent that can read and write files and run shell commands, such as Claude Code. You also need write access to ~/.geo-prospects/, and the companion /geo quick command if you want the audit feature.
Where do I put the skill folder?
Put it in ~/.claude/skills/ for a personal install, or in your project's .claude/skills/ folder for one project. In the Claude apps, you can upload it under Settings → Capabilities → Skills.
Can geo-prospect run a full GEO audit or write proposals?
Not by itself. The SKILL.md refers to /geo quick and /geo proposal, but those commands are not included in these files, so the audit and proposal features depend on other parts of the repository.
Can my team share one prospect list?
Not as delivered. All data lives in one local file under your home folder, so it is designed for a single user. Teams that need shared, multi-user CRM data should choose a tool built for that.
Is my client data safe in this skill?
Data is stored locally, but contact names and emails are kept as plain JSON with no encryption. Keep the file private, limit what you store, and review the scripts before installing.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
geo-prospect suits a small GEO or SEO agency, a freelancer tracking a few prospects, or a developer who wants a template for a local sales pipeline skill. It is a poor fit for teams that need shared CRM data, for anyone expecting full audits or proposal writing from this package alone, or for handling sensitive contact data without extra care.
Download the skill