Adiact docs / CLI

CLI documentation for shipping skills in production

End-to-end guide based on the Adiact CLI reference: install, authenticate, save skills, publish bundles, activate versions, sync across machines, and configure MCP clients.

Step 1

Install CLI

Install the published npm package and use adiact globally right away.

Step 2

Authenticate

Use API token login once and keep credentials in secure keychain storage.

Step 3

Ship + Sync

Publish versions, activate in workspace, then sync local and remote safely.

Installation

# Install from npm registry
npm install -g adiact-cli

# Verify installation
adiact --help

This installs the published CLI package and exposes adiact globally.

Authentication

adiact login
adiact login --token adiact_xxxxxxxx
adiact logout

Get your token from dashboard Settings > API Token.

Core command groups

Skills

  • adiact list, adiact search <query>
  • adiact pull <slug>, adiact use <slug>
  • adiact save <path> with tags, visibility, collection and dry-run

Bundles (versioned packages)

  • adiact upload <skill-slug> <directory>
  • adiact publish <skill-slug> <version-id>
  • adiact activate <skill-slug> <version-id>

Sync

  • adiact sync, adiact sync --pro, adiact sync --fast
  • adiact sync:status
  • direction, tags, collections, apply-local and local-dir options

MCP integration

  • adiact mcp interactive setup
  • Target Cursor, Claude or Gemini via --agent
  • Use --out, --skills, --collections and --copy

End-to-end workflow (recommended)

# 1) Login
adiact login --token YOUR_TOKEN

# 2) Save local skill content (file or folder with SKILL.md)
adiact save ./my-skill --tags ops,deploy --visibility PRIVATE

# 3) Upload and publish a versioned bundle
adiact upload my-skill ./my-skill --version 1.0.0
adiact publish my-skill VERSION_ID

# 4) Activate the version in your workspace
adiact activate my-skill VERSION_ID

# 5) Sync between local and cloud
adiact sync --pro

# 6) Generate MCP config for your agent
adiact mcp -a cursor -o .cursor/mcp.json

Use strict semantic versioning: patch for fixes, minor for backward compatible features, major for breaking changes.

Troubleshooting

  • If adiact is not found, check npm global bin path and reinstall with npm install -g adiact-cli.
  • If auth fails, refresh token in dashboard and run adiact login again.
  • If local files are not updated, run adiact sync --apply-local or --pro.
  • Use adiact sync:status to inspect last sync time and counters.
  • For publish waits, tune --timeout or use --no-wait and check status in dashboard.
Need implementation help?Get early access