Skip to content
LoopSkill

Docs · Deployment

Coming Q2 2026 with per-bundle API keys and client deployment. The deployment pipeline described here ships as part of Phase C. This page documents the intended flow so you can plan your client onboarding. Everything described below is forward-looking and will be updated when Phase C ships.

Deploying bundles to client agents

Pro+ lets you push a pre-built skill bundle — a bundle — straight into an agent you operate for a client. One install command. Stays in sync. No LoopSkill branding on the client side unless you want it.

Prerequisites

  • An active Pro+ subscription
  • At least one bundle created in your library
  • An available API key slot (Pro+ includes 20 keys)
  • Your client's agent up and running (Claude Code, Codex, Cline, Cursor, Hermes, or any AgentPact-compatible host)

Step-by-step deployment

1

Create a bundle

In /library, click New bundle. Give it a name (visible only to you), and select the skills you want to include. Pin versions or track latest — your choice.

Set visibility to Private if this bundle is client-specific. Public bundles are discoverable by anyone with the URL.

2

Assign an endpoint API key

From the bundle detail view, click Assign key. You'll create a labeled API key scoped to this bundle — for example, acme-client-prod.

This key will only serve skills in this cookbook. Even if someone guesses or leaks the key, they can't access your other skills or other bundles.

3

Give your client the install command

Copy the one-line meta-skill install command from the bundle detail view. It includes the bundle-scoped key pre-filled: 

RECIPES_API_KEY=rec_live_cbk_... \
  curl -sL https://recipes.wisechef.ai/skill \
  -o ~/.claude/skills/recipes/SKILL.md

Your client runs this once in their agent's environment. No other configuration needed.

4

Bundle auto-syncs

The meta-skill fetches the bundle manifest on every poll cycle (default: every 15 minutes). When you push an update — adding a skill, bumping a version, removing something outdated — all agents using that key receive the change on their next sync automatically.

Pushing updates

Edit the bundle in your library: add skills, remove skills, or change version pins. Save. Done. Every agent that installed via the bundle-scoped key picks up the update within one poll cycle — there is no push command, no client-side action required.

If you want to roll back, pin the previous version in the cookbook. The agents revert on the next sync.

White-label guidance

The client-side experience is entirely yours to control:

  • Skills run locally on the client's machine. No LoopSkill domain appears in agent responses unless a skill description explicitly mentions it — and you control the skill descriptions.
  • The bundle-scoped API key URL path does not expose your account name or any identifiable information.
  • You bill your client at your rate. LoopSkill charges you $100/mo flat for Pro+, regardless of how many clients or how much they use.

Learn about bundles first

See what a bundle is, visibility options, and how versions work.

Bundles →