Skip to main content
Use an AI coding agent to add custom events to your application. Corbado Observe ships an agent skill following the open agentskills.io standard. It teaches your AI coding agent how to instrument Corbado Observe in your frontend: which events to fire, where to fire them and how to verify the result. The skill uses the SKILL.md format read by most AI coding tools, including Cursor, Claude Code, Codex, GitHub Copilot, Windsurf and Gemini CLI, plus around 70 more compatible agents.
For Autocapture, Corbado configures the capture rules for your login. Follow Integrate Autocapture. To analyze existing Observe data with an agent, use the Observe CLI or MCP server.

​
1. Use it in a prompt

The fastest way, no install required:

​
2. Install it

To make the skill permanently available to your agent:
The https:// scheme is required. The bare domain form (npx skills add docs.corbado.com) is not accepted by the Skills CLI. The command detects your installed agents and writes the skill into each one’s namespaced skills folder, for example .cursor/skills/ or .claude/skills/. It never edits or overwrites your existing AGENTS.md or CLAUDE.md. Manually installed skills do not auto-update. Run npx skills update -y to pull the latest version. Once installed, ask your agent in natural language, for example “Add Corbado Observe tracking to my login and signup flows” or “Instrument my passkey login with Corbado Observe events”.

​
3. What the agent does

The skill guides the agent through a safe, telemetry-only integration:
1

Discovers the auth surface

Finds your login, sign-up, recovery and enrollment entry points and the methods each offers.
2

Models the journeys

Defines flow boundaries, assigns every screen to a decision and maps each method to a subflow, following the modeling method. Where your app and the taxonomy do not match, it documents the lossy mapping instead of contorting the code.
3

Instruments

Adds flows, decisions and subflows with the correct events and payloads, using guarded tracking calls that cannot break your app’s behavior.
4

Validates

Writes down the event series a few representative journeys should produce, asks you to walk them with debug mode on and reads the console output against the rules. See Verify your integration.

​
4. Next steps

Custom events

Install the SDK and send your first event manually.

Modeling

The mapping method the skill applies.