@maximusgtm/lead-management 1.0.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.claude-plugin/plugin.json +22 -0
- package/README.md +54 -0
- package/SKILL.md +93 -0
- package/lead-sourcing/SKILL.md +139 -0
- package/package.json +17 -0
|
@@ -0,0 +1,22 @@
|
|
|
1
|
+
{
|
|
2
|
+
"name": "@maximusgtm/lead-management",
|
|
3
|
+
"version": "1.0.0",
|
|
4
|
+
"description": "Lead management skill for Maximus GTM - search, filter, enrich, and analyze leads",
|
|
5
|
+
"author": "Maximus GTM",
|
|
6
|
+
"homepage": "https://maximusgtm.com",
|
|
7
|
+
"mcp": {
|
|
8
|
+
"servers": {
|
|
9
|
+
"maximus": {
|
|
10
|
+
"type": "url",
|
|
11
|
+
"url": "${MAXIMUS_MCP_URL}",
|
|
12
|
+
"headers": {
|
|
13
|
+
"Authorization": "Bearer ${MAXIMUS_API_KEY}"
|
|
14
|
+
}
|
|
15
|
+
}
|
|
16
|
+
}
|
|
17
|
+
},
|
|
18
|
+
"skills": [
|
|
19
|
+
"SKILL.md",
|
|
20
|
+
"lead-sourcing/SKILL.md"
|
|
21
|
+
]
|
|
22
|
+
}
|
package/README.md
ADDED
|
@@ -0,0 +1,54 @@
|
|
|
1
|
+
# @maximusgtm/lead-management
|
|
2
|
+
|
|
3
|
+
Claude Code skill for lead management on the Maximus GTM platform. Search, filter, enrich, and analyze leads using natural language.
|
|
4
|
+
|
|
5
|
+
## Installation
|
|
6
|
+
|
|
7
|
+
```bash
|
|
8
|
+
/plugin install @maximusgtm/lead-management
|
|
9
|
+
```
|
|
10
|
+
|
|
11
|
+
## Configuration
|
|
12
|
+
|
|
13
|
+
Set the following environment variables before using the skill:
|
|
14
|
+
|
|
15
|
+
| Variable | Description |
|
|
16
|
+
|----------|-------------|
|
|
17
|
+
| `MAXIMUS_MCP_URL` | URL of your Maximus MCP server (e.g., `https://mcp.maximusgtm.com/mcp`) |
|
|
18
|
+
| `MAXIMUS_API_KEY` | Your MCP agent API key |
|
|
19
|
+
|
|
20
|
+
### Getting an API Key
|
|
21
|
+
|
|
22
|
+
1. Log in to the Maximus GTM portal
|
|
23
|
+
2. Navigate to **Settings > MCP Agents**
|
|
24
|
+
3. Create a new agent with the `leads` and `accounts` scopes
|
|
25
|
+
4. Copy the generated API key
|
|
26
|
+
|
|
27
|
+
## Available Tools
|
|
28
|
+
|
|
29
|
+
### Account Context
|
|
30
|
+
- `maximus_list_accounts` - List available accounts
|
|
31
|
+
- `maximus_get_account` - Get account details
|
|
32
|
+
|
|
33
|
+
### Lead Data
|
|
34
|
+
- `maximus_list_leads` - Search and filter leads with pagination
|
|
35
|
+
- `maximus_get_lead` - Get complete lead details
|
|
36
|
+
- `maximus_get_lead_stats` - Aggregate lead statistics
|
|
37
|
+
|
|
38
|
+
### Lead Search (External)
|
|
39
|
+
- `maximus_search_leads` - Search for new leads by criteria (Apollo, Builtin DB)
|
|
40
|
+
- `maximus_search_leads_from_icp` - Search using ICP-derived criteria
|
|
41
|
+
- `maximus_enrich_lead` - Enrich a person by email address
|
|
42
|
+
- `maximus_list_lead_search_providers` - List available search providers
|
|
43
|
+
|
|
44
|
+
## Usage Examples
|
|
45
|
+
|
|
46
|
+
```
|
|
47
|
+
> Show me all qualified leads from Apollo
|
|
48
|
+
|
|
49
|
+
> Search for VP-level SaaS leaders in the US
|
|
50
|
+
|
|
51
|
+
> Enrich sarah@techcorp.com
|
|
52
|
+
|
|
53
|
+
> What's my lead pipeline health?
|
|
54
|
+
```
|
package/SKILL.md
ADDED
|
@@ -0,0 +1,93 @@
|
|
|
1
|
+
# Lead Management Skill
|
|
2
|
+
|
|
3
|
+
Specialized skill for working with leads in the Maximus GTM platform. Use this for lead-focused operations including search, filtering, quality analysis, and bulk operations.
|
|
4
|
+
|
|
5
|
+
## Prerequisites
|
|
6
|
+
|
|
7
|
+
- Use `maximus_list_accounts` to find the `accountId` before calling lead tools
|
|
8
|
+
- Use `maximus_get_account` for account context (plan limits, integrations status)
|
|
9
|
+
|
|
10
|
+
## When to Use
|
|
11
|
+
|
|
12
|
+
Use this skill when the user wants to:
|
|
13
|
+
- Search or filter leads
|
|
14
|
+
- Understand lead quality scores
|
|
15
|
+
- Analyze lead sources
|
|
16
|
+
- Get lead statistics and trends
|
|
17
|
+
- Work with specific leads
|
|
18
|
+
|
|
19
|
+
## Available MCP Tools
|
|
20
|
+
|
|
21
|
+
### Lead Data
|
|
22
|
+
- `maximus_list_leads` - Search and filter leads with pagination
|
|
23
|
+
- `maximus_get_lead` - Get complete lead details
|
|
24
|
+
- `maximus_get_lead_stats` - Aggregate statistics
|
|
25
|
+
|
|
26
|
+
### Lead Search (External)
|
|
27
|
+
- `maximus_search_leads` - Search for new leads by criteria (Apollo, Builtin DB)
|
|
28
|
+
- `maximus_search_leads_from_icp` - Search using ICP-derived criteria
|
|
29
|
+
- `maximus_enrich_lead` - Enrich a person by email address
|
|
30
|
+
- `maximus_list_lead_search_providers` - List available search providers
|
|
31
|
+
|
|
32
|
+
## Lead Filtering
|
|
33
|
+
|
|
34
|
+
The `maximus_list_leads` tool supports these filters:
|
|
35
|
+
- `search` - Search by name, email, company
|
|
36
|
+
- `status` - Filter by lead status (new, contacted, qualified, converted)
|
|
37
|
+
- `source` - Filter by source (apollo, linkedin, manual, etc.)
|
|
38
|
+
- `sortBy` / `sortOrder` - Sort results
|
|
39
|
+
|
|
40
|
+
## Lead Quality Interpretation
|
|
41
|
+
|
|
42
|
+
When presenting lead data, interpret quality indicators:
|
|
43
|
+
|
|
44
|
+
### High Quality Lead Signals
|
|
45
|
+
- Complete contact information (email, phone, LinkedIn)
|
|
46
|
+
- Job title matches ICP buyer persona
|
|
47
|
+
- Company fits target firmographics
|
|
48
|
+
- Recent engagement activity
|
|
49
|
+
|
|
50
|
+
### Data Quality Issues to Flag
|
|
51
|
+
- Missing email or phone
|
|
52
|
+
- Generic email domains (gmail, yahoo)
|
|
53
|
+
- Incomplete company information
|
|
54
|
+
- Stale leads (no recent updates)
|
|
55
|
+
|
|
56
|
+
## Common Queries
|
|
57
|
+
|
|
58
|
+
**"Show me qualified leads"**
|
|
59
|
+
```
|
|
60
|
+
Use maximus_list_leads with status="qualified"
|
|
61
|
+
```
|
|
62
|
+
|
|
63
|
+
**"Find leads from Apollo in the last week"**
|
|
64
|
+
```
|
|
65
|
+
Use maximus_list_leads with source="apollo", sortBy="createdAt"
|
|
66
|
+
```
|
|
67
|
+
|
|
68
|
+
**"What's my lead pipeline health?"**
|
|
69
|
+
```
|
|
70
|
+
Use maximus_get_lead_stats for aggregate view
|
|
71
|
+
```
|
|
72
|
+
|
|
73
|
+
## Response Format
|
|
74
|
+
|
|
75
|
+
When presenting leads:
|
|
76
|
+
1. Show total count and pagination info
|
|
77
|
+
2. Present key fields: Name, Company, Title, Email
|
|
78
|
+
3. Include status and source
|
|
79
|
+
4. Highlight quality indicators
|
|
80
|
+
5. Offer drill-down options
|
|
81
|
+
|
|
82
|
+
Example:
|
|
83
|
+
```
|
|
84
|
+
Found 47 qualified leads from Apollo:
|
|
85
|
+
|
|
86
|
+
1. **Sarah Chen** - VP Engineering at TechCorp
|
|
87
|
+
sarah@techcorp.com | Added 2 days ago | Score: 85
|
|
88
|
+
|
|
89
|
+
2. **Mike Johnson** - CTO at StartupXYZ
|
|
90
|
+
mike@startupxyz.io | Added 5 days ago | Score: 78
|
|
91
|
+
|
|
92
|
+
...showing 1-10 of 47. Say "show more" to continue.
|
|
93
|
+
```
|
|
@@ -0,0 +1,139 @@
|
|
|
1
|
+
# Lead Sourcing Skill
|
|
2
|
+
|
|
3
|
+
Specialized skill for finding and importing leads from multiple sources. Supports Apollo API search, database search, and ICP-driven lead discovery.
|
|
4
|
+
|
|
5
|
+
## When to Use
|
|
6
|
+
|
|
7
|
+
Use this skill when the user wants to:
|
|
8
|
+
- Find leads matching specific criteria
|
|
9
|
+
- Search for leads from an ICP profile
|
|
10
|
+
- Enrich existing leads with additional data
|
|
11
|
+
- Understand which lead search providers are available
|
|
12
|
+
- Build a lead list from search results
|
|
13
|
+
- Compare lead sources
|
|
14
|
+
|
|
15
|
+
## Available MCP Tools
|
|
16
|
+
|
|
17
|
+
### Search
|
|
18
|
+
- `maximus_search_leads` - Search by criteria (job titles, industries, company size, location, etc.)
|
|
19
|
+
- `maximus_search_leads_from_icp` - Search using an ICP's criteria (auto-converts ICP fields)
|
|
20
|
+
|
|
21
|
+
### Enrichment
|
|
22
|
+
- `maximus_enrich_lead` - Enrich a person by email (title, company, seniority, LinkedIn)
|
|
23
|
+
|
|
24
|
+
### Providers
|
|
25
|
+
- `maximus_list_lead_search_providers` - List available providers for the account
|
|
26
|
+
|
|
27
|
+
## Provider Selection Guide
|
|
28
|
+
|
|
29
|
+
| Provider | Best For | Requires |
|
|
30
|
+
|----------|----------|----------|
|
|
31
|
+
| **APOLLO** | External lead discovery, fresh data | Apollo API key (in Integrations) |
|
|
32
|
+
| **BUILTIN** | Searching existing leads in database | Nothing (always available) |
|
|
33
|
+
|
|
34
|
+
**Auto-detection:** If no provider is specified, the system checks for Apollo first, then falls back to Builtin.
|
|
35
|
+
|
|
36
|
+
## Search Criteria Reference
|
|
37
|
+
|
|
38
|
+
| Field | Type | Description | Example |
|
|
39
|
+
|-------|------|-------------|---------|
|
|
40
|
+
| `jobTitles` | string[] | Job titles to match | ["VP Engineering", "CTO", "Head of Product"] |
|
|
41
|
+
| `seniorities` | string[] | Seniority levels | ["c_suite", "vp", "director", "manager"] |
|
|
42
|
+
| `industries` | string[] | Target industries | ["SaaS", "FinTech", "E-commerce"] |
|
|
43
|
+
| `employeeRange` | {min, max} | Company size | {min: 50, max: 500} |
|
|
44
|
+
| `locations.countries` | string[] | Countries | ["United States", "Canada"] |
|
|
45
|
+
| `locations.cities` | string[] | Cities | ["San Francisco", "New York"] |
|
|
46
|
+
| `technologies` | string[] | Tech stack | ["React", "AWS", "Salesforce"] |
|
|
47
|
+
| `keywords` | string[] | General keywords | ["AI", "machine learning"] |
|
|
48
|
+
| `companyDomains` | string[] | Specific domains | ["stripe.com", "shopify.com"] |
|
|
49
|
+
| `excludeTitles` | string[] | Titles to exclude | ["Intern", "Assistant"] |
|
|
50
|
+
| `limit` | number | Results per page | 25 |
|
|
51
|
+
| `page` | number | Page number | 1 |
|
|
52
|
+
|
|
53
|
+
## ICP-to-Search Mapping
|
|
54
|
+
|
|
55
|
+
When using `maximus_search_leads_from_icp`, ICP fields map to search criteria:
|
|
56
|
+
|
|
57
|
+
| ICP Field | Search Criteria |
|
|
58
|
+
|-----------|----------------|
|
|
59
|
+
| `targetCompany.verticals` | `industries` |
|
|
60
|
+
| `targetCompany.employeeRange` | `employeeRange` |
|
|
61
|
+
| `targetCompany.technologies` | `technologies` |
|
|
62
|
+
| `buyerPersonas[].roles` | `jobTitles` |
|
|
63
|
+
| `buyerPersonas[].seniority` | `seniorities` |
|
|
64
|
+
| `geography.countries` | `locations.countries` |
|
|
65
|
+
| `geography.cities` | `locations.cities` |
|
|
66
|
+
| `exclusions.titles` | `excludeTitles` |
|
|
67
|
+
| `exclusions.industries` | `excludeIndustries` |
|
|
68
|
+
|
|
69
|
+
## Workflows
|
|
70
|
+
|
|
71
|
+
### "Find leads matching my ICP"
|
|
72
|
+
|
|
73
|
+
```
|
|
74
|
+
1. maximus_list_lead_search_providers (check what's available)
|
|
75
|
+
2. maximus_search_leads_from_icp (auto-converts ICP and searches)
|
|
76
|
+
3. Review results with user
|
|
77
|
+
4. If satisfactory, proceed to campaign assignment
|
|
78
|
+
```
|
|
79
|
+
|
|
80
|
+
### "Search for VP-level SaaS leaders in the US"
|
|
81
|
+
|
|
82
|
+
```
|
|
83
|
+
1. maximus_search_leads with criteria:
|
|
84
|
+
- jobTitles: ["VP", "Vice President"]
|
|
85
|
+
- industries: ["SaaS", "Software"]
|
|
86
|
+
- locations: { countries: ["United States"] }
|
|
87
|
+
- seniorities: ["vp"]
|
|
88
|
+
2. Present results with name, title, company, email
|
|
89
|
+
3. Offer to refine or expand search
|
|
90
|
+
```
|
|
91
|
+
|
|
92
|
+
### "Enrich this email address"
|
|
93
|
+
|
|
94
|
+
```
|
|
95
|
+
1. maximus_enrich_lead with the email
|
|
96
|
+
2. Present enriched data (title, company, seniority, LinkedIn)
|
|
97
|
+
3. Offer to add to a lead list or campaign
|
|
98
|
+
```
|
|
99
|
+
|
|
100
|
+
### "What data sources do I have?"
|
|
101
|
+
|
|
102
|
+
```
|
|
103
|
+
1. maximus_list_lead_search_providers
|
|
104
|
+
2. Present available vs. all providers
|
|
105
|
+
3. If Apollo not available, suggest adding API key
|
|
106
|
+
```
|
|
107
|
+
|
|
108
|
+
## Response Format
|
|
109
|
+
|
|
110
|
+
When presenting search results:
|
|
111
|
+
```
|
|
112
|
+
Found 234 leads matching your criteria via Apollo
|
|
113
|
+
|
|
114
|
+
Criteria used:
|
|
115
|
+
- Titles: VP Engineering, CTO, Head of Engineering
|
|
116
|
+
- Industries: SaaS, FinTech
|
|
117
|
+
- Company size: 50-500 employees
|
|
118
|
+
- Location: United States
|
|
119
|
+
|
|
120
|
+
Top results:
|
|
121
|
+
1. Sarah Chen — VP Engineering at CloudTech (SaaS, 200 employees)
|
|
122
|
+
sarah@cloudtech.io | San Francisco, CA
|
|
123
|
+
|
|
124
|
+
2. James Park — CTO at PayFlow (FinTech, 150 employees)
|
|
125
|
+
james@payflow.com | New York, NY
|
|
126
|
+
|
|
127
|
+
3. Maria Garcia — Head of Engineering at DataSync (SaaS, 320 employees)
|
|
128
|
+
maria@datasync.io | Austin, TX
|
|
129
|
+
|
|
130
|
+
Showing 1-10 of 234. Say "show more" or "refine search" to continue.
|
|
131
|
+
```
|
|
132
|
+
|
|
133
|
+
## Quality Assessment
|
|
134
|
+
|
|
135
|
+
When reviewing search results, flag:
|
|
136
|
+
- **Missing emails** — leads without email addresses cannot be contacted
|
|
137
|
+
- **Generic domains** — gmail.com, yahoo.com may indicate personal accounts
|
|
138
|
+
- **Title mismatches** — results that don't match the intended seniority
|
|
139
|
+
- **Company size outliers** — companies outside the target range
|
package/package.json
ADDED
|
@@ -0,0 +1,17 @@
|
|
|
1
|
+
{
|
|
2
|
+
"name": "@maximusgtm/lead-management",
|
|
3
|
+
"version": "1.0.0",
|
|
4
|
+
"description": "Lead management skill for Maximus GTM platform",
|
|
5
|
+
"author": "Maximus GTM",
|
|
6
|
+
"license": "UNLICENSED",
|
|
7
|
+
"files": [
|
|
8
|
+
".claude-plugin/",
|
|
9
|
+
"SKILL.md",
|
|
10
|
+
"lead-sourcing/",
|
|
11
|
+
"README.md"
|
|
12
|
+
],
|
|
13
|
+
"publishConfig": {
|
|
14
|
+
"access": "public",
|
|
15
|
+
"registry": "https://registry.npmjs.org"
|
|
16
|
+
}
|
|
17
|
+
}
|