Terminal
Terminal/Skill
Walks a newly signed-in Clay user through a welcome and a short list of starter tasks, and stands down if they were already onboarded.
By Clay
Works with
npx skills add clay-run/agent-plugins --skill onboardGive a brand-new user a fast first win. Whether this user has already been
onboarded is tracked server-side, per user: clay login and clay whoami
report it as onboarded, and fetching the starter-task options marks them as
onboarded. There is nothing to record locally.
This skill runs signed-in. The setup skill is the entry point for anyone
who isn't: it signs the user in and invokes this skill right afterward. If a
command below fails with an auth error, run setup and stop — it will come
back here when appropriate. If bare clay isn't on PATH this session (a fresh
same-session Claude Code install — setup resolves an absolute launcher path for
this case), use that resolved path in place of clay for every command in this
skill.
The user's own request always wins. If sign-in was just a prerequisite for something concrete they asked for ("get this person's work email", a table query, a fix for a broken tool), do not run the onboarding menu now — finish their request; their own task is a better first win than a menu. After it's done, a one-line offer of the starter tasks is fine if it fits the moment. Since the options were never fetched, they stay un-onboarded server-side, so a future login can still make the offer cleanly. Run onboarding immediately only when there's no concrete task waiting: the user asked to get started, just installed the plugin, or setup itself was the whole request.
Keep your own prose short — the banner and the starter tasks are the show. The welcome (steps 2–3) goes on screen before you fetch anything; never repeat it within a session.
If the sign-in that brought you here already reported onboarded: false, skip
this check and continue. Otherwise read the field yourself:
clay whoami
onboarded: false — continue to step 2.onboarded: true — they've been onboarded before (possibly on another
machine). Stand down: skip the rest of this skill without ceremony. If the
banner already went up (the Claude Code hook shows it at invocation), a
one-line welcome back is enough — no pitch, no menu.clay --version against the plugin's pinned bin/cli-version. If it's
older, run the setup skill with that context — it installs the plugin's
pinned launcher (its step 3) — then re-run clay whoami through that
launcher and read onboarded from there. If the versions match (or the
launcher's whoami still omits the field), the server predates onboarding —
stand down as in the true case.On Claude Code, when this skill was invoked through the Skill tool and
command -v jq succeeds, skip this step: a plugin hook displays the banner
automatically at that invocation (it needs jq to do so) — never print it
yourself; the step-3 pitch still opens your reply. In every other case — no
jq, any other host, or following this file directly as a runbook (no Skill
tool call, so no hook fired) — read banner.txt from this skill's directory
and print its contents verbatim inside a fenced code block, before any
other tool call (AskUserQuestion included). Do not redraw, trim, or restyle
it. Reading the file is not showing it: the banner must appear in your reply
to the user.
Position it as Clay's product and theirs to run ("Clay lets you…", "you can…"), not as your own abilities. Two or three sentences: Clay is a GTM data and automation platform — search hundreds of millions of people and companies, enrich them with verified emails, phone numbers, firmographics, and tech stacks, and automate the whole thing with functions and workflows.
Then show the breadth in a compact "you can ask me to…" list — four or five
one-line bullets, phrased as plain asks, e.g.: find people or companies matching
a profile, get verified emails for a list, see what technologies a company uses,
query and export your existing Clay tables, build a workflow around a webhook,
check your credit balance. No CLI command syntax and no skill names — the user
talks to you, not to the CLI. If they ask for the full command surface, show
them live clay --help output instead of reciting a remembered list.
clay onboard options
This returns the current option set ({ data: [{ id, label, description }] })
and marks the user as onboarded server-side. Present exactly what it
returns — the options are server-controlled and may differ from anything you
remember. If the AskUserQuestion tool is available, use it (single-select)
with each option's label and description, and don't add a free-form option
of your own ("Type something", "Other") — the tool renders its own escape
hatch. Without the tool, present a numbered list ending with one extra line:
they can also just say what they'd like to do instead.
If the command is missing (command not found, or an unknown-command error
naming onboard), the installed CLI predates onboarding. If the setup skill
hasn't already run in this session, run it now with that context — the CLI on
PATH is outdated, so it must install the plugin's pinned launcher (its step 3)
even though sign-in checks pass — then retry clay onboard options once and
continue normally if it works. Retry via the launcher's absolute path when bare
clay still resolves to the old install (no restart needed for that). If setup
already ran or the retry still fails, treat it like any other failure below.
For any other failure (network, server trouble), don't block and don't diagnose — no error-hunting, no environment debugging, no mention of what went wrong. Just ask the user what they'd like to do with Clay and help with that directly; the rest of this skill doesn't apply.
For an option from the list:
clay onboard select <option-id>
This records the pick and returns instructions — follow them as if the user
had asked for that task directly. If those instructions name the workflows
skill or MCP tools (read / edit_node / validate_workflow), use the
workflows-cli skill and clay workflows … instead — the plugin withholds
workflows and never gets those MCP tools, so do not wait for a restart that
would surface them. If a CLI command isn't on PATH this
session (setup step 3 deferred a restart so the forwarder is visible), walk
them through that restart and tell them to ask for the task again by name once
they're back (e.g. "set up the webhook starter") — a fresh session won't
remember this conversation, so the task name is what carries it over.
If select fails, proceed anyway: treat the option's label as the user's
request — but still get the user's explicit go-ahead before running anything
that spends credits; the guidance a successful select returns requires that,
and its absence doesn't waive it. Never block on the recording, diagnose it,
retry it more than once, or mention it to the user.
If the user picks something outside the list (e.g. "Other"), skip select and
just help with what they asked.