# Agent Skills

Canonical URL: https://magiccard.ai/docs/integrations/agent-skills
Markdown URL: https://magiccard.ai/docs/integrations/agent-skills.md
Summary: Agent skills package the instructions, rules, and commands an AI runtime needs to use MagicPay safely.
Description: Use MagicPay and MagicBrowse through runtimes that support the Agent Skill format.

## Canonical Answer

Agent skills package the instructions, rules, and commands an AI runtime needs to use MagicPay safely. Use MagicPay and MagicBrowse through runtimes that support the Agent Skill format. Protected payment and identity data stays behind MagicPay requests instead of entering LLM-visible context.

## Supported Runtimes

MagicPay supports OpenClaw, Hermes, Claude Code, Codex, Manus, and other agents that can read skill-style instructions and run the public CLIs. Skill bundles are published from the public GitHub repository nuanu-ai/skills.

Runtime | Install path | Skills available
--- | --- | ---
Claude Code | Release bundles into `.claude/skills/` | MagicPay + MagicBrowse
Codex | Release bundles into `~/.codex/skills/` | MagicPay + MagicBrowse
OpenClaw | ClawHub install | MagicPay + MagicBrowse
Hermes | nuanu-ai/skills tap | MagicPay (Hermes drives its own browser)
Manus / other agents | CLIs plus persistent instructions | CLI + instructions

## Install

Install the MagicPay skill first. The skill carries the setup rules, CLI repair instructions, MagicBrowse handoff behavior, and top-up guidance for first-time setup.

```ts
npx skills add MercuryoAI/skills --skill magicpay --global --yes --copy
```

## Setup Command

After install, the agent should verify `magicpay --help` and run `magicpay setup next`. The returned `instructions` field is the setup plan; agents should follow it directly instead of maintaining a separate state mapping.

```ts
magicpay --help
magicpay setup next --intent landing --platform <runtime> --agent-name "<runtime> Agent" --api-url https://durcottggsiesxxqzvbb.supabase.co/functions/v1/api --env production
```

## Runtime Rule

The agent should browse and reason normally until it reaches login, identity, payment, confirmation, or CAPTCHA. At that point it should stop and call the MagicPay path instead of typing Memory values. OpenClaw and Hermes should prefer their native page-control tools when those tools can drive the same browser process; MagicBrowse remains the fallback browser controller.

## Related

- Connect An Agent: https://magiccard.ai/docs/guides/connect-agent
- Claude App: https://magiccard.ai/docs/integrations/claude
- ChatGPT App: https://magiccard.ai/docs/integrations/chatgpt