skipper

Skipper plugin for Claude Code

A shareable Claude Code plugin that lets your coding agent delegate backend generation to Skipper and build the frontend itself.

Ask "build an app/website with a backend" or "create an API for X" and the agent will: confirm you want Skipper → check your environment → write a prompt.md → skipper create the service → read the generated openapi.json → run it → scaffold a UI against the spec. The backend is generated by Skipper; the UI is built by your agent against the generated OpenAPI contract.

What's inside

Item	Type	Triggers on
/skipper:skipper-build	skill	"build an app/website with a backend", API/service requests, or mentioning Skipper
/skipper:skipper-setup	skill	"set up / log into Skipper", or when build's preflight fails
/skipper:status	command	quick readiness check (Docker / login / balance)
/skipper:new	command	start a new service: /skipper:new <description>

The build skill defers to the setup skill when the environment isn't ready — there's no router; Claude selects skills by their descriptions.

Layout

.
├── .claude-plugin/
│   ├── plugin.json        # plugin manifest
│   └── marketplace.json   # this repo doubles as a single-plugin marketplace
├── skills/
│   ├── skipper-build/SKILL.md
│   └── skipper-setup/SKILL.md
└── commands/
    ├── status.md
    └── new.md

Install

npx skills add skiplabs/skipper-skills

Then start a fresh session so the skills load. (skiplabs is the marketplace name from marketplace.json; skipper is the plugin name from plugin.json, hence the /skipper: command prefix.)

Try it locally before publishing

# Fastest: load the plugin dir directly
claude --plugin-dir /Users/hugo/dev/skiplabs/skipper-skills

# Or exercise the real marketplace path against the local checkout
/plugin marketplace add /Users/hugo/dev/skiplabs/skipper-skills
/plugin install skipper@skiplabs

Start a fresh session after installing so the skills load.

Requirements

The setup skill guides these, but they ultimately need a human (browser/payment) and can't be automated:

• Docker running locally (the setup skill can start Docker Desktop on macOS).
• A Skipper account, logged in via npx --yes @skiplabs/skipper login (interactive: browser + paste token). Sign up / top up at https://www.skipper.skiplabs.io.
• A positive balance — generation costs money.

The CLI itself needs no install; the skills always call it via npx --yes @skiplabs/skipper — never a skipper on PATH, which could be a different tool or a local dev build pointing at the wrong backend.

Before publishing

• Push this directory to the public skiplabs/skipper-skills repo so npx skills add skiplabs/skipper-skills resolves.
• Bump version in both plugin.json and marketplace.json on each release (omit version to track the git SHA instead) — CI fails the build if they drift apart.

What it drives

The published @skiplabs/skipper CLI. See each SKILL.md for the full runbook and command reference.