Individual skill
clay-playbooks
Index and shared harness for the 19 signal playbooks. Each playbook turns one buying signal (new in role, raised a round, hiring surge, pricing page, tech on website, ...) into one copy-ready sentence you can drop into a cold email. Every playbook ships three ways to run it: as a Claude skill, as a Clay table built through a browser harness, and as a Clay workflow built from the clay CLI. Use when someone says "personalize this list", "what signal should I use", "build the Clay column for X", or names any of the 19 signals.
skills/playbooks/clay-playbooks/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.
- operations 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 · 8,699 bytesSKILL.mdcore · 8,699 bytesSKILL.mdcore · 8,699 bytesSKILL.mdcore · 8,699 bytesSKILL.mdcore · 8,699 bytesclay-cli-harness.mddoc · 11,027 bytesclay-table-harness.mddoc · 10,160 bytes
Read excerpt
# Clay Playbooks
Nineteen playbooks. Each one answers a single question:
> A campaign needs signal X on every row. What is the cheapest reliable way to get X, and what exact prompt turns X into copy-ready text?
One playbook produces one field. `new_in_role_line`. `funding_line`. `pricing_page_line`. That
field slots into one sentence of email 1. That is the whole product.
## The three run modes
Every playbook directory ships the same three files. They are three delivery mechanisms for the
same recipe, not three different recipes.