Orca Skills

Agent Skills are self contained guides that teach an AI agent how to do a specific job well. Orca publishes skills so Claude and other skill aware agents get the Orca data model, the correct order of steps, and the traps, without you re-explaining the platform every time.

Skills cost nothing until the agent needs them. The agent reads each skill’s description, and loads the whole thing only when your task matches.

Available skills

Skill	Use it when
orca-integration	Wiring Orca into an app or backend. The data model, the three key types, both API planes, environments, common pitfalls. Start here.
orca-store-onboarding	Connecting Google Play, Stripe, GoCardless or App Store credentials. Ships a gcloud script that does the automatable Play setup.
orca-product-provisioning	Creating a paid product across every store at once, with pricing and introductory offers.
orca-webhooks	Receiving Orca events and verifying signatures. Includes working Ed25519 verifiers for Node, Go and Python.
orca-billing-ops	Live customer work: checking access, auditing customers, cancelling subscriptions.

Install as a plugin

The easiest way, and it stays up to date with the API:

/plugin marketplace add maxint-app/orca-skills
/plugin install orca@orca

That installs all five. Run it inside Claude Code.

Install manually

Each skill is a folder with a SKILL.md and optional references/, scripts/ and assets/ directories. Clone the repo and copy the folders you want:

$ git clone https://github.com/maxint-app/orca-skills
$ cd orca-skills

# user level, available in every project
$ cp -r skills/orca-integration ~/.claude/skills/

# or project level, checked in with your code
$ cp -r skills/orca-integration .claude/skills/

You don’t invoke skills by hand. The agent reads the description in each one and loads it when your task matches.

How skills and the MCP server work together

They’re complementary, and each works alone.

• Skills are the knowledge: what an entitlement is, why your code should check it instead of a store SKU, which parts of store onboarding no API can automate, how the webhook signature is actually built.
• The MCP server is the actions: callable tools that check a customer’s access, provision products, or register a webhook endpoint.

Together the agent can read orca-store-onboarding to understand how to provision Google Play credentials, run the bundled gcloud script, then walk you through the dashboard where you paste the service account JSON.

Every skill also works without the MCP server. Each one lists the direct API call alongside the tool, so if no orca_* tools are available the agent falls back to plain curl instead of stopping.

Worth knowing

The orca-webhooks skill exists because Orca’s outbound webhooks don’t look like most people expect. There’s no {id, type, data} envelope, the payload is the customer’s entitlement object directly, and the signature is Ed25519 over "{timestamp}.{body}" with the timestamp in Unix epoch seconds. The skill carries verifiers that handle this correctly in three languages.

Store credentials never pass through an agent or the MCP server. Orca’s API rejects store config writes from API keys by design, so the human pastes them into the dashboard, which validates them live. Every skill is written to that rule.