Atelier docs
Public setups
Publish reviewed setups, find public setups, and install selected resources safely with signature checks, previews, and backups.
What public setups are
A setup is a public bundle of reviewed resources that someone can share as @owner/name. A setup can include config files, reviewed folders, and Agent Skills.
Public setups are different from private profile sync. Private profile sync stores encrypted config snapshots for your account. Published setups are intentionally public so other people can search, inspect, and install them.
Before you publish
Publishing is explicit and review-first. Atelier shows what it found, asks you to pick the resources to include, and blocks detected secrets or private material. Only publish files you are comfortable making public.
atl setups publish editor-pack You need to be signed in to publish. The setup version is signed with your publishing key so installers can verify who published it and whether the manifest changed.
Find public setups
Search is public and does not require login.
atl setups search zed
atl setups search zed --list
atl setups search zed --json In an interactive terminal, search lets you choose a result and continue into install review.
Preview and install safely
Install fetches the setup, verifies the author's signature, checks every downloaded file hash, then shows a local plan before writing.
atl setups install @owner/name --preview
atl setups install @owner/name The install review shows selected resources, target paths, created files, matching files, conflicts, and diffs when available. Pick only the resources you want on this machine.
Conflicts and backups
Atelier never silently overwrites a differing local file. If a target file already exists and differs from the setup, install blocks unless you ask Atelier to back up the local file first.
atl setups install @owner/name --backup Project-relative resources require an explicit project confirmation so a public setup cannot quietly write into the wrong repository.
Yank a version
Owners can yank a published setup version. A yanked version is blocked for normal new installs, and latest falls back to the newest non-yanked version when one exists.
atl setups yank @owner/name 2 Agent Skills in setups
Setups can include Agent Skills as one resource type. If you only want private account-backed skill sync, keep using the dedicated atl skills workflow.
atl skills scan
atl skills save
atl skills install Safety checklist
- Private profile sync stays encrypted for your account.
- Published setups are public and readable by anyone.
- Publish blocks detected secrets and private material.
- Install verifies signatures and file hashes before planning writes.
- Preview shows what would change before anything is written.
- Differing local files require explicit backup behavior before replacement.