Claude Code Skills

The laser-cli-claude skill pack lets Claude Code translate requests into laser commands. It includes /laser-deploy, /laser-troubleshoot, and /laser-snapshot. Source is available at github.com/laserdata/laser-cli-claude.

Install

Bundled with the CLI (one shot)

If laser is not installed, install the binary and skills together:

curl -fsSL https://cli.laserdata.cloud/install.sh | sh -s -- --with-cc-skills

The installer runs cli.laserdata.cloud/claude.sh after installing the binary. Re-running updates both in place, with cp -f for skill files. See installer flags for the full list.

Marketplace (recommended for skills-only)

/plugin marketplace add laserdata/laser-cli-claude
/plugin install cli@laser

Script (skills only)

curl -fsSL https://cli.laserdata.cloud/claude.sh | sh

The script downloads the latest bundle and copies its *.md files to ~/.claude/skills/. Run it again to update existing files. Use these environment variables to change the destination:

LASER_CLAUDE_DEST=~/my-skills ./claude.sh
LASER_CLAUDE_REF=v0.0.1 ./claude.sh   # pin to a tag

Manual

git clone https://github.com/laserdata/laser-cli-claude.git
cp -R laser-cli-claude/skills/* ~/.claude/skills/

Prerequisites

curl -fsSL https://cli.laserdata.cloud/install.sh | sh
laser auth login --tenant-id <numeric-id>

Each skill runs laser commands. It stops with an error if the binary is missing from $PATH or credentials are unavailable. Agents and CI can supply LD_API_KEY and LD_TENANT_ID instead of running auth login.

Skills

Slash command	Purpose
`/laser-onboard`	First-run setup. Installs the binary, walks through sign-in, and sanity-checks the active context.
`/laser-deploy`	Translates a request like "spin up Iggy in `eu-west-1` on the Standard tier" into the matching `laser deployment create-managed`, `create-starter`, or `create-byoc` invocation, plus `preview` for cost estimates, the two-step BYOC helpers `byoc setup` + `byoc validate`, and the full lifecycle: `upgrade`, `extend`, `retention`, `spend-limit`, `update`, `delete`. Cloud, region, tier, and storage are discovered from the API rather than guessed.
`/laser-troubleshoot`	Pulls metrics, heartbeats, activity, recent runtime logs, network, tasks, and access rules for a deployment in trouble. Returns a structured health report with a concrete next step, including per-runtime restart on a single node when that is the right call.
`/laser-config`	Manages versioned deployment configs (Iggy, connectors, Warden, individual connector instances): list, view, create new versions from a JSON file, activate, delete. Plus connector-instance lifecycle.
`/laser-snapshot`	Manages diagnostic HTML snapshots covering system state, runtimes, certificates, network, kernel parameters, and logs.
`/laser-backup`	Manages point-in-time storage volume backups. Available for AWS Network Drive deployments when backups are enabled on your account plan.
`/laser-access`	Manages access rules: list, add CIDR allowlists with per-protocol toggles (Iggy TCP/HTTP/WebSocket/UDP), and delete.
`/laser-channel`	Manages tenant notification channels (Slack, webhook, email): create, list, update, delete, test, and inspect delivered notifications.
`/laser-iam`	Manages tenant identity and access: tenant config (join policy + invitation rules), API keys, members, roles, invitations, and cloud-account registrations. All scoped to the tenant.
`/laser-billing`	Reads the tenant billing surface: subscription and customer info, billing reports, invoices, and invoice PDF downloads. Read-only on the CLI today.
`/laser-credentials`	Reads deployment connection credentials safely. Output is masked in chat and never persisted.
`/laser-context`	Manages named CLI contexts (api-url + tenant scope + key store): list, switch, create, rename, and delete.
`/laser-audit`	Queries the tenant audit log with filters for time window, division, environment, deployment, subject user, author, types, or correlation id. Useful for incident forensics and compliance.
`/laser-debug`	Reads the local debug log and surfaces recent failures grouped by target. Also documents the platform headers (`ld-request`, `idempotency-key`, `idempotent-replayed`, `link`, `retry-after`) and the `application/problem+json` envelope (RFC 7807) so failure traces map back to API behavior.

Built-in Guardrails

Each skill follows these rules:

Retrieve current tiers, regions, and account details through laser cloud tiers, laser cloud regions, and laser tenant get.
Display the exact command before any change and wait for your approval.
Use -o json and parse structured responses.
Read credentials through laser and its keyring support instead of placing API keys in commands.
Require typed approval for deletion, restoration, and spend-limit changes. Protected resources also require a one-time code.
Show /laser-credentials values once on screen. Do not save them to files or shell history.

Examples

To create a starter deployment, ask:

"Set up a starter Iggy for me to play with."

/laser-deploy asks for AWS or GCP and presents the default region, us-east-1 or us-central1. It shows the laser deployment create-starter command and waits for approval. It then follows the deployment until it is ready.

To investigate a deployment, ask:

"events-prod looks unhealthy."

/laser-troubleshoot events-prod finds the deployment by name. It reads heartbeats, metrics, the last 200 log lines, recent activity, and active access rules. It presents a summary and the most likely cause on one screen.

To add a firewall rule, ask:

"Allow my home IP to hit events-prod."

/laser-access finds your public IP. It displays laser deployment access-rule add --deployment-id 611298765432109056 --cidr <ip>/32 --description "home" and waits for approval before applying it.