← ClayCONTENT HISTORY
WHAT CHANGED
Update to Clay
Snapshot Nov 18, 2026 · 06:19 UTC · version 2.38.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Clay and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "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 CLI setup skill after its sign-in step. It checks server-side whether this user has been onboarded and stands down if so. Assumes the CLI is already signed in; for access or authentication problems, consult the clay entry skill first.",
"included_files": [
{
"relative_path": "banner-ansi.txt",
"size_in_bytes": 2472
},
{
"relative_path": "banner-narrow-ansi.txt",
"size_in_bytes": 1429
},
{
"relative_path": "banner-narrow.txt",
"size_in_bytes": 468
},
{
"relative_path": "banner.txt",
"size_in_bytes": 1511
}
],
"name": "onboard",
"skill_md_contents": "---\nname: onboard\ndescription: 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 CLI setup skill after its sign-in step. It checks server-side whether this user has been onboarded and stands down if so. Assumes the CLI is already signed in; for access or authentication problems, consult the clay entry skill first.\nallowed-tools: Bash(clay whoami), Bash(command -v jq), Bash(printf '%s\\n' \"${COLUMNS:-0}\"), Read\n---\n\n# Clay onboarding\n\nBefore using this skill, read the `clay` entry skill if you haven’t already this session, and follow its access guidance.\n\nBefore continuing, read the `clay` entry skill and follow its access guidance.\n\nGive a brand-new user a fast first win. Whether this user has already been\nonboarded is tracked server-side, per user: `clay login` and `clay whoami`\nreport it as `onboarded`, and fetching the starter-task options marks them as\nonboarded. There is nothing to record locally.\n\n**This skill runs signed-in.** For access or authentication problems, consult the\n`clay` entry skill before continuing. If CLI access uses an absolute executable\npath, use that path in the examples below.\n\n**The user's own request always wins.** If sign-in was just a prerequisite for\nsomething concrete they asked for (\"get this person's work email\", a table\nquery, a fix for a broken tool), do not run the onboarding menu now — finish\ntheir request; their own task is a better first win than a menu. After it's\ndone, a one-line offer of the starter tasks is fine if it fits the moment.\nSince the options were never fetched, they stay un-onboarded server-side, so a\nfuture login can still make the offer cleanly. Run onboarding immediately only\nwhen there's no concrete task waiting: the user asked to get started, just\ninstalled the plugin, or setup itself was the whole request.\n\nKeep your own prose short — the banner and the starter tasks are the show. The\nwelcome (steps 2–3) goes on screen before you fetch anything; never repeat it\nwithin a session.\n\n## 1. Check that onboarding applies\n\nIf the sign-in that brought you here already reported `onboarded: false`, skip\nthis check and continue. Otherwise read the field yourself:\n\n```bash\nclay whoami\n```\n\n- **`onboarded: false`** — continue to step 2.\n- **`onboarded: true`** — they've been onboarded before (possibly on another\n machine). Stand down: skip the rest of this skill without ceremony. If the\n banner already went up (the Claude Code hook shows it at invocation), a\n one-line welcome back is enough — no pitch, no menu.\n- **The field is absent** — do not infer onboarding status. Consult the `clay` entry\n skill if access needs repair; otherwise stand down.\n\n## 2. Show the banner\n\nOn Claude Code, when this skill was invoked through the Skill tool **and**\n`command -v jq` succeeds, skip this step: a plugin hook displays the banner\nautomatically at that invocation (it needs `jq` to do so) — never print it\nyourself; the step-3 pitch still opens your reply. In every other case — no\n`jq`, any other host, or following this file directly as a runbook (no Skill\ntool call, so no hook fired) — print a banner file from this skill's directory\n**verbatim** inside a fenced code block, before any other tool call\n(`AskUserQuestion` included). Pick the file by terminal width: run\n`printf '%s\\n' \"${COLUMNS:-0}\"` and use `banner.txt` only when it prints a\nnumber of 115 or more; on anything smaller, non-numeric, or a failed probe,\nuse `banner-narrow.txt` — it fits every host. Exception: a number from 1 to\n39 means the pane is too narrow even for the narrow art — show no banner at\nall and go straight to step 3. Do not redraw, trim, or restyle\nthe art. Reading the file is not showing it: the banner must appear in your\nreply to the user.\n\n## 3. Say what Clay is\n\nPosition it as Clay's product and theirs to run (\"Clay lets you…\", \"you can…\"),\nnot as your own abilities. Two or three sentences: Clay is a GTM data and\nautomation platform — search hundreds of millions of people and companies,\nenrich them with verified emails, phone numbers, firmographics, and tech stacks,\nand automate the whole thing with functions and workflows.\n\nThen show the breadth in a compact \"you can ask me to…\" list — four or five\none-line bullets, phrased as plain asks, e.g.: find people or companies matching\na profile, get verified emails for a list, see what technologies a company uses,\nquery and export your existing Clay tables, build a workflow around a webhook,\ncheck your credit balance. No CLI command syntax and no skill names — the user\ntalks to you, not to the CLI. If they ask for the full command surface, show\nthem live `clay --help` output instead of reciting a remembered list.\n\n## 4. Fetch and offer the starter tasks\n\n```bash\nclay onboard options\n```\n\nThis returns the current option set (`{ data: [{ id, label, description }] }`)\nand marks the user as onboarded server-side. **Present exactly what it\nreturns** — the options are server-controlled and may differ from anything you\nremember. If the `AskUserQuestion` tool is available, use it (single-select)\nwith each option's `label` and `description`, and don't add a free-form option\nof your own (\"Type something\", \"Other\") — the tool renders its own escape\nhatch. Without the tool, present a numbered list ending with one extra line:\nthey can also just say what they'd like to do instead.\n\nIf the onboarding operation is unavailable, consult the `clay` entry skill for\naccess guidance. Do not install tools as part of onboarding.\n\nFor any other failure (network, server trouble), don't block and don't\ndiagnose — no error-hunting, no environment debugging, no mention of what went\nwrong. Just ask the user what they'd like to do with Clay and help with that\ndirectly; the rest of this skill doesn't apply.\n\n## 5. Record the selection and run the task\n\nFor an option from the list:\n\n```bash\nclay onboard select <option-id>\n```\n\nThis records the pick and returns `instructions` — follow them as if the user\nhad asked for that task directly. If the independent CLI's directory is not on PATH in this session,\nuse the verified absolute executable path from setup for the selected task too.\n\nIf `select` fails, proceed anyway: treat the option's label as the user's\nrequest — but still get the user's explicit go-ahead before running anything\nthat spends credits; the guidance a successful `select` returns requires that,\nand its absence doesn't waive it. Never block on the recording, diagnose it,\nretry it more than once, or mention it to the user.\n\nIf the user picks something outside the list (e.g. \"Other\"), skip `select` and\njust help with what they asked.\n"
}SHA-256 of public snapshot: 5c8ae6ee8f3094791af2d2cdc884e59ece1321d5bc666e1b4ecad98680f3dc26