find-service-providers
Use whenever the user wants to find, shortlist, vet, enrich, or research US professional-services firms — law, marketing, consulting, accounting, IT services, architecture, engineering, HR, PR, design, and similar B2B service providers. Triggers on requests like "find me a PPC agency in California", "shortlist three boutique IP law firms", "build a longlist of 50 mid-size IT consultancies", or "here are 12 agency domains — pull contact info and confirm which are US-based", even when the need is described indirectly without naming a category. Drives the ServiceGraph API (api.servicegraph.co) —
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill find-service-providers --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Find-service-providers helps a user locate US-based professional-services firms (e.g., law, marketing, IT, consulting, engineering, HR, design) and supports shortlisting, vetting, enrichment, and research tasks. It drives the ServiceGraph API to query a large catalog with filters for industry, services, location, size, ratings, and third-party listings. The skill is designed to respond to requests like finding a PPC agency in California or building a longlist of IT consultancies, and it can process indirect phrasing that implies a need for a structured firm directory.
How it works
- It uses the ServiceGraph API endpoints under the pro_services dataset to discover fields, build and validate a DSL filter, and perform a search that returns brief firm cards with an unlock hint and a total count.
- The workflow supports translating plain English intents into a DSL filter via translate-intent, validating with check, and then executing search to present options.
- When a user selects firms, it unlocks detail data via the Unlock endpoint, returning full detail blocks (contact fields, address, socials, platforms map) for each unlocked firm, with a 30-day TTL on detail data and a per-firm billing model.
- The skill emphasizes cost awareness: discovery, validation, and brief reads are free; detailed data costs 10 credits per firm with atomic unlocking behavior.
- Apexes are identified as apex domains (lowercase host) and used to fetch or unlock specific rows; 404 indicates not in catalog with no charge.
When to use it
Use when a user asks to find, shortlist, vet, or enrich US professional-services firms, across various industries and services, including indirect or multi-criterion requests. Skip non-US firms, personal/consumer services, individual freelancers, recruiting tasks, or general web research without a structured firm directory. Triggered by phrases like find me a PPC agency in California or build a longlist of 50 mid-size IT consultancies.
What it can touch
- API endpoints under https://api.servicegraph.co (via MCP tools or REST flow):
- GET /v1/datasets/pro_services/fields
- GET /v1/datasets/pro_services/check
- POST /v1/datasets/pro_services/translate-intent
- GET /v1/datasets/pro_services/search
- GET /v1/datasets/pro_services/:apex
- POST /v1/datasets/pro_services/unlocks
- GET /v1/me/credits
- The toolset includes mcp__servicegraph__list_fields, mcp__servicegraph__list_field_values, mcp__servicegraph__check_filter, mcp__servicegraph__translate_intent, mcp__servicegraph__search_dataset, mcp__servicegraph__get_row, mcp__servicegraph__unlock_rows, mcp__servicegraph__get_credit_balance.
Caveats
- Costs are charged per unlocked firm (10 credits) with a 30-day TTL for detail data; briefs remain free.
- The dataset is US-only B2B pro-services; non-US requests or consumer/legal/financial personal needs may be refused.
- The translator is a convenience and may return an empty filter or a questionable result; always inspect reasoning and count before searching.
- Unlocks are atomic per batch; partial success may still charge for the chosen apexes.
- All interactions assume a bearer API key; the token must not appear in the LLM context.
# find-service-providers ## Overview Drive the **ServiceGraph API** (`https://api.servicegraph.co`) to find, shortlist, and enrich US professional-services firms. The API hosts several **datasets** behind a uniform per-dataset URL shape (`/v1/datasets/:id/…`). This skill is for the agencies dataset — **dataset id `pro_services`** — which holds 100k+ B2B service firms classified across 22 industrie
What does the find-service-providers skill do?
Use whenever the user wants to find, shortlist, vet, enrich, or research US professional-services firms — law, marketing, consulting, accounting, IT services, architecture, engineering, HR, PR, design, and similar B2B service providers. Triggers on requests like "find me a PPC agency in California", "shortlist three boutique IP law firms", "build a longlist of 50 mid-size IT consultancies", or "here are 12 agency domains — pull contact info and confirm which are US-based", even when the need is described indirectly without naming a category. Drives the ServiceGraph API (api.servicegraph.co) —
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill find-service-providers --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
