{"id":103317,"plugin_id":"plugin_asdk_app_6aedf6ea2fac819180910f8b98663c77","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-18T06:19:20.421Z","digest":"acdfb1956eef23f995d4a239dffe43b3f5a27d854d61f8509fbb9c7c14ca0ea6","against":null,"payload":{"description":"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 cited, never from memory.","included_files":[],"name":"clay-docs","skill_md_contents":"---\nname: clay-docs\nallowed-tools: WebFetch(domain:www.clay.com), WebFetch(domain:university.clay.com), WebFetch(domain:trust.clay.com), WebFetch(domain:developers.clay.com)\ndescription: 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 cited, never from memory.\n---\n\n# Clay product documentation\n\nBefore using this skill, read the `clay` entry skill if you haven’t already this session, and follow its access guidance.\n\nClay's public documentation is the source of truth for product questions. Your training\ndata about Clay is stale and incomplete: features ship weekly, integrations are added\nand renamed, and plans change. Answering a Clay product question from memory risks\ntelling the user something that is no longer true, or denying something that now exists.\n\n**The rule: fetch a live doc page, answer from what it says, and cite its URL.** If you\ncannot find the answer in the docs, say so plainly — \"I couldn't find this documented\".\nNever fill the gap by guessing.\n\n## Not this skill\n\n- **Doing things** (run a search, query a table, build a workflow) — use the area skill\n  (`searches`, `tables-cli`, `workflows`, …). This skill answers questions, it does not\n  operate Clay.\n- **Live workspace state** — credit balances, quotas, plan limits in effect for this\n  workspace: use `credits-quotas-plans`. This skill covers what plans and pricing _are_\n  publicly, not what this workspace has.\n- **Upgrading or changing a plan** — use `credits-quotas-plans` for the workspace’s\n  direct plan-selector link, including when the user still has credits.\n- **API and CLI reference** — endpoints, schemas, flags: the `public-api` and `cli`\n  skills point at <https://developers.clay.com/llms.txt>.\n- **Something looks broken** — use `clay-feedback`.\n\n## Docs map\n\nStart from the most specific hub that matches the question:\n\n| Question is about                                                            | Fetch                                                                         |\n| ---------------------------------------------------------------------------- | ----------------------------------------------------------------------------- |\n| How a feature works (find, enrich, transform, scraping, AI, export, signals) | <https://university.clay.com/docs> — the product docs hub, organized by topic |\n| Whether Clay integrates with a specific tool                                 | <https://www.clay.com/integrations> — the catalog; tool pages hang off it     |\n| Plans and pricing                                                            | <https://www.clay.com/pricing>                                                |\n| Common product questions                                                     | <https://www.clay.com/faq>                                                    |\n| GTM tactics and playbooks built on Clay                                      | <https://www.clay.com/claybooks>                                              |\n| Prebuilt table templates                                                     | <https://www.clay.com/templates>                                              |\n| What a GTM term means                                                        | <https://www.clay.com/glossary>                                               |\n| What shipped recently                                                        | <https://www.clay.com/changelog>                                              |\n| Security, compliance, subprocessors                                          | <https://trust.clay.com>                                                      |\n| Structured learning (courses, lessons, certifications)                       | <https://university.clay.com/courses>                                         |\n| End-to-end use-case walkthroughs                                             | <https://university.clay.com/use-case-templates>                              |\n\n## Finding the right page\n\n1. Pick the closest hub from the map and fetch it with your web fetch tool. Hubs link\n   to their leaf pages; follow the link that matches the question and fetch that. One\n   caveat: the University docs hub leans toward per-integration reference pages, while\n   conceptual \"how does X work\" content (waterfalls, credits, signal types) lives in\n   lessons at `university.clay.com/lessons/<slug>` — when the hub surfaces only\n   integration pages, go to the sitemap (step 3) instead of digging deeper.\n2. For an integration, fetch the catalog and follow its link for the tool. Tool pages\n   live at `/integrations/<category>/<slug>` and the category is not guessable, so do\n   not construct URLs by hand — and a 404 on a guessed URL does not mean unsupported.\n3. Find lessons through <https://university.clay.com/sitemap.xml>. It is large enough\n   that a summarizing fetch tool can silently miss entries, so when you have a shell,\n   grep a raw fetch instead: `curl -sL <sitemap-url> | grep -i <keyword>`. Skip `/fr/`\n   entries — they are French duplicates.\n4. When hub navigation dead-ends or a page you expected is missing, use web search\n   scoped to the docs (`site:university.clay.com` or `site:www.clay.com`) to locate a page,\n   then fetch it. Never answer from a search snippet alone.\n\nIf your environment has no web fetch tool, fetch with `curl -sL <url>` instead. If you\ncannot fetch at all, say you can't verify against the docs and link the user to the\nrelevant hub URL rather than answering from memory.\n\n## Answering\n\n- Cite the page URL with every answer so the user can read the source.\n- Report what the page says, in its terms. Do not extrapolate a capability the page\n  does not state, and do not present an inference as documented fact.\n- Pricing: state numbers only from a page fetched this session, and say plans change —\n  link <https://www.clay.com/pricing> as the current source. The page's interactive\n  tier sliders flatten badly into fetched markdown, so present dollar figures as\n  \"starts at\" rather than exact.\n- University `/docs/...` pages are product reference; `/lessons/...` and claybooks are\n  educational content that can lag or generalize. When they disagree, report both with\n  their sources instead of picking one.\n- A capability you cannot find documented is \"not documented\", not \"not supported\" —\n  unless a page says it is unsupported. Say what you checked, and don't volunteer a\n  support handoff for a capability gap — the `clay` skill's escalation rules say when\n  support enters.\n\n## Known unsupported\n\nClay does not offer X (formerly Twitter) data sourcing, scraping, or enrichment — no\nfollower lists, profile data, posts, or mentions. Say so directly — this answer needs\nno fetch and no citation, and it overrides the fetch-first rule. Do not search the\ndocs for a workaround.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}