Update to Kairon

{
  "description": "Define who a team sells to, as an ideal customer profile (ICP). Use when someone says who their ideal customer is, wants to describe their target market, or wants to decide who counts as a good lead.",
  "included_files": [],
  "name": "define-your-icp",
  "skill_md_contents": "---\nname: define-your-icp\ndescription: Define who a team sells to, as an ideal customer profile (ICP). Use when someone says who their ideal customer is, wants to describe their target market, or wants to decide who counts as a good lead.\n---\n\n# Define an ideal customer profile (ICP)\n\nAn ICP says who is worth contacting: the companies, and the people inside them. It has two\nparts, and they do different jobs.\n\n- **Filters** carve out a broad group to search: places, job titles, industry, company size.\n- **Checks** are the real test. Each check is one yes/no question about one public fact.\n\n## Rules\n\n- **One ICP at a time.** If the person describes several buyers, help them pick the sharpest one\n  first. The others can come later.\n- **A check asks ONE thing, in at most 250 characters.** If it has an \"and\", a list of\n  exceptions, or two ideas, make it two checks. Most good checks are under 100 characters.\n- **A check must be answerable from public information.** \"Is a B2B software company\" works.\n  \"Owns the tooling budget\" does not: nobody publishes it. If a person with only public pages\n  could not answer it, do not write it.\n- **Translate a pain, never restate it.** If the person says \"they have no CRM\", ask: what is\n  publicly true of a company that has this pain? Write that.\n- **Write it so \"yes\" is good:** \"is an architecture studio, not a staffing firm\".\n- **Places, job titles, industry and size go in the filters, not in a check.** The same for lists\n  of companies to avoid.\n- **Do not use dates or sums in a check.** Ask about the fact itself.\n\n## Steps\n\n1. Ask what they sell and who bought best. Look up what you can before you ask, starting with\n   `workspace_profile_get`, which holds what the workspace has already said about its offer. Ask\n   only what you cannot find. Save a better answer with `workspace_profile_update` once the\n   person agrees; it replaces that whole section.\n2. Propose a place first, then ask them to confirm it. Set only what they confirm, and say it\n   back in plain words.\n3. Create the ICP with `icp_create`. It is a **draft**: nothing can use it yet. Show the person\n   the filters and each check in plain words.\n4. Change it with `icp_update`. Send only the fields that change. Rewrite or split the ONE check\n   that decided a case. Never add an exception to an existing check; a new rule is a new check.\n5. Look at `icp_get` to see what publishing would change.\n6. **Ask before `icp_publish`.** Publishing makes this ICP decide who counts as a fit, and it can\n   use the workspace balance for re-checks. Say that, then wait for a yes.\n7. After it is live, go to the `qualify-a-list` skill to test it on a few people.\n\n## How to know it is good\n\nA good ICP, tested on ten people who should fit, passes about six in ten. If most people come\nback \"not sure\", a check asks for something nobody publishes: rewrite it. If the list is full of\nthe wrong kind of company, the search is too wide, not the ICP.\n\nSay what you changed and why, so the person can disagree with the reasoning.\n"
}