kagi-ai
Skill190 starsChanged 8 months agoMITView on GitHub
Use Kagi's paid AI allowance for reasoning, coding, research, file analysis, structured generation, or model comparison. Use when a task should spend Assistant value instead of only searching the web or transforming one known page.
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 7 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 37
Use only model slugs and assistant names returned by the account.
- Distinctive: line 44
Use a closed model call for reasoning that needs no current information:
- Distinctive: line 93
Use a built-in contract for reusable decisions, plans, and checklists:
- Very specific: line 102
Use --contract-file PATH when the consumer needs a different small JSON shape.
- Distinctive: line 107
Use subscriber Summarizer or Translate for direct transformations when the active plan includes them.
- Distinctive: line 109
Use the account default or a lower-cost model for simple work.
- Distinctive: line 111
Keep prompts specific and attach only relevant files.
- Distinctive: line 112
Start a new thread for an unrelated task.
- Distinctive: line 121
every explicit model or assistant came from live account discovery.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Kagi AI
Spend the Assistant allowance on reasoning and synthesis. When the active plan includes unlimited Summarizer or Translate usage, use those tools for direct transformations and reserve the allowance for harder work.
Choose the lane
| Need | Lane |
| Find or verify sources | Load kagi-usage and search |
| Summarize one URL or text | kagi summarize --subscriber |
| Translate supplied text | kagi translate |
| Get a fast cited answer | kagi quick |
| Reason, code, synthesize, or analyze files | kagi assistant |
| Run multi-step research or tool use | An account-visible Research assistant |
| Manage threads or custom assistants | Load kagi-assistant |
The Assistant allowance is separate from API credit. A plan's monthly value sets its token allowance across Assistant models. Premium models, web access, large files, and long thread histories consume more of that allowance.
Start with live account state
kagi auth status
kagi assistant models
kagi assistant custom listUse only model slugs and assistant names returned by the account. When the
model catalog is empty, use the account default instead of guessing a slug.
Kagi Quick and Kagi Research are usable through --assistant only when they
appear in the assistant listing.
Use Assistant deliberately
Use a closed model call for reasoning that needs no current information:
kagi assistant \
"find the weakest assumption in this design and propose a simpler one" \
--no-web-access \
--format markdownEnable web access when the answer needs current sources:
kagi assistant \
"compare these database options for this workload and cite current limits" \
--web-access \
--format markdownChoose a live model explicitly only when its cost, speed, or capability matters:
kagi assistant \
"review this migration plan for data-loss risks" \
--model MODEL_SLUG \
--no-web-access \
--format markdownFor a model comparison, send the same bounded prompt to each model in a fresh thread. Compare correctness, latency, and usefulness, not prose style alone.
Analyze files
Attach only the files needed for the answer. Assistant accepts documents, spreadsheets, images, and audio; one upload can be at most 30 MB.
kagi assistant \
--attach ./report.pdf \
"extract the decision, evidence, risks, and unresolved questions" \
--no-web-access \
--format markdownUploaded content remains in the thread context. Start a new thread when the next task should not inherit it.
Require structured output
Use a built-in contract for reusable decisions, plans, and checklists:
kagi assistant \
"decide whether this service is ready to launch" \
--contract decision \
--format jsonUse --contract-file PATH when the consumer needs a different small JSON
shape. Contract mode validates the response and makes one repair attempt.
Budget discipline
- Use subscriber Summarizer or Translate for direct transformations when the active plan includes them.
- Use the account default or a lower-cost model for simple work.
- Disable web access for closed-context work.
- Keep prompts specific and attach only relevant files.
- Start a new thread for an unrelated task.
- Reserve Research assistants and premium models for work that needs their extra tools or reasoning depth.
Completion criteria
AI work is complete when:
- the selected lane matches the task;
- every explicit model or assistant came from live account discovery;
- web access and attachments are limited to what the answer needs;
- structured output passes its contract when a machine will consume it;
- the response answers the task instead of spending allowance on avoidable transformations; and
- you changed or deleted account state only when the user asked.
In this repository6 other files it gives its agents.
- docs/llms.txtllms.txt
- kagi-cliSkill
- kagi-account-configSkill
- kagi-assistantSkill
- kagi-monitoringSkill
- kagi-usageSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

