Lakehousecat Plugin for Claude Code

The Lakehousecat plugin for Claude Code lets you operate a Lakehousecat instance in plain language from your terminal. It is a set of skills that teach Claude Code how to drive the lhc CLI — everything the plugin does goes through lhc. There is no separate API client, no bundled binary, and no credentials of its own.

Claude Code  ──►  skills (this plugin)  ──►  lhc <command>  ──►  your instance

Availability

The plugin is published as lhc-claude-plugin in the lakehousecat GitHub organisation.

Requirements

• Claude Code
• The lhc CLI on your PATH — the /lhc:setup skill installs it for you if it is missing (see the CLI Reference)
• A Lakehousecat instance and an API key (Account Settings → Security → API Keys → Generate API Key)

Getting Started

Once installed, run:

/lhc:setup

Setup checks whether the CLI is present, whether a profile or the LHC_API_KEY + LHC_ENDPOINT environment pair is configured, and walks you through lhc configure if neither is. It finishes by reporting which instance you are pointed at and which role your key has.

After that, just say what you want in plain language — Claude picks the matching skill:

"Which datasources are configured?" "Create a chart showing revenue per region for the retail model." "Invite alice@example.com as a builder."

You rarely name a skill yourself. Describe what you want and Claude picks the matching one; the /lhc:... form is there when you want to be explicit.

Skills

Skill	What it covers
/lhc:setup	Install the CLI, configure a profile, report target and role
/lhc:instance	Version, licence and subscription state; who your key belongs to
/lhc:users	Invite, update and remove users; roles
/lhc:groups	Groups and membership
/lhc:datasources	Database and file connections
/lhc:semantic	Schema extraction, data loads, descriptions, hierarchies
/lhc:models	Provider models and custom models
/lhc:analytics	Turn a question into a chart; pipeline steps; SQL validation
/lhc:charts	List, share, clone and delete existing charts
/lhc:dashboards	Dashboards, sharing, approval, export and import
/lhc:sessions	Chat sessions
/lhc:prompts	Reusable prompt templates
/lhc:jobs	Scheduled job definitions and runs
/lhc:samples	Install a ready-made sample package
/lhc:backup	Trigger a backup and report per-component status
/lhc:restore	Restore from a backup — destructive, confirmation required

Authentication

The plugin has no credential store of its own. It authenticates exactly the way the lhc CLI does — through your existing profiles in ~/.lhc/credentials, selected via --profile or the LHC_PROFILE environment variable. See Authentication & Setup for the full setup guide.

What Your API Key Can Do

The plugin inherits the permissions of the key your active profile uses — it cannot exceed them:

Role	Scope
admin	Full administrative control, including users, groups and instance settings
builder	Builds and manages data assets: datasources, models, semantic layer, charts, dashboards
user	Consumes existing assets: runs analyses, reads charts and dashboards

If a skill attempts an action your role does not permit, the underlying lhc command returns the same 403 it would from a direct CLI call.