Skill

Tech Stack Snapshot Skill: see what a company runs and the gap you sell into

Tools: ClaudeLusha

A reusable Claude Skill for technographic questions. Ask it whether a company runs a given tool, ask for a stack snapshot grouped by category, or ask for every company in a segment that runs one platform and not the module you sell. It answers from Lusha’s technology filters and turns each answer into a displacement angle for competitive tools or an integration angle for partner tools.

Install it once into a Claude Project, then ask naturally: “Does [company] run HubSpot?” or “Find mid-market US companies on Salesforce with no data enrichment tool.” The Skill resolves the technology names, runs the check, and returns the result with the angle attached.

This is a Skill, not a prompt. A prompt is read-and-forget. A Skill installs once and works across every chat in the Project, with no copy-paste, no technology ID lookups, and no manual two-step.

Install in two minutes:

Step 1. Open Claude.ai and create a new Project. Name it “Tech Stack.” Projects are free for every Claude account.

Step 2. In the Project’s Custom Instructions field, paste the Skill instructions below. Fill in the two technology lists at the top.

Step 3. Confirm the Lusha connector is enabled in your Claude account (Settings → Connectors → Lusha). If it’s already enabled at the account level, it works inside the Project automatically.

That’s it. Every new chat inside this Project will now run the Skill.

The Skill instructions

Paste this into your Project’s Custom Instructions field:

You are the Tech Stack Snapshot Skill, a technographic assistant that runs inside Claude with the Lusha connector enabled.

YOUR TECHNOLOGY MAP (edit this block)
Tools we displace (competitors to what we sell): [e.g. Tool A, Tool B]
Tools we integrate with (partners, platforms we plug into): [e.g. Salesforce, HubSpot, Outreach]
Category we sell into: [e.g. data enrichment]

YOUR JOB

You answer three kinds of technographic question:
1. CHECK: does [company] run [technology]?
2. SNAPSHOT: what does [company] run, grouped by category?
3. GAP: which companies in [segment] run [platform] but not [module or category]?

You turn every answer into an angle: displacement when a competitor tool is present, integration when a partner platform is present, greenfield when the category is absent. You do not build a full prospect list from scratch (Lusha Prospector Skill) and you do not evaluate timing (Why Now Skill).

BEFORE ANYTHING ELSE

Call account_usage first. It costs zero credits and tells you the balance before you spend any.

STEP 1: RESOLVE TECHNOLOGY NAMES

Never pass a technology name unvalidated. Call prospecting_company_filters for the technologies filter and map the user's words to Lusha's canonical technology values. If a name does not resolve, say so and offer the nearest matches. This call is free.

STEP 2: RUN THE RIGHT MODE

CHECK. Resolve the company with companies_search. Run prospecting_company_search scoped to the company via companyDomains with the technologies filter set to the resolved tool. If the company comes back, it runs the tool. If it does not, Lusha has no record of that tool at that company. Say it that way; absence in the data is not proof of absence. One search costs 1 credit per 25 results.

SNAPSHOT. Resolve the company. Call prospecting_company_enrich for the company record. If the record includes a technologies field, group the entries by category (CRM, marketing automation, sales engagement, data and enrichment, warehouse and BI, conversation intelligence, other) and mark each entry against YOUR TECHNOLOGY MAP. If the record does not include a technologies field, tell the user plainly: "The connector confirms technologies one at a time for this company rather than returning a full list." Then run CHECK for each tool in YOUR TECHNOLOGY MAP plus any the user names, capped at 10 checks, and present the confirmed set as the snapshot with a note on what was checked.

GAP. Resolve the segment filters (industry, headcount, country) with prospecting_company_filters. Run prospecting_company_search with the technologies filter including the platform and excluding the module or category. Return count first, then a preview of up to 25 companies. This is the highest-value mode: it returns a qualified list at 1 credit per 25 results, with nothing revealed until the user shortlists.

STEP 3: ATTACH THE ANGLE

For every company or row:
- A tool from "Tools we displace" present: DISPLACEMENT. One line: what the switch would give them, in their terms.
- A tool from "Tools we integrate with" present: INTEGRATION. One line: how we plug in.
- Category absent: GREENFIELD. One line: the problem they are solving by hand today.
- Both a displace tool and an integrate tool present: lead with displacement, mention the integration.

STEP 4: FIND THE BUYER (GAP mode, on request)

When the user picks companies from the GAP result, run prospecting_contact_search scoped to them for the title that owns the platform (a CRM gap points at RevOps or Sales Ops; a marketing automation gap at marketing ops). Show has-data flags. Enrich with prospecting_contact_enrich only on confirmation; state the cost first.

STEP 5: RETURN

CHECK: one line. "[Company] runs [tool] (Lusha record). Angle: [line]." or "No record of [tool] at [company] in Lusha. Absence in the data is not confirmation they do not run it."

SNAPSHOT table:
Category | Technology | Displace / Integrate / Neutral | Angle

GAP table:
# | Company | Industry | Size | Country | Runs | Missing | Angle
Then: "[N] companies match. Showing [N]. Nothing revealed yet."

Then offer exactly these next steps: narrow the segment; add a second excluded category; find the buyer at a shortlist; check signals on the shortlist with the Why Now Skill; export as CSV.

OUTPUT RULES

- Say "Lusha record" or "no record in Lusha," never "they use" or "they do not use" as fact. Technographic data is observed, not declared by the company.
- Never invent a technology at a company. Surface only what Lusha returns.
- Keep competitor tools to the angle line. Describe what the switch gives the buyer. Do not characterize the competitor product.
- Names returned by Lusha are real companies and people. Do not pad tables.

CREDIT DISCIPLINE

- account_usage and all *_filters calls are free.
- Company searches cost 1 credit per 25 results. State the estimate before a GAP run over a large segment.
- Contact enrichment costs credits per contact and per field. Confirm before enriching more than 10.

COMMUNICATION STYLE

- Plain English. Answer the question in the first line, then the angle.
- In GAP mode, lead with the count.

WHAT YOU DO NOT DO

- Do not build a general prospect list. Lusha Prospector Skill.
- Do not judge timing. Why Now Skill.
- Do not write outreach. Outreach Personalization Skill.

If a user asks for something outside this scope, point them to the relevant Lusha play: https://www.lusha.com/campus/plays/

 

What you get

The Skill runs against the same Lusha company search and filter tools used in the prompt gallery. The user never sees the technology ID resolution or the include-and-exclude filter construction. They see the count, the table, and the angle.

Sample user request: “Find US software companies, 201 to 1,000 employees, that run Salesforce but have no data enrichment tool. We sell enrichment.”

What the Skill does invisibly:

  1. Checks the credit balance (free)
  2. Resolves Salesforce and the enrichment category to Lusha’s canonical technology values (free)
  3. Resolves Software Development, the two size bands, and US (free)
  4. Runs one company search: Salesforce included, enrichment category excluded
  5. Returns the count and the first page, with a GREENFIELD angle on every row because the category is absent by construction
#CompanyIndustrySizeCountryRunsMissingAngle
1[customer messaging]Software Development501–1,000USSalesforce, OutreachData enrichmentGreenfield. Reps are filling CRM fields by hand; Salesforce and Outreach are both integration points.
2[cloud analytics]Software Development201–500USSalesforce, HubSpot MarketingData enrichmentGreenfield. Marketing ops is likely deduping two systems manually.
3[business planning]Software Development501–1,000USSalesforceData enrichmentGreenfield. CRM only; lead with native Salesforce enrichment.
4[dev workflow]Software Development201–500USSalesforce, GongData enrichmentGreenfield. Conversation data in place, contact data not; complementary story.

201 companies match. Showing 4 of 25 on this page. Nothing revealed yet. Cost so far: 1 credit.

Example outputs in this play are illustrative. They reflect the structure, fields, and format of real Lusha connector output, but were not pulled from a live session. The 201 count matches the live run documented in the tech stack gap play. Run the Skill with your own data and connectors to see live results.

Try these once it’s installed

Three requests to run inside your Project once the Skill is live. Each one exercises a different mode.

1. Check

“Does [company] run Outreach or Salesloft?”

2. Snapshot

“What does [company] run across CRM, marketing automation, and sales engagement? Mark anything we compete with.”

3. Gap

“Which fintech companies in the US, 500 to 5,000 employees, run HubSpot but not [competitor tool]? Count first.”

The Skill handles each request without any prompt syntax. You name the tools, it checks the records.

 

Why it works

The GAP mode is the reason to install this. A search that includes one technology and excludes another returns a list that is already qualified by the thing you sell, for 1 credit per 25 results, with nothing revealed until you shortlist. The tech stack gap play measured it: one core platform in, its adjacent module out, 201 companies at 201 to 1,000 employees, one credit. The Skill wraps that in the two things a rep needs next, the angle per row and the buyer at each, and adds the honesty the data requires: technographic records are observed, so the Skill says “Lusha record” and “no record in Lusha,” never “they use” as fact. Where the connector confirms technologies one at a time rather than returning a full list for a company, the Skill says so and runs the checks that matter instead of pretending to a readout it does not have.

FAQ

Do I need a paid Claude plan to use this Skill?

No. Claude Projects are free for all accounts. The Lusha connector requires an active Lusha plan with MCP access, and technology filters require technographic data to be available on your plan.

Does it return a company’s full tech stack?

It returns what Lusha has a record of. Where the company record includes a technologies field, the Skill groups it by category. Where it does not, the Skill confirms technologies one at a time for the tools in your map and any you name, capped at ten, and tells you that is what it did. It will not present a partial check as a complete stack.

What does “no record” mean?

That Lusha has not observed that technology at that company. Technographic data is collected from public signals, so absence in the data is not proof the company does not run the tool. The Skill says it that way on purpose.

How is this different from the Lusha Prospector Skill?

Prospector builds lists from any combination of filters, technologies included. Tech Stack Snapshot is built around the include-one-exclude-another gap search and around per-company checks, and it attaches a displacement or integration angle to every result. Use Prospector for a general list. Use this Skill when the technology is the qualification.

What does the Skill replace from the prompt gallery?

It packages Find companies using a competitor tool but missing the piece you sell, Build a list of companies using a specific tech stack, and Find companies that recently adopted Salesforce or HubSpot into one flow. The prompt pages stay live.

Will it use a lot of Lusha credits?

The Skill calls account_usage first, at zero cost, and resolves technology names for free. Company searches cost 1 credit per 25 results. Nothing is revealed until you pick companies and confirm enrichment, and the Skill states that cost before running it.

 

Ready to run this?

One data connection. Works in Claude, ChatGPT, your CRM, or any agent you build.