agentleFS
gofixpointgofixpoint/amika/.agents/skills/amika-cli/SKILL.md

amika-cli

Skill301 starsChanged 11 days agoApache-2.0View on GitHub

Drive the `amika` CLI to create, inspect, and operate Amika rigs, the organization's own hosts, and agent chat sessions non-interactively. Use when a task involves `amika rig`, `amika host`, `amika send`, `amika auth`, `amika secret`, `amika service`, `amika snapshot`, or `amika scp`, including listing or retiring bring-your-own-compute hosts and discovering and debugging services from inside an Amika rig.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 4 are distinctive, and 7 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 7

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use amika to operate hosted Amika rigs, the organization's own hosts, and agent chat sessions without hanging on prompts or interactive …

    line 8
  2. Distinctive:

    Read only the reference relevant to the task:

    line 13
  3. Very specific:

    When $AMIKA_RIG_NAME is set, it means you are running inside a rig, and it has that rig's name.

    line 28
  4. Very specific:

    Only if the command succeeds and the referenced service is absent should you inspect the repository's .amika/config.toml.

    line 43
  5. Distinctive:

    If service listing fails, diagnose the CLI or authentication error.

    line 48
  6. Distinctive:

    Follow these rules unless the user explicitly wants an interactive session:

    line 54
  7. Very specific:

    Prefer -o json or -o json-pretty when the command supports it.

    line 56
  8. Very specific:

    Do not run rig connect, rig open (alias rig code), or bare rig ssh in a tool call.

    line 58
  9. Very specific:

    Use amika rig ssh <rig> <command> for non-interactive remote work.

    line 60
  10. Very specific:

    Use amika send to send messages to an agent that either creates a new rig or lives inside an existing rig.

    line 61
  11. Distinctive:

    Check structured results for per-item errors.

    line 63

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Using the amika CLI

Use amika to operate hosted Amika rigs, the organization's own hosts, and agent chat sessions without hanging on prompts or interactive sessions. Hosted rigs are the default target. Run amika <command> --help before relying on a flag in a reference because the installed binary is authoritative.

Read only the reference relevant to the task:

  • Rig lifecycle, hosts, agents, auth, and secrets
  • Services, repository config, and snapshots
  • SSH, editors, and file transfer
  • Structured output and non-interactive behavior

This skill ships inside the amika binary, versioned with it. Install or upgrade it with amika skill install --global (home directory) or amika skill install --local (current repository), optionally limited with --agents claude,codex,cursor. Rerun it after upgrading amika so the skill matches the installed CLI.

Inside an Amika rig

When $AMIKA_RIG_NAME is set, it means you are running inside a rig, and it has that rig's name. Otherwise, you are running outside a rig. Inside a rig, _self names it wherever a command takes a rig.

For any task involving a service, URL, port, preview, or local server, inspect the rig's live services first:

amika service list --rig _self -o json

Find the referenced service in that result and use its provisioned url and ports. The live service record is authoritative for how to reach the service. A service whose URL is - still exists; it may not have a public URL yet.

Only if the command succeeds and the referenced service is absent should you inspect the repository's .amika/config.toml. Its [services.<name>] entry declares the expected container port and URL scheme, but it does not prove that the service was provisioned or reveal its current public URL.

If service listing fails, diagnose the CLI or authentication error. Do not treat a failed lookup as evidence that the service is absent and skip directly to the config file.

Safe automation

Follow these rules unless the user explicitly wants an interactive session:

  1. Prefer -o json or -o json-pretty when the command supports it.
  2. Supply required confirmation flags up front.
  3. Do not run rig connect, rig open (alias rig code), or bare rig ssh in a tool call. They require a controllable terminal.
  4. Use amika rig ssh <rig> <command> for non-interactive remote work.
  5. Use amika send to send messages to an agent that either creates a new rig or lives inside an existing rig.
  6. Check structured results for per-item errors. Do not rely only on the process exit code.

See non-interactive behavior for output shapes, confirmation flags, and commands that reject JSON output.

Task routing

NeedStart with
Identify the current rig$AMIKA_RIG_NAME
Find a service URL or port inside a rigamika service list --rig _self -o json
Create, list, start, stop, or delete rigsamika rig --help
Run a coding agentamika send --help
Run a command remotelyamika rig ssh <rig> <command>
Copy filesamika scp --help
Manage service exposureamika service --help
Capture a base environmentamika snapshot --help
Fork from a snapshotamika rig create --snapshot <name>
List the org's own hostsamika host list
Run a rig on one of those hostsamika rig create --host <hostname>
Authenticate in a headless environmentSet AMIKA_API_KEY

Critical facts

  • Rig creation auto-detects the current git repository and makes a clean clone. Uncommitted work is not copied.
  • snapshot list -o json returns {"items": [...]}; most list commands return a bare array.
  • --secret env:KEY=NAME refers to a stored secret name, not a literal value.
  • amika send can report an agent failure through is_error; inspect the result even when the request completed.
  • .amika/config.toml is the reviewable source for how a repository configures a rig. It is the default, but can be overridden, so it's not a substitute for checking a running rig's live state.

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.