luna/marketingskills
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
Files
a10be10a9fdc5e54fe34780a806a66af5cbe37fc
marketingskills/tools/integrations/clay.md
T
Corey Haines 30f9b9a729 feat: v2.0 skill renames and CRO consolidation (#291) 
* feat: v2.0 skill renames and CRO consolidation

BREAKING CHANGE: Users must reinstall skills after this update.

## Skill Renames (16)
- ab-test-setup → ab-testing
- analytics-tracking → analytics
- aso-audit → aso
- competitor-alternatives → competitors
- email-sequence → emails
- free-tool-strategy → free-tools
- launch-strategy → launch
- onboarding-cro → onboarding
- paywall-upgrade-cro → paywalls
- popup-cro → popups
- pricing-strategy → pricing
- product-marketing-context → product-marketing
- referral-program → referrals
- schema-markup → schema
- signup-flow-cro → signup
- social-content → social

## Consolidations (1)
- page-cro + form-cro → cro (form content in references/form.md)

## Why 2.0?
- Shorter, cleaner skill names
- Consistent naming (no -strategy, -setup, -cro suffixes)
- All cross-references updated across 100+ files

Total skills: 40

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* fix(v2.0): update evals for renamed skills, fix validate script, clear warnings

- Update 32 evals.json files to reference new skill names (page-cro → cro,
  product-marketing-context → product-marketing, etc.) — these were missed
  in the initial v2.0 rename pass since only SKILL.md and marketplace.json
  were updated.
- Fix validate-skills.sh: replace GNU-only `head -n -1` with portable awk
  so frontmatter extraction works on macOS.
- Move Copy Editing Checklist (56 lines) to references/checklist.md to
  bring copy-editing SKILL.md under the 500-line limit (508 → 457).
- Add "see X" pointers to marketing-psychology description for skill
  discovery (cro, pricing, copywriting).
- Update skill-request.yml issue template placeholder (page-cro → cro).

All 40 skills now pass validation with zero warnings.

* fix(v2.0): add evals for 8 missing skills, strip stale frontmatter from cro/form.md

Adds 48 new eval cases (6 per skill) for skills that previously had no evals:
aso, co-marketing, community-marketing, competitor-profiling, directory-submissions,
image, lead-magnets, video. All 40 skills now have eval coverage (251 total cases).

Strips leftover frontmatter from skills/cro/references/form.md — it was inherited
from the old form-cro SKILL.md before consolidation. Reference files don't need
frontmatter.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* fix(v2.0): rename paid-ads → ads

One more v2.0 simplification — drops the redundant 'paid-' qualifier. Updates
the skill directory, SKILL.md frontmatter, evals.json, README skill table, the
v2.0 rename table in VERSIONS.md (now 17 renames), and all cross-references in
related skills (ad-creative, aso, competitor-profiling, customer-research,
lead-magnets, marketing-ideas) plus the tools/integrations guides.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* fix(v2.0): bump SKILL.md frontmatter version to 2.0.0 for all 40 skills

VERSIONS.md was already updated to 2.0.0 but the metadata.version field inside
each SKILL.md was still on 1.x. That mismatch would have caused the update-check
flow to perpetually report 'update available' since it compares VERSIONS.md
against local SKILL.md metadata versions.

Caught by codex review (P1).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* fix(v2.0): add legacy product-marketing-context.md filename fallback

Before this fix, users upgrading from v1.x who had a `product-marketing-context.md`
file would lose automatic context loading — every skill only checked the new
`product-marketing.md` filename. Now all 40 skills also accept the legacy
filename (in either `.agents/` or `.claude/`), and the README migration command
covers both legacy and current filenames.

Caught by codex review (P1 + P2).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* fix(v2.0): re-sort README skills table alphabetically, fix ads box width

The skills table had a few entries out of alphabetical order from the renames
(co-marketing was after cold-email, ads was at the renamed position).
Re-sorted alphabetically per sync-skills.js. Also padded the 'ads' cell in the
ASCII flow diagram to keep the box width consistent.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* fix(v2.0): document folder cleanup on upgrade, stop sync-skills from re-adding skills array

README upgrade guide now includes:
- A clear cleanup step for stale v1.x skill folders (renamed + consolidated) so
  users don't end up with both old and new folders side-by-side after upgrading
- The full v1 to v2 rename map for reference
- Existing product-marketing-context.md migration steps (preserved)

sync-skills.js no longer (re-)introduces a `skills` array on marketplace.json --
Claude Code's plugin schema discovers skills via the `skills/` directory, and the
explicit array was failing validation. The script now refreshes the description
count and strips the stale array if present.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
2026-05-13 22:05:15 -07:00

3.2 KiB
Raw Blame History

Clay

Data enrichment and outbound automation platform for building lead lists with waterfall enrichment across 75+ data providers.

Capabilities

Integration Available Notes
API ✓ Tables, People Enrichment, Company Enrichment
MCP ✓ Claude connector
CLI ✓ clay.js
SDK - REST API only

Authentication

  • Type: API Key (Bearer token)
  • Header: Authorization: Bearer {api_key}
  • Get key: Settings > API at https://app.clay.com

Common Agent Operations

List Tables

GET https://api.clay.com/v3/tables

Authorization: Bearer {api_key}

Get Table Details

GET https://api.clay.com/v3/tables/{table_id}

Authorization: Bearer {api_key}

Get Table Rows

GET https://api.clay.com/v3/tables/{table_id}/rows?page=1&per_page=25

Authorization: Bearer {api_key}

Add Row to Table

POST https://api.clay.com/v3/tables/{table_id}/rows

{
  "first_name": "Jane",
  "last_name": "Doe",
  "company": "Acme Inc",
  "email": "jane@acme.com"
}

People Enrichment

POST https://api.clay.com/v3/people/enrich

{
  "email": "jane@acme.com"
}

Company Enrichment

POST https://api.clay.com/v3/companies/enrich

{
  "domain": "acme.com"
}

Key Metrics

Person Data

  • first_name, last_name - Name
  • email - Email address
  • title - Job title
  • linkedin_url - LinkedIn profile
  • company - Company name
  • location - Location
  • seniority - Seniority level

Company Data

  • name - Company name
  • domain - Website domain
  • industry - Industry
  • employee_count - Number of employees
  • revenue - Estimated revenue
  • location - Headquarters location
  • technologies - Tech stack
  • description - Company description

Table Data

  • id - Table ID
  • name - Table name
  • row_count - Number of rows
  • columns - Column definitions
  • created_at - Creation timestamp
  • updated_at - Last update timestamp

Parameters

Tables

  • page - Page number (default: 1)
  • per_page - Results per page (default: 25)

People Enrichment

  • email - Email address
  • linkedin_url - LinkedIn profile URL
  • first_name + last_name - Name-based lookup

Company Enrichment

  • domain - Company domain (e.g., "acme.com")

Add Row

  • Fields are dynamic and match the table's column definitions
  • Pass data as key-value pairs matching column names

When to Use

  • Building enriched prospect lists with waterfall enrichment across multiple providers
  • Enriching leads with person and company data from 75+ sources
  • Automating outbound workflows with enriched data
  • Finding verified contact info (emails, phone numbers, social profiles)
  • Company research and firmographic analysis
  • Triggering enrichment workflows via webhooks
  • Syncing enriched data back to CRM or outbound tools

Rate Limits

  • Rate limits vary by plan
  • Standard: 100 requests/minute
  • Enterprise plans have higher limits
  • Enrichment credits consumed per lookup vary by data provider
  • Webhook endpoints accept data continuously

Relevant Skills

  • cold-email
  • revops
  • sales-enablement
  • competitors
Reference in New Issue View Git Blame Copy Permalink