geo-prospect

Q: How do I install geo-prospect?

Run npx skills add https://github.com/zubair-trabzada/geo-seo-claude --skill geo-prospect 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/geo-prospect/ (personal) or .claude/skills/geo-prospect/ (project).

by zubair-trabzadaMarketing & SEO

CRM-lite for managing GEO agency prospects and clients. Track leads through the full sales pipeline: Lead → Qualified → Proposal Sent → Won → Lost. Store audit history, notes, deal values, and generate pipeline summaries. Use when user says "prospect", "lead", "client", "pipeline", "crm", "nuovo prospect", "aggiungi cliente", or when managing the business side of GEO services.

Installs: 785
Last 24h: —
Trending rank: —
Security: Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/zubair-trabzada/geo-seo-claude --skill geo-prospect

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 geo-prospect 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.

GEO Prospect Manager

Purpose

Manage GEO agency prospects and clients through the full sales lifecycle. All data is stored in ~/.geo-prospects/prospects.json (persistent across sessions).

Commands

Command	What It Does
`/geo prospect new <domain>`	Create new prospect (interactive prompts)
`/geo prospect list`	Show all prospects with pipeline status
`/geo prospect list <status>`	Filter: lead, qualified, proposal, won, lost
`/geo prospect show <id-or-domain>`	Full prospect detail with history
`/geo prospect audit <id-or-domain>`	Run quick GEO audit and save to prospect record
`/geo prospect note <id-or-domain> "<text>"`	Add interaction note with timestamp
`/geo prospect status <id-or-domain> <new-status>`	Move through pipeline
`/geo prospect won <id-or-domain> <monthly-value>`	Mark as won, set contract value
`/geo prospect lost <id-or-domain> "<reason>"`	Mark as lost with reason
`/geo prospect pipeline`	Visual pipeline summary with revenue forecast

Data Structure

Each prospect is stored as a JSON record:

{
  "id": "PRO-001",
  "company": "Electron Srl",
  "domain": "electron-srl.com",
  "contact_email": "info@electron-srl.com",
  "contact_name": "",
  "industry": "Educational Equipment Manufacturing",
  "country": "Italy",
  "status": "qualified",
  "geo_score": 32,
  "audit_date": "2026-03-12",
  "audit_file": "~/.geo-prospects/audits/electron-srl.com-2026-03-12.md",
  "proposal_file": "~/.geo-prospects/proposals/electron-srl.com-proposal.md",
  "monthly_value": 0,
  "contract_start": null,
  "contract_months": 0,
  "notes": [
    {
      "date": "2026-03-12",
      "text": "Initial GEO quick scan. Score 32/100 - Critical tier. Strong candidate for GEO services."
    }
  ],
  "created_at": "2026-03-12",
  "updated_at": "2026-03-12"
}

Orchestration Instructions

`/geo prospect new <domain>`

Check if ~/.geo-prospects/prospects.json exists, create if not (empty array)
Auto-detect company name from domain (e.g., electron-srl.com → Electron Srl)
Assign next sequential ID: PRO-001, PRO-002, etc.
Ask user for:
- Contact name (optional)
- Contact email
- Monthly contract value estimate (optional)
Set status to lead
Save to JSON file
Suggest next step: "Run /geo prospect audit electron-srl.com to score this prospect"

`/geo prospect list`

Read ~/.geo-prospects/prospects.json and render a summary table:

GEO Prospect Pipeline — March 2026
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

ID       Domain                  Company           Status      Score  Value
───────  ──────────────────────  ────────────────  ──────────  ─────  ──────
PRO-001  electron-srl.com        Electron Srl      Qualified   32/100  €4.5K
PRO-002  acme.com                ACME Corp         Lead        —       —
PRO-003  bigshop.it              BigShop           Won         41/100  €6.0K

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Pipeline: 1 lead | 1 qualified | 0 proposals | 1 won | 0 lost
Committed MRR: €6,000 | Pipeline Value: €4,500

`/geo prospect audit <id-or-domain>`

Run /geo quick <domain> to get GEO snapshot score
Save score to prospect record: geo_score, audit_date
Save audit output to ~/.geo-prospects/audits/<domain>-<date>.md
Update audit_file path in prospect record
Add auto-note: "Quick audit run. GEO Score: XX/100."
If score < 55: suggest "Score indicates strong sales opportunity. Run /geo proposal <domain> to generate proposal."

`/geo prospect note <id-or-domain> "<text>"`

Find prospect by ID or domain
Append note with current ISO date
Save back to JSON
Confirm: "Note added to Electron Srl (PRO-001)"

`/geo prospect status <id-or-domain> <status>`

Valid statuses: lead, qualified, proposal, won, lost

Update status field
Add auto-note: "Status changed to <status>"
Save and confirm

`/geo prospect pipeline`

Visual revenue-focused pipeline summary:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
GEO AGENCY PIPELINE SUMMARY — March 2026
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

STAGE          COUNT   POTENTIAL VALUE   NOTES
─────────────  ─────   ───────────────   ─────────────────────
Lead             2      €8,000/mo        New discoveries
Qualified        1      €4,500/mo        Ready for proposal
Proposal Sent    1      €6,000/mo        Awaiting signature
Won              3      €18,500/mo       Active clients (MRR)
Lost             1      —                Budget freeze

COMMITTED MRR:        €18,500
PIPELINE (qualified+): €10,500
TOTAL POTENTIAL:      €29,000/mo → €348,000/yr

Next actions:
→ PRO-003 (acme.com): Send proposal — score 38/100 (strong case)
→ PRO-007 (shop.it): Follow up — proposal sent 8 days ago
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Storage Location

All data stored in ~/.geo-prospects/:

~/.geo-prospects/
├── prospects.json          # Main CRM database
├── audits/                 # Quick audit snapshots
│   └── electron-srl.com-2026-03-12.md
└── proposals/              # Generated proposals
    └── electron-srl.com-proposal.md

Create directory if it does not exist: mkdir -p ~/.geo-prospects/audits ~/.geo-prospects/proposals

Pipeline Stage Definitions

Status	Meaning	Typical Next Action
`lead`	Discovered, not yet contacted	Run quick audit, assess opportunity
`qualified`	Audit done, confirmed pain points	Generate proposal
`proposal`	Proposal sent, awaiting decision	Follow up, answer questions
`won`	Contract signed, active client	Run full audit, start onboarding
`lost`	Deal closed lost	Log reason for future reference

Output

All commands print confirmation + current prospect status to terminal
No external files unless explicitly saving audits/proposals
JSON database is the single source of truth

FAQ

What does the geo-prospect skill do?

How do I install geo-prospect?

Run npx skills add https://github.com/zubair-trabzada/geo-seo-claude --skill geo-prospect 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/geo-prospect/ (personal) or .claude/skills/geo-prospect/ (project).

Which AI agents can use geo-prospect?

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 geo-prospect 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 geo-prospect?

It is published by zubair-trabzada in zubair-trabzada/geo-seo-claude. It has 785 recorded installs.