clay

Plugin clay from marketplace jarvis-telegram-fork in Hocza-Jozsef-Szabolcs/claude-plugins-telegram-fork. Commands read from the repo's manifest — 1 month ago.

Skills (34)

• 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 pi

• campaigns-interview

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

• campaigns-sequence-reviewing

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

• campaigns-sequence-writing

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

• campaigns

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

• clay-docs

  Use when the user asks a Clay product question — how a feature works, whether Clay supports or integrates with something, what plans include, security/compliance, or what's new — and the answer isn't operational guidance another skill owns. Answer from Clay's live public documentation, fetched and c

• clay-feedback

  Clay feedback — send a bug report or product feedback to the Clay team via the `clay feedback` CLI.

• 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 custo

• cli

  Clay CLI — the primary scripting surface (JSON output, typed errors). Use when running or discovering `clay` commands. For what Clay can do and which skill to use, read the `clay` skill when it is available; otherwise run `clay --help`. Use `clay --help` for command names, flags, JSON shape, and err

• 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.

• onboard

  Clay first-run onboarding — banner, what Clay can do, and starter tasks served by the Clay API. Run this right after a sign-in that just happened — from `clay login` directly, or invoked by the setup skill after its sign-in step. It checks server-side whether this user has been onboarded and stands

• public-api

  Clay Public API — HTTP access for building services, apps, and integrations: GTM database search, structured table queries, and async routine and batch runs.

• 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/stat

• schedules

  GTM Agent schedules — recurring prompts the GTM Agent runs on a cadence, each occurrence starting a fresh agent task. Use for any request to do something on a schedule or recurring cadence: a daily digest, a weekly report, checking or changing when a scheduled run happens next, pausing or deleting o

• 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.

• setup

  Clay setup — install and authenticate the `clay` CLI, which is how the plugin talks to Clay. Use when `clay` is not found on PATH or the `clay` found in the PATH is the wrong version, `clay whoami` fails, the CLI isn't signed in, the Cursor plugin never appears after a local install, or the user wan

• 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

• 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?".

• 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?".

• tables-cli

  Clay tables — inspect, query, and export data from an existing table via the `clay tables` CLI (list, columns, rows, query-live, structured query). To investigate a table or record, use the focused `/tables-*` skills (analyze, trace, error-sweep, value-trace, capacity).

• 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?".

• 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?".

• 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?".

• update

  Keep Clay up to date. Use when the user asks to update or upgrade Clay, the plugin, or the `clay` CLI; when `clay update` reports the CLI is pinned / managed by the plugin; or to check whether a newer version is available. The plugin and CLI update independently; migrate older plugin-managed install

• workflows-audience-enrichment

  Clay workflows — build enrichment steps and map their results back to Audiences in an existing audience enrichment workflow. Use while editing an audience enrichment workflow or migrating an Audience-backed bulk enrichment table into a workflow.

• 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.

• workflows-claygent

  Build and run Claygent agent nodes in Clay workflows. Use when the user asks for custom LLM research, reasoning, classification, drafting, or summarization over records; when no existing routine fits a Claygent task; or when creating or editing a workflow `agent` node.

• 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.

• 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.

• 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.

• 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.

• 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.

• 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

  Clay workflows — plan, review, build, and edit automations with the Clay CLI. Use when planning or working on a Clay workflow.

Hooks (3)

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}"/hooks/approve-cli.sh claude

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}"/hooks/approve-skills.sh claude

• SessionStart

  bash "${CLAUDE_PLUGIN_ROOT}/scripts/check-cli.sh" claude

Similar plugins