Agent Skill

The official Guapocado Agent Skill gives compatible coding agents the product context and workflow they need to build, review, and troubleshoot a Guapocado integration.

Instead of asking an agent to reconstruct the billing model from scattered API examples, install the skill once:

npx skills add https://github.com/guapocado/guapocado --skill guapocado

The installer detects supported coding agents and adds the skill to the current project. To make it available across projects, install it globally:

npx skills add https://github.com/guapocado/guapocado --skill guapocado -g

The skill follows the open Agent Skills format and works with Codex and other compatible coding agents. Its source is public at skills/guapocado so you can review the exact instructions before installing it.

What the Skill Adds

The skill teaches an agent to:

• Inspect your framework, package manager, authentication model, and existing billing code before making changes.
• Choose the stable user, organization, team, workspace, account, or project ID that should become the Guapocado customerId.
• Model access with the correct feature, meter, or limit primitive.
• Select the server SDK, React, Better Auth, Hono, Supabase, or raw HTTP path that fits the existing application.
• Start with the managed edge API and choose a local read model only for a concrete latency, availability, or reporting requirement.
• Keep server keys and billing mutations on trusted server paths.
• Work in test first, preview remote changes, and require approval before signup, authentication, config pushes, or live-mode actions.
• Retrieve current documentation and installed package types instead of relying on a version frozen into the skill.

The skill is procedural guidance. It does not contain credentials, grant access to a Guapocado account, bypass code review, or make production changes merely because it is installed.

Example Prompts

Invoke it explicitly with $guapocado when you want the agent to apply the full integration workflow:

Use $guapocado to add organization billing to this Next.js app. Model Pro as a
monthly subscription with SSO, 10 seats, and 40,000 AI credits.

Use $guapocado to review this billing.config.ts and find places where the app
trusts a browser-provided customerId.

Use $guapocado to add usage accounting to this queue worker. Make retries
idempotent and refund credits if the downstream generation fails.

Use $guapocado to decide whether this Hono app needs the managed edge API or a
local read model. Implement the smallest safe option.

You can also ask naturally—compatible agents may load the skill automatically when the request clearly involves Guapocado.

From Repository to Test Workspace

A typical agent-assisted integration still keeps you in control:

1. The agent inspects the repository and proposes a billing identity, primitives, packages, and deployment mode.
2. It creates the local config and application changes, then runs the project’s formatter, typecheck, and focused tests.
3. If the project has no credentials, it may offer agent-native signup. The agent must ask before creating the claimable test workspace.
4. It previews the remote config with guap plan --test.
5. It asks before guap push --test, and it does not target live unless you explicitly request and review that action.

This boundary matters: the skill speeds up the product and integration work without turning “help me add billing” into an unreviewed production mutation.

Keep It Current

Update the installed skill from its public source:

npx skills update guapocado

The skill uses llms.txt as the map to current Guapocado documentation. The two surfaces have different jobs:

• The Agent Skill provides workflow, decision rules, and safety guardrails.
• llms.txt tells an agent which current documentation page to retrieve for a specific API, framework, or billing concept.

For a manual integration, continue with the Quickstart. For an agent-created test workspace, read Agent-native Signup.