Stats
Actions
Tags
From salto-cli-skills
Single entry point for all Salto workflows. Type a natural-language request and the skill routes it internally — deploy (make changes) or explore (query/inspect) — and loads adapter-specific knowledge as needed. Use this for any task against a Salto NACL workspace.
How this skill is triggered — by the user, by Claude, or both
Slash command
/salto-cli-skills:saltoThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
> [!NOTE]
[!NOTE]
Usage: /salto "" [--workspace ] [--deployment-id | --branch-name ]
The only Salto command exposed in Claude Code. This skill is a thin router. Based on your request it loads the right internal workflow (references/salto-deploy.md or references/salto-explore.md) plus any adapter-specific knowledge (adapters/<adapter>.md) from this plugin, then executes those instructions with your original $ARGUMENTS.
Claude Code automatically sets ${CLAUDE_PLUGIN_ROOT} to this plugin's absolute path. Use it directly for any sibling file:
${CLAUDE_PLUGIN_ROOT}/references/salto-deploy.md, ${CLAUDE_PLUGIN_ROOT}/references/salto-explore.md${CLAUDE_PLUGIN_ROOT}/adapters/<adapter>.mdNo discovery needed.
$ARGUMENTSDEPLOY — the user wants to create, change, rename, delete, or fix a configuration element, or resume an existing deployment.
Keywords that signal DEPLOY: add, create, rename, delete, remove, change, update, set, enable, disable, fix, deploy.
EXPLORE — the user wants to read, list, compare, inspect, or understand current state without making changes.
Keywords that signal EXPLORE: what, show, list, which, how many, compare, diff, explain, find, status, history, does, is there, are there.
AMBIGUOUS — intent cannot be determined.
| Input | Route |
|---|---|
| "add Zendesk trigger ai_review_test that tags new tickets" | DEPLOY |
| "what Zendesk triggers exist in my prod environment?" | EXPLORE |
| "rename the Okta group admins to platform-admins" | DEPLOY |
| "what would change if I deployed now?" | EXPLORE |
| "fix the changeError on trigger ai_review_test" | DEPLOY |
| "list my deployments" | EXPLORE |
| "compare prod and staging" | EXPLORE |
| "show me the ai_review_test trigger definition" | EXPLORE |
| "delete the old Zendesk macro close_ticket_legacy" | DEPLOY |
| "Zendesk trigger ai_review_test" | AMBIGUOUS |
If DEPLOY:
Routing to salto-deploy workflow...${CLAUDE_PLUGIN_ROOT}/references/salto-deploy.md using the Read tool.$ARGUMENTS unchanged. The reference file uses ${CLAUDE_PLUGIN_ROOT} for paths to adapter knowledge (e.g. ${CLAUDE_PLUGIN_ROOT}/adapters/zendesk.md).If EXPLORE:
Routing to salto-explore workflow...${CLAUDE_PLUGIN_ROOT}/references/salto-explore.md using the Read tool.$ARGUMENTS unchanged.If AMBIGUOUS: Ask exactly: "Do you want to (1) make a change and deploy it, or (2) explore/query the current state without making changes?"
/salto "add Zendesk trigger ai_review_test that tags new tickets as pending_review"
/salto "what Zendesk triggers exist in my prod environment?"
/salto "show me what would change if I deployed now" --deployment-id abc123
/salto "compare prod and staging Zendesk triggers"
/salto "rename the Okta group admins to platform-admins"
All flags (--workspace, --deployment-id, --branch-name, etc.) are passed through to the inner workflow unchanged.
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub salto-io/salto-claude-plugin --plugin salto-cli-skills