Download for MacApple silicon, macOS 14+
Skill

ory-local-dev

@ory Updated 2026-09-30

Run a local Ory stack (Kratos identity, Keto permissions, Hydra OAuth2, gateway on :4000) for building and testing an authentication application without an Ory Network project. Use whenever the user wants to develop, prototype, or test login/registration/recovery/permission flows locally — phrases like "run Ory locally", "no Ory project yet", "offline auth dev", "test my login flow", "spin up Kratos/Keto/Hydra", or "I just want to try this on my machine". Drives the `/ory-agent-plugin:local-up` and `/ory-agent-plugin:local-down` commands.

Install

With your agent

Install OMGSkills skill "ory/claude-plugins:plugins/ory-agent-plugin/skills/ory-local-dev" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.

Manual command

git clone https://github.com/ory/claude-plugins /tmp/claude-plugins && ln -s /tmp/claude-plugins/plugins/ory-agent-plugin/skills/ory-local-dev ~/.claude/skills/ory-local-dev

From README

Build an Auth App Against a Local Ory Stack You are helping the user develop an authentication application against a local Ory stack running in Docker — not against Ory Network. The @ory/claude-code plugin ships two commands that manage the lifecycle: /ory-agent-plugin:local-up — start Kratos, Keto, Hydra, and an Nginx gateway, then seed a test identity, session, and permission tuples. /ory-agent-plugin:local-down — stop all services while preserving data volumes. Both delegate to npx -y -p @ory/claude-code ory-claude local , so the same workflow runs from the shell when the command shortcuts are not available. When to use this skill Pick the local stack over Ory Network when any of these are true: The user has no Ory Network project yet and wants to prototype. The user is working offline or behind an egress restriction. The user wants deterministic, throwaway test data they can reset freely (local reset). The user is writing automated tests that hit a real Ory backend.