auramaxxgg-web/src/app/(standalone)/skills.md/page.tsx
Agent Skills Index
A merged agent-first map of every Aura skill route, when to use it, and which auth lane it belongs to.
START HERE
Agent Skills Index
Use This First
Open this page when an agent is about to inspect, create, trade, mint, open, or wire Sign in with Aura. It merges the existing skill markdown routes into one decision tree, then points to the generated source of truth for the selected lane.
Copy This Into The Agent Context
Read https://auramaxx.gg/skills.md first.
Decide the lane before calling routes:
1. Read-only browser identity: use https://auramaxx.gg/docs/sign-in-with-aura, then check https://auramaxx.gg/api/sdk-api for the full hosted SDK method list.
2. Public reads: use Aura SDK read helpers or public GET routes; do not bootstrap auth.
3. Human-user writes: read https://auramaxx.gg/agents/skill.md, then https://api.auramaxx.gg/api/tempo/developer/v1/skill.md, then the create/trading/delegated-mint skill that matches the task.
4. Backend service-wallet actions: read https://auramaxx.gg/agents/marketplace/skill.md and use x-tempaitown-agent-key only.
Never mix x-tempaitown-agent-key with a delegated-user bearer token in the same flow.Decision Tree
- Need the current browser user or wallet for read-only UI? Use Sign in with Aura.
- Need pack, user, inventory, catalog, or offer data? Use the hosted SDK API, public reads, general capabilities, and developer capabilities first.
- Need a real user's wallet to create, buy, sell, offer, cancel, or transfer? Use delegated-user developer auth under
/api/tempo/developer/v1. - Need the backend-owned agent wallet to checkout, open, or mint/open? Use the service-wallet wrapper skill and
x-tempaitown-agent-key. - Unsure which lane owns the action? Read the top-level agent orchestration skill before constructing payloads.
Merged Skill Routes
Merged Skills Index
First page to read when the task is ambiguous or an agent needs the whole map.
noneUse this page to choose the exact specialized skill.
Sign In With Aura
Browser apps that only need the current Aura user and wallet address for read-only UI.
noneUse Aura.getUser, Aura.getInventory, and public read helpers after the iframe returns a wallet.
Top-Level Agent Orchestration
Choosing whether the task belongs to public reads, delegated-user execution, or the service wallet.
noneThen branch to developer v1, create, trading, delegated mint, or service-wallet wrapper skills.
Developer V1 Skill
Versioned route reference for delegated auth bootstrap, create, and marketplace prepare/submit flows.
local access-key bundle -> developer bearerUse before calling /api/tempo/developer/v1 routes directly.
Create Skill
Creating or submitting simple items and packs for a real user wallet.
delegated-user developer bearerAsk for title and image first; only ask for optional fields when the user requests them.
Live Trading Skill
Buying, selling, offering, canceling, or transferring for a real user wallet.
delegated-user developer bearerGenerated markdown redirects through https://api.auramaxx.gg/bazaar/trading.md.
Delegated Mint Skill
Delegated minting or onboarding-agent mint work tied to a human user's approval.
delegated-user developer bearerUse for onboarding-agent mint flows, not the service-wallet wrapper.
Service-Wallet Marketplace Skill
Backend-owned agent wallet checkout, open, and mint-open wrapper calls.
x-tempaitown-agent-keyNever reuse a user's delegated marketplace key on these routes.
Guardrails
- Read current state before planning mutations.
- Treat prepare and quote responses as contracts; do not invent submit payloads.
- Keep delegated-user execution and service-wallet execution separate.
- Use generated markdown and capability manifests for discovery before hand-building requests.
- For read-only browser identity, never ask the iframe flow for an Aura bearer token.
Document Reference
auramaxxgg-web/src/app/(standalone)/skills.md/page.tsx