Update to Kapa

{
  "description": "Set up a Kapa GitHub issues source so repository issues are ingested. Use when the user wants Kapa to answer from problems and solutions discussed in GitHub issues.",
  "included_files": [],
  "name": "kapa-setup-github-issues",
  "skill_md_contents": "---\nname: kapa-setup-github-issues\ndescription: Set up a Kapa GitHub issues source so repository issues are ingested. Use when the user wants Kapa to answer from problems and solutions discussed in GitHub issues.\n---\n\n# Set up GitHub issues\n\n## 1. Create the source\n\n`create_github_issues_source` with `project` and `name`. Keep the returned id.\n\n## 2. Configure it\n\n`set_github_issues_config` with `source_github_issues`, `repo_owner` and\n`repo_name`.\n\n`repo_owner` and `repo_name` together make the repository path. For\n`github.com/acme/docs`, the owner is `acme` and the name is `docs`.\n\n`personal_access_token` is **required only for a private repository**. Do not\nask for one for a public repo. If you do need it, it is the user's secret: ask,\nnever invent one, and tell them it needs the `repo` scope.\n\n## Check the repository first\n\n`validate_github_issues_repo` with `repo_owner`, `repo_name` and, for a private repo,\n`personal_access_token`. It answers HTTP 200 with `false` when the repo cannot\nbe reached, so read the body rather than the status.\n\nA false covers all of: the repo does not exist, it is private and the token is\nmissing, or the token lacks the `repo` scope. Offer those to the user rather\nthan guessing which.\n\n`list_github_issues_labels` then shows the repository's labels.\n\n## Let the user choose the filters\n\nShow these options and ask. Do not pick for them and do not apply a default\nsilently: what belongs in a knowledge base differs per team.\n\n- `issue_state`: open, closed, or all. Closed issues carry resolutions, open\n  ones carry live problems.\n- `issue_age`: how far back to read, or all history.\n- `labels`: restrict to specific labels, or leave out for every label.\n\nSay what each does, then set what they asked for.\n\n## What it is good for\n\nIssues answer \"has someone hit this before\". For \"how does this work\", use\nGitHub files against the docs instead.\n\n## Finish the job\n\nSaving the configuration starts ingestion. There is no separate publish step.\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"
}