How do I install the Index365 Setup skill?

Run npx skillmds@latest add index365usa/index365-setup in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Index365 Setup safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Index365 Setup?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Index365 Setup free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Index365 Setup?

index365usa (@index365usa) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Index365 Setup by index365usa — Agent Skill

Name: Index365 Setup
Author: index365usa

Index365 Setup

Use when index365 is being used for the first time, when any index365 command exits 3 or returns a 401 / auth error, when `index365 doctor` reports missing authentication, or when the user says "connect index365", "set up index365", "log in to index365", or "add my index365 API key". This is the recovery path for every other index365 skill. Do not work around missing or insufficient authentication, fix it here.

index365usa 893ddd9 3.2 KB Updated Sep 17, 2026

File contents

index365 setup

Get the @index365/cli installed and signed in.

1. Install

npm install -g @index365/cli   # then the bin is `index365`
# If global installation is unavailable, define this wrapper in the current shell:
index365() { npx -y @index365/cli "$@"; }

Install unpinned so a new machine gets the current CLI. The CLI reports its own updates.

2. Sign in

index365 login

index365 login opens the browser: you authorize on the dashboard and the key saves itself (loopback + PKCE, nothing to copy or paste). It confirms who you are signed in as and your credit balance. That is the whole flow on a machine with a browser.

In CI or a non-interactive runtime the browser consent cannot complete, so a bare login exits 3 with the exact alternative. Create a dedicated revocable API key in Org settings → API keys (available on every plan, including Free), then use one of:

export INDEX365_API_KEY=i365_xxx   # preferred: keeps the key out of shell history
index365 login --key i365_xxx

The key is saved to ~/.config/index365/config.json (mode 0600). INDEX365_API_KEY overrides the file. Never print the key in shared logs.

3. Verify

index365 --status

--status shows auth, org, plan, credits, and your latest run at a glance. If it shows you signed in, hand back to whatever skill triggered setup: no further pre-flight is needed, every command self-reports failures through exit codes and a next: hint.

Troubleshooting (this is where `doctor` lives)

index365 doctor diagnoses auth, connectivity, version, and config permissions; doctor --fix applies the safe fixes. Reach for it only when a command's own error message is not enough.

Symptom	Fix
Exit code 3 / "auth" on any command	key is missing, wrong, or revoked: run `index365 login` again, or set a fresh `INDEX365_API_KEY` in a non-browser runtime
`login` exits 3 saying it needs a browser	non-interactive shell: use `INDEX365_API_KEY` or `index365 login --key <key>`
A command says the credential lacks a scope	sign in again through `index365 login`; current keys carry the full work-area scope set. If the scope is still absent, stop and report it
`index365: command not found`	npm global bin not on PATH, or use `npx -y @index365/cli`
Exit code 5 / quota or rate	plan limit or rate limit: wait and retry, or check the plan
Config permission warnings	`index365 doctor --fix`

MCP (optional, for Claude Code / Codex / Cursor)

index365 mcp config   # prints ready-to-paste config for each host

The MCP server calls the same /api/v1 as the CLI and acts with the credential's scopes. Credit-spending and destructive calls keep their separate confirmation gates.

---name: index365-setupdescription: Use when index365 is being used for the first time, when any index365 command exits 3 or returns a 401 / auth error, when `index365 doctor` reports missing authentication, or when the user says "connect index365", "set up index365", "log in to index365", or "add my index365 API key". This is the recovery path for every other index365 skill. Do not work around missing or insufficient authentication, fix it here.---# index365 setupGet the `@index365/cli` installed and signed in.## 1. Install```bashnpm install -g @index365/cli # then the bin is `index365`# If global installation is unavailable, define this wrapper in the current shell:index365() { npx -y @index365/cli "$@"; }```Install unpinned so a new machine gets the current CLI. The CLI reports its own updates.## 2. Sign in```bashindex365 login````index365 login` opens the browser: you authorize on the dashboard and the key savesitself (loopback + PKCE, nothing to copy or paste). It confirms who you are signed inas and your credit balance. That is the whole flow on a machine with a browser.In CI or a non-interactive runtime the browser consent cannot complete, so a bare`login` exits 3 with the exact alternative. Create a dedicated revocable API key in**Org settings → API keys** (available on every plan, including Free), then use oneof:```bashexport INDEX365_API_KEY=i365_xxx # preferred: keeps the key out of shell historyindex365 login --key i365_xxx```The key is saved to `~/.config/index365/config.json` (mode 0600). `INDEX365_API_KEY`overrides the file. Never print the key in shared logs.## 3. Verify```bashindex365 --status````--status` shows auth, org, plan, credits, and your latest run at a glance. If itshows you signed in, hand back to whatever skill triggered setup: no furtherpre-flight is needed, every command self-reports failures through exit codes and a`next:` hint.## Troubleshooting (this is where `doctor` lives)`index365 doctor` diagnoses auth, connectivity, version, and config permissions;`doctor --fix` applies the safe fixes. Reach for it only when a command's own errormessage is not enough.| Symptom | Fix || --- | --- || Exit code 3 / "auth" on any command | key is missing, wrong, or revoked: run `index365 login` again, or set a fresh `INDEX365_API_KEY` in a non-browser runtime || `login` exits 3 saying it needs a browser | non-interactive shell: use `INDEX365_API_KEY` or `index365 login --key <key>` || A command says the credential lacks a scope | sign in again through `index365 login`; current keys carry the full work-area scope set. If the scope is still absent, stop and report it || `index365: command not found` | npm global bin not on PATH, or use `npx -y @index365/cli` || Exit code 5 / quota or rate | plan limit or rate limit: wait and retry, or check the plan || Config permission warnings | `index365 doctor --fix` |## MCP (optional, for Claude Code / Codex / Cursor)```bashindex365 mcp config # prints ready-to-paste config for each host```The MCP server calls the same `/api/v1` as the CLI and acts with the credential'sscopes. Credit-spending and destructive calls keep their separate confirmation gates.

Frequently asked questions