What is clay-playbooks?

A collection of 19 workflows for finding specific buying signals, such as a new employee, recent funding, hiring growth, or a technology used on a website. Each workflow turns one signal into a sentence that can be added to a cold email, with options for one-off, table-based, or command-line use.

Use it to add signal-based lines to outreach, such as mentioning a funding event or pricing page, and to build those checks into Clay tables or version-controlled workflows.

It replaces vague personalization with one consistent piece of evidence for each lead. It also gives teams a defined way to run the same signal manually or repeatedly in a data table.

clay-playbooks — Skill by growthenginenowoslawski/coldoutboundskills

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add growthenginenowoslawski/coldoutboundskills --skill clay-playbooks

Clone the repo

git clone --depth 1 https://github.com/growthenginenowoslawski/coldoutboundskills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/growthenginenowoslawski/coldoutboundskills/clay-playbooks/github.svg)](https://agentmods.dev/skills/growthenginenowoslawski/coldoutboundskills/clay-playbooks)

Your own site

<a href="https://agentmods.dev/skills/growthenginenowoslawski/coldoutboundskills/clay-playbooks"><img src="https://agentmods.dev/badge/skills/growthenginenowoslawski/coldoutboundskills/clay-playbooks/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/growthenginenowoslawski/coldoutboundskills/clay-playbooks"><img src="https://agentmods.dev/badge/skills/growthenginenowoslawski/coldoutboundskills/clay-playbooks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,202 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.02202
Opus 5.5	$0.00000	$0.00881
Sonnet 5.5	$0.00000	$0.00440
Haiku 4.5	$0.00000	$0.00220

Measured 2mo ago against content hash fbdba57b6c89, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

clay-playbooks scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/playbooks/clay-playbooks/SKILL.md · 146 lines

How it starts

The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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.

File	What it is	Use it when
`SKILL.md`	The playbook itself: source chain, output contract, locked prompt, edge cases	You are running the signal from Claude, ad hoc, on a CSV or a one-off list
`clay-table.md`	The Clay table build: exact columns, types, formulas, credit gates, AI-column bindings	The signal needs to run continuously on a client table that other people will look at
`clay-workflow.md`	The Clay workflow build via the `clay` CLI: node graph, real action keys, publish and run	You want the signal version-controlled and buildable from a terminal, no UI clicking

Why tables are browser-driven and workflows are CLI-driven. This is a real constraint, not a style choice. The clay CLI's tables command group is read-only (list, get, columns, rows, query) — it cannot create a table or add a column. Tables must be built in the UI. Workflows are the opposite: clay workflows create / nodes create / publish / runs test all exist, so a workflow can be built end to end from a terminal.

Shared procedures, written once so the 19 playbooks do not repeat them:

clay-table-harness.md — the generic browser procedure for building any playbook's table.
clay-cli-harness.md — the generic clay CLI procedure for building any playbook's workflow.

Read the relevant harness once, then read the playbook's own clay-table.md / clay-workflow.md for what is specific to that signal.

Read the full file on GitHub · 146 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 146 lines · 0 tokens per session scan A fbdba57b6c89

Subscribe to this mod's changes

clay-playbooks is a skill published in the GitHub repository growthenginenowoslawski/coldoutboundskills (802 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,202 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Marketing and SEO Research

clay-playbooks next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
clay-playbooksgrowthenginenowoslawski/coldoutboundskills	Skill	802	1mo ago	MIT	A	0	Claude Code, Codex
imagegenopenai/codex	Skill	133k	today	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	today	MIT	A	95	Claude Code
chat-pet-sprite-creationmicrosoft/vscode	Skill	195k	today	MIT	A	53	Claude Code, Codex