clay-run/agent-plugins

24 skill entries

• audiences

  Clay Audiences — the workspace's own people, companies, and deals (contacts, leads, accounts, customers). Use for any request about their records when no surface is named, including counts, fill rates, lookups ("how many people have a phone?"), saved segments, and field definitions. Also deal and pipeline questions like largest opportunities, biggest pipeline items, recent wins, closed-won, deal stage, and ACV.

  Self-containedActs undeclared2,973 words
• campaigns

  Inspect, create, compare, analyze, and edit Clay Campaigns or Sequencer campaigns through the clay CLI.

  Self-containedActs undeclared3,339 words
• campaigns-interview

  Use when a fresh Clay Sequencer campaign has no meaningful subject or body copy and needs its first draft.

  Self-containedInstructions only435 words
• campaigns-sequence-reviewing

  Review Clay Sequencer copy as the intended recipient and identify only material, actionable objections.

  Self-containedInstructions only356 words
• campaigns-sequence-writing

  Draft and revise complete Clay Sequencer email sequences using supplied campaign strategy and context.

  Self-containedInstructions only347 words
• clay

  Clay — start here. A table of contents for working with Clay and which skill to use for each thing — audiences (the workspace's own people/companies/deals), campaigns (create, improve, and analyze outbound email sequences), search (find net-new people/companies), routines (run Clay-managed and custom functions), tables (query/export data), the CLI (ephemeral programmatic access), the Public API (build services on Clay), workflows (build automations), and feedback. Read this first to answer "what can I do with Clay?

  Self-containedInstructions only1,553 words
• credits-quotas-plans

  Use when the user asks about credits, quotas, or plan limits, or verified usage requires a significant-spend warning or reveals a limit. Covers data-credit balance, action-execution balance, search result caps, period quotas, and upgrade paths before starting work that would only partially complete.

  Reaches the webActs undeclared776 words
• routines

  Clay routines — create a routine from an existing function/workflow, then run a saved routine that exists in this workspace. Use when the user asks to create/register a routine, or to run, execute, or trigger a function, workflow, or routine (by name or id), pass it inputs, or check the results/status of a run. For building a new workflow, use the workflows entry-point skill instead.

  Reaches the webActs undeclared1,481 words
• searches

  Clay search — find people or companies in Clay's GTM database with advanced queries and page through the matches. Use when the user wants to search Clay for prospects/accounts, not query an existing table.

  Reaches the webDeclared tools1,655 words
• signals

  Clay Signals — watches that detect real-world changes (job changes, new hires, promotions, funding news, job postings, topic intent) and write them as events onto a table or an audience. Use for any request about a workspace''s signals: which ones exist, what one watches or writes to, whether one is running, turning one on or off, and why one is or is not producing events.

  Self-containedActs undeclared5,301 words
• tables-analyze

  Clay tables — analyze what a table does: reconstruct the column DAG, stage it, and narrate the workflow encoded in its columns. Use when the user asks "what does this table do?", "explain the {table} workflow", "walk me through this table", or "what''s set up here?".

  Self-containedDeclared tools986 words
• tables-capacity

  Clay tables — check the row-capacity ceiling when imports stall, before assuming a run/config/enrichment problem. Use when the user asks "why aren't new rows being added?", "why is the import stuck?", or "is this table full?".

  Self-containedDeclared tools840 words
• tables-error-sweep

  Clay tables — sweep a table for errored rows and report grouped by root cause (not a specific record). Use when the user asks "what's erroring in {table}?", "show failed rows", or "is {action} failing?".

  Self-containedDeclared tools1,394 words
• tables-trace

  Clay tables — locate a record by identifier and snapshot its state: which table(s) hold it and each cell''s status. Use when the user has an id and asks "trace {id}", "where is {id}?", "what enrichments ran for this lead?", or "is this record done?".

  Self-containedDeclared tools1,016 words
• tables-value-trace

  Clay tables — explain one cell by walking a column backward through its dependencies and run-gate to the origin or root cause. Use when the user asks "where did this value come from?", "why did {action} error?", "why didn't {action} run?", or "why is this value empty?".

  Self-containedDeclared tools1,031 words
• workflows

  Clay workflows — build and edit automations with `clay workflows nodes/graph/groups/actions/code/triggers` (CLI). Use when building or editing Clay workflows.

  Self-containedActs undeclared3,934 words
• workflows-audience-enrichment

  Clay workflows — build enrichment steps and map their results back to Audiences in an existing audience enrichment workflow. Use only while editing a workflow whose `clay workflows get` output has type `audience_enrichment`.

  Self-containedDeclared tools668 words
• workflows-campaign-enrollment

  Enrol Audiences people into a Clay campaign from a workflow step, using the "Enroll in campaign" action (`enroll-lead-in-sequence`). Use when a workflow should start emailing the people it just processed.

  Self-containedActs undeclared1,205 words
• workflows-discover-actions

  Clay workflows — discover available actions for workflow nodes (email lookup, company enrichment, phone finders, etc.) and inspect their input and output schemas. Use while building a workflow.

  Self-containedDeclared tools1,721 words
• workflows-inbound-lead-routing

  Guide customers through building an inbound lead-routing workflow in Clay Workflows. Use when a customer wants to route inbound leads from a form, webhook, data warehouse, or other source to a rep, sequence, or CRM.

  Self-containedInstructions only1,132 words
• workflows-optimize-credits

  Clay workflows — reduce a workflow's credit and LLM cost via the CLI (`clay workflows` commands). Identifies expensive patterns and suggests cheaper alternatives.

  Self-containedInstructions only741 words
• workflows-simplify

  Clay workflows — simplify a workflow via the CLI (`clay workflows` commands): merge redundant nodes, cut unnecessary complexity, and replace LLM nodes with deterministic alternatives where possible.

  Self-containedInstructions only594 words
• workflows-snapshots

  Clay workflows — version history: view snapshots, see what changed, and restore or undo a previous state. Use when the user mentions snapshots or asks to undo an edit.

  Self-containedDeclared tools1,691 words
• workflows-vs-tables

  Clay Workflows vs Tables — conceptual explainer for a customer asking what the difference is or which one to use. Read this when explaining the two products or recommending one for a use case. Users cannot build tables via the CLI/API; if a task needs a new table, surface that to the user & explain workflows are the only way to build in via CLI/API today.

  Self-containedInstructions only726 words