agentleFS
Sign inStart free
MicrockMicrock/kagi-cli/skills/kagi-account-config/SKILL.md

kagi-account-config

Skill190 starsChanged 8 months agoMITView on GitHub

Configure Kagi CLI credentials, profiles, lenses, custom bangs, redirects, site preferences, and account-backed assistants. Use when the user wants to inspect or change how Kagi authenticates, searches, or applies account settings.

  • Reads credentials

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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
  1. Very specific:

    Use status to see credential presence and source.

    line 32
  2. Distinctive:

    Use the auth wizard or explicit auth subcommands to set credentials:

    line 35
  3. Distinctive:

    Never pass secrets on a shared shell command line.

    line 42
  4. Distinctive:

    Use profiles when separate accounts or credential policies must coexist.

    line 47
  5. Distinctive:

    Verify the selected profile before changing any setting.

    line 54
  6. Very specific:

    Use each command's --help for the flags a mutation needs.

    line 77
  7. Distinctive:

    no secret value appears in output or persisted scripts.

    line 96

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Kagi Account Configuration

Inspect current state before changing it. Never print, echo, or paste stored credential values into output.

Credential model

CredentialMain capabilities
KAGI_SESSION_TOKENsubscriber search, Quick Answer, Assistant, ask-page, translation, subscriber summarization
KAGI_API_KEYcurrent Search API and Extract API
KAGI_API_TOKENlegacy summarize, FastGPT, and Enrichment APIs

Environment variables override .kagi.toml. --profile NAME selects a named profile. Base search prefers session auth when both search credentials are available, unless preferred_auth = "api" is configured.

Inspect and verify auth

kagi auth status
kagi auth check
kagi usage --format pretty

Use status to see credential presence and source. Use check when a configured credential fails at request time.

Use the auth wizard or explicit auth subcommands to set credentials:

kagi auth
kagi auth set --session-token "https://kagi.com/search?token=..."

Never pass secrets on a shared shell command line. Prefer the interactive wizard or protected environment injection in shared environments.

Profiles

Use profiles when separate accounts or credential policies must coexist.

kagi --profile work auth status
kagi --profile personal search "query" --format toon

Verify the selected profile before changing any setting.

Search settings

Inspect before creating, updating, or deleting:

kagi lens list
kagi lens get "Default"
kagi bang custom list
kagi redirect list
kagi site-pref list

Example custom bang:

kagi bang custom create \
  "Docs" \
  --trigger docs \
  --template "https://docs.rs/releases/search?query=%s"

Use each command's --help for the flags a mutation needs. Never delete or overwrite an account setting unless the user asked for it.

Custom assistants

kagi assistant custom list
kagi assistant custom get "Researcher"

Conversation and thread use belongs in kagi-assistant. This skill owns the account-level configuration of custom assistants.

Completion criteria

Configuration work is complete when:

  • you know the active profile and credential source;
  • the requested setting is visible through its read command;
  • no secret value appears in output or persisted scripts;
  • unrelated account settings remain unchanged; and
  • you made a destructive change only when the user asked for it.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free