Claude Code Skills

Drive laser from Claude Code with natural language - install the official skill pack

When you drive laser from inside Claude Code, the official laser-cli-claude skill pack lets the agent translate plain language into the right command without you memorizing every flag. The pack ships slash commands such as /laser-deploy, /laser-troubleshoot, and /laser-snapshot.

Source: github.com/laserdata/laser-cli-claude

Install

Bundled with the CLI (one shot)

If you have not installed laser yet, the CLI installer can drop both the binary and the skill pack in a single step:

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

The flag tells the installer to fetch and run cli.laserdata.cloud/claude.sh after the binary is in place. Both halves are idempotent, so re-running upgrades the binary (overwrite) and the skill pack (cp -f) together. See the CLI install reference for the full flag table.

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

Fetches the latest skill bundle from the public repository and copies every *.md file into ~/.claude/skills/. The script is idempotent, so re-run it any time to update.

Override the install target with environment variables:

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 shells out to laser. If the binary is missing from $PATH or you have not signed in, the skill exits early with a clear error. CI / agents can skip auth login entirely by exporting LD_API_KEY and LD_TENANT_ID instead.

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 small" 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-storage deployments on Pro and Enterprise plans.
`/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

The skill pack is designed for unattended use, so each skill enforces a set of rules:

API-first discovery. Tier names, regions, and storage classes are pulled from laser cloud tiers, laser cloud regions, and laser tenant get at runtime, never hard-coded. The skills stay correct as plans and regions change.
Dry-run before execute. Every mutating command is printed back to you with the exact laser invocation. Nothing runs until you confirm.
JSON-only parsing. Skills always pass -o json and parse structured output rather than scraping table renderings.
No inline API keys. Credentials are read from the OS keyring through laser.
Per-entry confirmation for destructive operations. Delete, restore, and spend-limit changes require typed confirmation. Protected resources additionally require their one-time resource code.
Credentials never leave the chat. /laser-credentials reveals values once on screen and never writes them to a file or shell history.

Examples

Provision a starter cluster:

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

/laser-deploy asks which cloud you want (AWS or GCP), confirms the default region (us-east-1 for AWS, us-central1 for GCP), prints the matching laser deployment create-starter invocation, waits for your confirmation, and then watches the deployment until it is ready.

Triage a flapping deployment:

"events-prod looks unhealthy."

/laser-troubleshoot events-prod resolves the deployment by name, then pulls heartbeats, metrics, the last 200 log lines, recent activity, and the active access rules. The result is a one-screen summary together with the most likely cause.

Add a CIDR to the firewall:

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

/laser-access resolves your public IP, prints the proposed laser deployment access-rule add --deployment-id 611298765432109056 --cidr <ip>/32 --description "home" command, and waits for confirmation before applying it.