playbook-tech-on-website

Verifies which named technologies a company runs on its website via live homepage fingerprinting.

Updated May 28, 2025
One-click install
npx skills add https://github.com/meloShaya/insteltech --skill playbook-tech-on-website-meloshaya
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playbook-tech-on-website
Source: https://github.com/meloShaya/insteltech/tree/main/crm/library/skills/playbooks/playbook-tech-on-website
Command: npx skills add https://github.com/meloShaya/insteltech --skill playbook-tech-on-website-meloshaya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Technographic databases report what a crawler saw at some unknown point in the past and are wrong often enough to embarrass a campaign — in testing, 4 of 10 provider-returned "Shopify" companies were not on Shopify. This Skill gates every domain against a live fetch of its actual homepage before it reaches a list or a personalization line. ## Core Features & Use Cases - Tandem discovery and union: Runs two technographic providers in parallel and unions the results, since measured overlap between providers was zero on first pages. - Live verification gate: Fetches each homepage with a browser user agent, matches fingerprints over HTML and response headers, and grades platform hits as confirmed only with header or oracle evidence. - Blocked and unconfirmed handling: Flags bot-walled or thin pages as blocked (never a negative) and HTML-only platform matches as unconfirmed, routing blocked rows to a rendering proxy rescue. - Opt-in personalization clause: Generates a 110-character cold-email clause via a locked prompt only when explicitly requested; the default deliverable is the verdict at zero model cost. - Use Case: Given 4,000 domains and a Klaviyo migration offer, run the gate to produce a per-domain tech_confirmed verdict with verified stack and evidence, expecting roughly 60% of a provider-sourced list to survive. ## Quick Start Verify which of the domains in my list actually run Shopify on their live websites and give me the confirmed verdicts with evidence.

Frequently Asked Questions about playbook-tech-on-website

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find companies using Shopify for cold outreach?

Run two technographic providers in tandem and union the results, since measured first-page overlap between providers was zero. Then verify every domain against its live homepage, because provider data alone returned 4 false positives out of 10 in testing.

How to verify a company actually uses a technology on its website?

Fetch the homepage with a browser user agent and match fingerprints over HTML and response headers. Platform hits like Shopify require header evidence such as x-shopid or an oracle endpoint like /products.json to grade as confirmed.

Why are technographic database lists inaccurate?

Technographic providers report what a crawler saw at an unstated point in the past, and measured raw precision was only 6 of 10 for a Shopify filter. Live homepage verification catches the stale and false rows before they reach a campaign.

What does a blocked result mean in website technology detection?

A blocked result means the page was never read, due to a 401/403/429 response, a body under 2,000 bytes, or a transport error. It is never a negative; route blocked rows through a rendering proxy rescue instead of excluding them.

Can Clay verify website technologies in a table column?

Not directly, because http-api-v2 parses responses as JSON and scrape-website does not expose response headers. The recommended approach is verifying outside Clay and importing verdicts, or standing up a small JSON verification endpoint the column can call.

When should the personalization clause not be generated?

Skip the clause by default; the verdict is the deliverable and costs zero model calls. Generate the 110-character line only when the brief explicitly requests one, and only for rows where tech_confirmed is true.