kiro-local-account-importer

Imports local Kiro CLI auth SQLite records into the llm-access admin API with proxy assignment.

2|Updated Jun 18, 2026
One-click install
npx skills add https://github.com/zero-yx/static_flow --skill kiro-local-account-importer-zero-yx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kiro-local-account-importer
Source: https://github.com/zero-yx/static_flow/tree/main/skills/kiro-local-account-importer
Command: npx skills add https://github.com/zero-yx/static_flow --skill kiro-local-account-importer-zero-yx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Manually migrating Kiro CLI accounts into StaticFlow's llm-access gateway requires reading local SQLite auth files, extracting tokens, and configuring concurrency and proxy settings by hand, which is error-prone and risks leaking credentials. ## Core Features & Use Cases - Local SQLite Discovery and Parsing: Finds Kiro auth databases from explicit paths, search directories, or the default ~/.local/share/kiro-cli/data.sqlite3, and reads social and IDC/OIDC token records from auth_kv. - Automated Admin API Import: Creates accounts via POST /admin/kiro-gateway/accounts/import-auth, applies standard scheduling (max concurrency 3, random start interval 200-1000ms, minimum 10 remaining credits), and assigns a fixed United States proxy chosen by least-used load balancing with latency tie-breaking. - Validation with Rollback: Refreshes account balance through the assigned proxy, rejects accounts with insufficient credits or duplicate upstream user IDs, and deletes failed imports automatically. - Use Case: You have several Kiro CLI installations on your machine and want to onboard them all into your self-hosted llm-access gateway. Run the script in dry-run mode to preview the imports, then apply them with balanced US proxy assignment in one command. ## Quick Start Ask the assistant to discover local Kiro auth SQLite files and dry-run import them into the llm-access admin API at http://127.0.0.1:19182, then apply the import after reviewing the output.

Frequently Asked Questions about kiro-local-account-importer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I import Kiro CLI accounts into the llm-access gateway?▼

Run the import_kiro_accounts.py script with --admin-base-url pointing at your local llm-access admin API. It discovers SQLite auth files, parses tokens from auth_kv, and creates accounts through the import-auth endpoint. Start with a dry run, then add --apply to execute.

Where does the importer find Kiro auth SQLite files?▼

It checks paths given via --sqlite-file, recursively scans directories from --search-dir for .sqlite, .sqlite3, and .db files, and falls back to the default ~/.local/share/kiro-cli/data.sqlite3 when nothing is specified.

What Kiro authentication methods are supported for import?▼

Both social login tokens (kirocli:social:token) and IDC/OIDC tokens with device registration records are supported. The script reads them from the auth_kv table and requires a refresh_token, plus client_id and client_secret for IDC accounts.

Can I import Kiro accounts without assigning a proxy?▼

No. Direct or no-proxy imports are explicitly rejected, and the --no-proxy flag causes the script to exit. Every imported account must be fixed to an active United States proxy selected by least-used load balancing.

What happens if an imported Kiro account fails validation?▼

The script refreshes the account balance through the assigned proxy and requires at least 10 remaining credits and a non-duplicate upstream user_id. If validation fails across all candidate proxies, the newly created account is deleted and reported as invalid.

Does the importer expose access tokens or client secrets?▼

No. Dry-run output redacts access_token, refresh_token, and client_secret values, and the skill instructions forbid printing raw credentials. Tokens are only transmitted to the local llm-access admin API during a real import.