菜单
Use the local kagi-cli for Kagi search, news, smallweb, quick answers, assistant, translate, and subscriber summarization. Trigger when asked to use Kagi or kagi-cli.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Teaching-assistant mode for hint-first help, conceptual explanations, debugging guidance, and code review without defaulting to full solutions. Use when the user wants to learn, be coached, or get guided help instead of direct code generation.
Documentation-driven development using Air - a filesystem-based planning tool. Use when working with Air documents, managing project specifications, tracking implementation progress, or when the user mentions Air, airctl commands, or documentation-driven development workflows.
Navigate and modify Nix-based dotfiles with flakes and home-manager. Use when working with nix configs, finding where settings live, or understanding the repository structure.
Create or update Pi skills (SKILL.md plus optional scripts, references, or assets). Use when someone asks to design a new Pi skill, refine an existing one, or structure skills for Pi discovery or packaging.
Guide for extending Pi — decide between skills, extensions, prompt templates, themes, context files, or custom models, then create and package them. Use when someone wants to extend Pi, add capabilities, create a skill, build an extension, or make a Pi package.
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
| name | kagi |
| description | Use the local kagi-cli for Kagi search, news, smallweb, quick answers, assistant, translate, and subscriber summarization. Trigger when asked to use Kagi or kagi-cli. |
Use the installed kagi command.
Authentication is managed by kagi-cli itself, usually via local ./.kagi.toml created by:
kagi auth
Do not print or inspect .kagi.toml; it may contain a session token. This repo ignores .kagi.toml so it should not be committed.
These commands use public endpoints or the Kagi subscriber/session path rather than API credits:
kagi news
kagi smallweb
kagi search "query"
kagi quick "question"
kagi assistant "prompt"
kagi translate "text" --to Korean
kagi summarize --subscriber --url https://example.com
Avoid these unless the user explicitly asks to use Kagi API credits/billing:
kagi extract ...
kagi fastgpt ...
kagi enrich ...
kagi summarize ... # without --subscriber
If auth fails, suggest running:
kagi auth status
kagi auth