◆ Atelier Install

Atelier docs

For AI agents

A safe, machine-readable playbook for agents helping someone install, inspect, save, preview, and apply Atelier setups.

Start with read-only discovery

Agents should identify the installed CLI, runtime, account state, inventory, and public docs before suggesting any write operation.

atl --version
atl guide --json
atl update --check
atl doctor --json
atl scan --json
atl list --json

If atl doctor --json reports an API URL other than https://atelier.mananjoshi.me/api, check for ATELIER_API_URL in the shell or a local .env before asking the user to log in.

Human handoffs

Atelier intentionally keeps sensitive steps in the user's interactive terminal.

  • Ask the user to run atl login and complete GitHub device auth when private profile sync is needed.
  • Ask the user to enter the vault passphrase in an interactive terminal. Do not ask for it in chat and do not put it in scripts.
  • Ask for approval before running any command that writes files, switches a profile, installs a setup, installs skills, or publishes public resources.

Private profile sync flow

After the user signs in, inspect profiles and saved configs with JSON output, then preview before applying.

atl whoami --json
atl profile list --json
atl saved list --json
atl profile switch personal --preview --json

Only apply after the user approves the preview. Use backups when local files differ.

atl profile switch personal --backup --json

Save configs from this machine

Scan first, inspect candidates, and save only specific items the user wants to carry forward.

atl scan --json
atl list --json
atl inspect zed.settings --json
atl save zed.settings
atl saved list --json

Atelier blocks missing files, generated/cache files, private auth material, detected secrets, oversized files, and unsupported binaries by default.

Install public setups

Public setup search and preview are safe starting points. Install only after the user approves the reviewed resources and target paths.

atl setups search zed --json
atl setups install @owner/name --preview --json
atl setups install @owner/name --backup --yes --json

Project-relative resources require --confirm-project so an agent cannot quietly install into the wrong repository.

Agent Skills

Use the dedicated skills workflow for directories that contain SKILL.md. Generic folder sync intentionally skips skill directories.

atl skills scan --json
atl skills install --preview --json
atl skills install --backup --yes --json

Rules for agents

  • Prefer JSON output when a command supports it.
  • Preview before writing files.
  • Use --backup when replacing a differing local file.
  • Treat plaintext diffs, config contents, and local paths as user-local sensitive data.
  • Do not publish a setup unless the user confirms the selected resources are intended to be public.
  • Do not claim general folder sync unless the installed atl save --help output documents the folder flow.