メニュー
Use Clay for lead enrichment, prospecting, and GTM workflows. Use when finding leads, enriching companies or people, pushing data to Clay tables, or running outreach workflows. Clay is the primary enrichment platform for bracos.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | clay |
| description | Use Clay for lead enrichment, prospecting, and GTM workflows. Use when finding leads, enriching companies or people, pushing data to Clay tables, or running outreach workflows. Clay is the primary enrichment platform for bracos. |
| metadata | {"author":"dandaka","version":"1.2"} |
| allowed-tools | Bash(infisical*), Bash(agent-browser*), Bash(curl*), Bash(sleep*), Read, Write, Edit |
Clay is the enrichment and GTM automation platform for bracos.
| Approach | When | Env |
|---|---|---|
| MCP (this session) | Small batches, lookups, research (≤20 results) | Claude.ai web only |
| Webhooks | Push data into a table for bulk enrichment | Any (remote OK) |
| Browser automation | Create tables, export, configure workflows | Local only |
Clay is connected to this Claude.ai account. Just ask naturally — no special syntax needed. Clay is invoked automatically based on context.
Find people at a company
Find property managers at imovirtual.pt
Find cleaning company owners in Lisbon, Portugal
Find operations managers at real estate agencies in Porto
Find VP-level contacts at airbnb.com who work in Portugal
Enrich a contact (returns: email, phone, LinkedIn, work history, thought leadership)
Find the email and LinkedIn for João Silva at limpezaslisboa.pt
Enrich the top 3 results with verified email and work history
Company research (returns: hiring trends, funding, tech stack, headcount, recent news)
Research oscar.pt — what are they building, who are their key hires?
Compare hiring trends at fixando.pt and zaask.pt
What is fixando.pt's revenue model and headcount?
Meeting prep / contact brief
I have a call with Ana Pereira at cleaningco.pt tomorrow. Give me a brief with background and 3 talking points.
Search broadly → filter → enrich only what matters:
1. Find operations managers at property management companies in Lisbon
2. Filter to decision-makers (manager level and above)
3. Enrich the top 5 with verified email and LinkedIn
Every Clay table can expose a webhook. Use this for bulk enrichment from any environment.
Setup (one-time, in browser): Table → Actions → View all sources → Webhook → copy URL
Push rows:
curl -s -X POST "https://api.clay.com/v3/sources/<webhook-id>/events" \
-H "Content-Type: application/json" \
-d '{"rows": [{"company": "Acme", "domain": "acme.pt"}, ...]}'
Clay enriches each row using pre-configured columns and consumes credits. Use an HTTP action column to push results back out (Postgres, CSV, etc.).
Credentials:
infisical run --env=dev --path=/bracos -- bash -c '
echo "Workspace: $CLAY_WORKSPACE_ID"
echo "Starter table: $CLAY_TABLE_STARTER"
echo "VC leads table: $CLAY_TABLE_VC_LEADS"
'
Chrome Beta on port 9223:
infisical run --env=dev --path=/bracos -- bash -c '
SESSION=$(LC_ALL=C tr -dc "a-z0-9" < /dev/urandom | head -c 6)
agent-browser --cdp 9223 --session "$SESSION" open "https://app.clay.com/workspaces/$CLAY_WORKSPACE_ID/home"
sleep 3
agent-browser --cdp 9223 --session "$SESSION" snapshot -i
'
Sculptor (AI table builder): Sidebar → Sculptor → describe in plain English what you need built.
Export: Open table → export button → CSV.
| Action | Credits |
|---|---|
| Enrich person (LinkedIn + work history) | ~2 |
| Find work email (waterfall) | ~3 |
| Validate email | ~1 |
| Enrich company | ~1–2 |
| MCP search (per search) | ~1–5 |
~400–500 fully enriched contacts per 2,000 credits in tables. MCP has a separate 1,000 credit/month cap.
Property managers, Airbnb/VRBO hosts, cleaning company owners in Lisbon/Porto — repeat buyers, high LTV.
Via MCP (quick lookup):
Find property management companies in Lisbon, Portugal.
Enrich the top 10 with decision-maker name, verified email, and company size.
Via tables (bulk, for full campaign):
Evidence-based frontend development protocol for matching a Figma source of truth to browser-rendered pixels. Ensures the project has docs/frontend-protocol.md (preflight harness checks, intent intake, measure→causal-chain→live-experiment→commit debugging modes), docs/design-vocabulary.md (shared industry design terms), and scripts/preflight.sh. Use this skill whenever the user asks to set up frontend standards, debug a layout issue, match a design or Figma artboard ("layout is off", "doesn't match the design", "pixel-perfect"), review frontend debugging practice, or when starting frontend work in a project that lacks these docs.
Ensure the current project has a docs/coding-standards.md checklist and use it to review code against the default stack (Bun, TypeScript, Drizzle, Biome, Bun-workspaces monorepo, red/green TDD) and quality principles — tidiness, separation of concerns, maintainability, stale assumptions, leftover experimental code, and doc drift. Use this skill whenever the user asks to check coding standards, review code quality, "is this tidy", "does this follow our standards", set up a coding standards doc, scaffold a new project's conventions, or before finishing/merging a change.
Interview the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.
Figma automation via the figma-use CLI (by dannote). Use when the user needs to create, modify, or inspect Figma designs programmatically. Triggers on requests to render components in Figma, sync design tokens, query or find nodes, export assets, manage variables/pages, compose screens from component instances, delta-sync web app CSS against Figma properties, or troubleshoot Figma CDP connections. Also triggers on mentions of "figma-use", "figma automation", "figma cli", "render to figma", "figma eval", or "design system sync". Never use computer-use (screenshot/click) for Figma — always use figma-use CLI.
Switch to Claude Opus 4.6 model
Fetch articles and save them to a local reading buffer, or compile all unsent articles into a Kindle-optimized PDF digest and email it to Kindle. Use when the user provides URLs to save for reading, or says "send" / "send to kindle" to compile and dispatch the digest.