clay-table-design
Skill0 starsChanged 48 days agoMITView on GitHub
Design Clay tables that stay small, auditable, and enrichment-efficient. Starting a new workbook, adding a signal intake table, or rebuilding a messy contact table.
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- competitor-teardownSkill
- deploy-surface-checkSkill
- fde-handoff-packSkill
- hermes-herdr-loopSkill
- icp-scorecardSkill
- jev-typesafe-briefSkill
- n8n-flow-scaffoldSkill
- signal-to-sequenceSkill
- trigger-job-patternSkill
- weekly-pipeline-pulseSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Add a qa_status and last_enriched_at column.
- Very specific: line 16
Document formulas in ops/<slug>/enrichment/schema.md so git can track intent.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill: clay-table-design
Design Clay tables that stay small, auditable, and enrichment-efficient.
When to use
Starting a new workbook, adding a signal intake table, or rebuilding a messy contact table.
Steps
- Name the table by job (
signals_intake,accounts_core,contacts_persona). - Define primary key (usually domain or LinkedIn URL). Prefer one identity column.
- Split firmographics, contacts, and scoring into separate tables linked by domain.
- For each enrichment column: source, cost sensitivity, null policy, refresh cadence.
- Add a
qa_statusandlast_enriched_atcolumn. - Document formulas in
ops/<slug>/enrichment/schema.mdso git can track intent.
Anti-patterns
- One mega-table with 80 columns
- Enriching every row daily without a trigger
- Storing API keys in Clay cells
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

