Update to Kapa

{
  "description": "Set up a Kapa custom question and answer source so hand-written answers are ingested. Use when the user wants to write answers directly for questions their documentation does not cover.",
  "included_files": [],
  "name": "kapa-setup-custom-qa",
  "skill_md_contents": "---\nname: kapa-setup-custom-qa\ndescription: Set up a Kapa custom question and answer source so hand-written answers are ingested. Use when the user wants to write answers directly for questions their documentation does not cover.\n---\n\n# Set up custom answers\n\nThe one source the user writes themselves. Use it when an answer exists nowhere\nelse, or when Kapa keeps getting something wrong and they want to correct it\ndirectly.\n\n## 1. Create the source\n\n`create_custom_qa_source` with `project` and `name`. Keep the returned id.\n\n## 2. Add the pairs\n\n`add_custom_qa_pair` with `custom_qa_source`, `question` and `answer`. **Call it\nonce per pair**; there is no batch call.\n\nConfirm the full list with the user before you start, then add them one at a\ntime.\n\n## Writing them well\n\n- Write the `question` the way a user would actually ask it, not as a heading.\n  \"How do I rotate an API key?\" rather than \"API key rotation\".\n- The `answer` takes Markdown.\n- The same question text cannot be added twice to one source.\n\n## After adding\n\nEach pair ingests as it is added, so there is no separate publish step.\n\n## Finish the job\n\nSaving the configuration starts ingestion. There is no separate publish step,\nso once the config saves the source is live.\n\nThen call `list_sources` with `project_id` to confirm what the project holds.\n\n## Shared Kapa workflow rules\n\nTools act as the connected user with that user's project permissions. Resolve the intended project and use only authorized data. Do not invent credentials, source IDs, filters, or tool results. Check the available tool schema before passing arguments.\n\nExplain and obtain approval for ingestion and its quota cost before saving a configuration that starts ingestion or calling `start_crawl`; existing explicit approval for that exact action is sufficient. Ask the user to choose source scope and filters. Validate credentials and discover accessible content before saving. Keep credentials out of visible results, logs, and exported artifacts. Use a secure credential input if the host provides one.\n\nFor a web source, preview the exact configuration and inspect the extracted article content before ingestion. Report queued, running, failed, and completed states accurately. If uncertain about Kapa behavior, use `search_kapa_docs` when available.\n"
}