Systems Lab

Agent skill

clay-column-contract

Define Clay table column names, types, dependencies, and run order before building.

activeSelf-containedInstructions only267 words

Filed under Prospecting and list building.

From rasulshaikh/outbound-skill-pack · 7 skill entries · 0 · pushed 2026-09-29

What it does when it runs

Define Clay table column names, types, dependencies, and run order before building. Use after ICP brief when designing or refactoring an outbound table.

Automated analysis of the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.

Keys and connectors you must supply
None found.
Hosts it reaches
No third-party host appears in the skill or its bundled files.
Tool permissions it declares
No allowed-tools in the frontmatter. It only issues instructions, so there is nothing to bound.
Actions present in the files
None. Instructions only.

Ask about clay-column-contract

Opens your assistant with this page's verified links already in the prompt.

Is this safe to install?ClaudeChatGPT
Adapt it to my stackClaudeChatGPT
What else do I need for it to workClaudeChatGPT
Rather ask a human? Talk to Cheetah
git clone --depth 1 --filter=blob:none --sparse https://github.com/rasulshaikh/outbound-skill-pack.git /tmp/outbound-skill-pack
git -C /tmp/outbound-skill-pack sparse-checkout set "skills/clay-column-contract"
mkdir -p ~/.claude/skills/clay-column-contract
cp -R "/tmp/outbound-skill-pack/skills/clay-column-contract/." ~/.claude/skills/clay-column-contract/

Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗

The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.

Reproduced in full from rasulshaikh/outbound-skill-pack/blob/9516d4bfa03b15648816760032ec8035370ca9f4/skills/clay-column-contract/SKILL.md, which is licensed MIT (repository). 267 words, 9 headings.

Clay Column Contract

Agree on the schema before you click enrich.

When to use

  • New Clay outbound table
  • Refactor of a messy table with duplicate enrichers
  • Hand-off between FDE and operator

Process

  1. List required outputs for the sequencer (email, first name, company, custom fields, sequence tags).
  2. Work backwards: for each output, name the source column and enrichment.
  3. Assign each column:
    • key (stable snake_case name)
    • type (text, number, boolean, url, json)
    • source (manual, formula, enrichment provider, HTTP)
    • depends_on (keys that must exist first)
    • credit_cost (estimate per row, or 0)
    • pii (yes/no)
  4. Order columns into phases: seed → qualify → enrich contact → draft → gate → export.
  5. Call out columns that must stay empty until purple-safety and cost checks pass.

Output format

## Column contract: <table name>

### Phases
1. seed
2. qualify
3. enrich_contact
4. draft
5. gate
6. export

### Columns
| key | phase | type | source | depends_on | credit_cost | pii |
| --- | --- | --- | --- | --- | --- | --- |
| company_domain | seed | text | manual | - | 0 | no |

### Export map
| sequencer field | column key |
| --- | --- |
| email | work_email |

Guardrails

  • No duplicate enrichers for the same field without a documented fallback reason.
  • PII columns need a retention note in the contract footer.
  • Prefer formulas over paid enrichers when the data is already on the row.

Other skills for the same job

Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.

Need help setting it up?

This page tells you what clay-column-contract does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.

Book a call →

The directory stays free. There is nothing gated behind this.