generated: '2026-07-19'
method: searched
source: https://github.com/laserdata/laser-cli-claude
docs: https://docs.laserdata.cloud/cli/claude-skills
publisher: LaserData (first-party)
notes: These are LaserData's OWN published Claude Code Agent Skills, saved verbatim from the official
  laser-cli-claude repository - not skills generated by API Evangelist. Each skill shells out to the `laser`
  CLI rather than calling the REST API directly, and exits early with a clear error if the binary is missing
  from $PATH or the user is not signed in. CI and agents can skip `laser auth login` by exporting LD_API_KEY
  and LD_TENANT_ID.
grounded_in: cli/laserdata-cli.yml
install:
- method: cli-installer
  command: curl -fsSL https://cli.laserdata.cloud/install.sh | sh -s -- --with-cc-skills
- method: claude-plugin-marketplace
  command: /plugin marketplace add laserdata/laser-cli-claude ; /plugin install cli@laser
- method: script
  command: curl -fsSL https://cli.laserdata.cloud/claude.sh | sh
- method: manual
  command: git clone https://github.com/laserdata/laser-cli-claude.git && cp -R laser-cli-claude/skills/*
    ~/.claude/skills/
install_env:
- name: LASER_CLAUDE_DEST
  effect: Override the skill install directory.
- name: LASER_CLAUDE_REF
  effect: Pin the skill bundle to a tag.
skill_count: 14
skills:
- file: laserdata-access.md
  name: laser-access
  slash_command: /laser-access
  description: Manage deployment access rules (firewall) - list, add CIDRs with per-protocol toggles (Iggy
    TCP/HTTP/WebSocket/UDP), delete. Every deployment is fully isolated by default until rules are added.
  upstream: https://github.com/laserdata/laser-cli-claude/blob/main/skills/laser-access.md
- file: laserdata-audit.md
  name: laser-audit
  slash_command: /laser-audit
  description: Query the tenant audit log. Filter by time window, division, environment, deployment, subject
    user, author user, audit types, or correlation id. Useful for incident forensics, compliance reviews,
    "who did what when".
  upstream: https://github.com/laserdata/laser-cli-claude/blob/main/skills/laser-audit.md
- file: laserdata-backup.md
  name: laser-backup
  slash_command: /laser-backup
  description: Manage point-in-time backups of a deployment's storage volumes (network storage only, AWS
    today). List, create, restore, delete - with safety checks for destructive ops.
  upstream: https://github.com/laserdata/laser-cli-claude/blob/main/skills/laser-backup.md
- file: laserdata-billing.md
  name: laser-billing
  slash_command: /laser-billing
  description: Read tenant billing surface - subscription/customer info, billing reports, invoices, and
    download invoice PDFs. Read-only on the CLI today.
  upstream: https://github.com/laserdata/laser-cli-claude/blob/main/skills/laser-billing.md
- file: laserdata-channel.md
  name: laser-channel
  slash_command: /laser-channel
  description: Manage tenant notification channels (slack, webhook, email). Create / get / list / update
    / delete / test / inspect delivered notifications. Channels are how the platform alerts a human when
    something happens to a deployment.
  upstream: https://github.com/laserdata/laser-cli-claude/blob/main/skills/laser-channel.md
- file: laserdata-config.md
  name: laser-config
  slash_command: /laser-config
  description: Manage versioned deployment configs (iggy, connectors, warden, individual connector instances).
    List, view, create new versions from a JSON file, activate, delete. Plus connector-instance lifecycle.
  upstream: https://github.com/laserdata/laser-cli-claude/blob/main/skills/laser-config.md
- file: laserdata-context.md
  name: laser-context
  slash_command: /laser-context
  description: Manage named CLI contexts - api-url + tenant scope + key store. List, switch, create, rename,
    delete contexts and explain what each verb does.
  upstream: https://github.com/laserdata/laser-cli-claude/blob/main/skills/laser-context.md
- file: laserdata-credentials.md
  name: laser-credentials
  slash_command: /laser-credentials
  description: Read deployment admin credentials safely - reveal once, never echo into the conversation.
    Returns username + password only. Endpoints come from `laser deployment get`.
  upstream: https://github.com/laserdata/laser-cli-claude/blob/main/skills/laser-credentials.md
- file: laserdata-debug.md
  name: laser-debug
  slash_command: /laser-debug
  description: Inspect the local laser CLI debug log to surface recent failures, transport errors, and
    slow requests. Useful when a CLI command misbehaves and the user wants to know why.
  upstream: https://github.com/laserdata/laser-cli-claude/blob/main/skills/laser-debug.md
- file: laserdata-deploy.md
  name: laser-deploy
  slash_command: /laser-deploy
  description: Translate a natural-language deployment request into the right `laser deployment create-managed
    | create-starter | create-byoc` invocation (plus `preview` for cost estimates before provisioning),
    then run it with the user's confirmation. Discovers cloud, region, tier and storage from the API rather
    than guessing.
  upstream: https://github.com/laserdata/laser-cli-claude/blob/main/skills/laser-deploy.md
- file: laserdata-iam.md
  name: laser-iam
  slash_command: /laser-iam
  description: Manage tenant identity + access - tenant config (join policy + invitation rules), API keys,
    members, roles, invitations, and cloud-account registrations. All operate at tenant scope.
  upstream: https://github.com/laserdata/laser-cli-claude/blob/main/skills/laser-iam.md
- file: laserdata-onboard.md
  name: laser-onboard
  slash_command: /laser-onboard
  description: First-run setup for the LaserData Cloud CLI. Installs the binary, signs in, sanity-checks
    the active context.
  upstream: https://github.com/laserdata/laser-cli-claude/blob/main/skills/laser-onboard.md
- file: laserdata-snapshot.md
  name: laser-snapshot
  slash_command: /laser-snapshot
  description: Manage diagnostic snapshots - full-system HTML reports per node (system, runtimes, certificates,
    network, kernel, logs). Snapshots are NOT data backups. Use /laser-backup for storage-volume restore
    points.
  upstream: https://github.com/laserdata/laser-cli-claude/blob/main/skills/laser-snapshot.md
- file: laserdata-troubleshoot.md
  name: laser-troubleshoot
  slash_command: /laser-troubleshoot
  description: Diagnose a struggling deployment. Pulls metrics, heartbeats, recent activity, runtime logs
    and access rules, summarises health, surfaces the likely root cause and a concrete next step.
  upstream: https://github.com/laserdata/laser-cli-claude/blob/main/skills/laser-troubleshoot.md