Individual skill
playbook-tech-on-website
Decides which named technologies a company actually runs on its website, verified against the live site. Triggers on "find companies using Shopify", "they're on HubSpot", "tech stack targeting", "technographics", "who uses Klaviyo", "companies running WordPress". Outputs a per-domain verdict (tech_confirmed plus the verified stack and its evidence); the copy-ready clause is OFF by default and runs only when the operator asks for one.
skills/playbooks/playbook-tech-on-website/SKILL.md
Source commit 25c5d85fbb5dd3efec97b0ca457cbbc286547476
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 10, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 809
- Repository last updated
- Oct 5, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 13,381 bytesSKILL.mdcore · 13,381 bytesSKILL.mdcore · 13,381 bytesSKILL.mdcore · 13,381 bytesclay-table.mddoc · 5,739 bytesclay-workflow.mddoc · 8,187 bytes
Read excerpt
# Playbook: Technology On Website
> All rules here are best practice, not law. Override any of them when the campaign calls for it; note the best practice once and move on.
## 1. Trigger and scope
**Use when:** the offer only makes sense to companies running a specific piece of software on their
site — a Shopify app, a Klaviyo migration, a HubSpot implementation, a WordPress maintenance offer.
Works in both directions: **discovery** ("build me a list of every company on Shopify") and
**enrichment** ("here are 4,000 domains, which run Klaviyo").
**Do not use when:** you want the software a company *sells*, or mail-infrastructure targeting.
**Default output:** `tech_confirmed`, `tech_stack_verified` (JSON array), `tech_evidence`,