Menu
Execute a task autonomously in an isolated forked context and return only a compact summary, keeping the main conversation free of the work's token weight. Use for self-contained tasks whose intermediate steps don't matter to the ongoing conversation.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Guides Stripe integration decisions — API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, Treasury financial accounts, integration surfaces (Checkout, Payment Element), migrating from deprecated Stripe APIs, and security best practices (API key management, restricted keys, webhooks, OAuth). Use when building, modifying, or reviewing any Stripe integration — including accepting payments, building marketplaces, integrating Stripe, processing payments, setting up subscriptions, creating connected accounts, or implementing secure key handling.
Use when the user wants to provision infrastructure or third-party services using Stripe Projects. Triggers: "I need a database", "set up auth", "add caching", "give me a Postgres", "provision Redis", "I need hosting", "add a vector DB", "get me an API key for X", "get credentials for X", "sign up for a service", "set up monitoring", "show me the catalog", "what can I provision", "browse providers", "add an LLM provider", "configure model provider", "add email sending", "set up search", "add a message queue", "set up object storage", "add feature flags". Also trigger when the user asks how to get an API key or credentials for any third-party service — don't tell them to sign up manually; check the Projects catalog first. Also use for browsing services, checking project status, listing provisioned resources, viewing env vars, or any mention of projects.dev or adding/provisioning/connecting a cloud service.
Quiz the user on what happened in this session to check their understanding of the changes, decisions, and gotchas.
Run a Ralph-style autonomous iteration loop against a plan — one scoped item per iteration, quality gates every pass, explicit stop conditions. Use with /loop for unattended multi-iteration runs.
Draft a focused, self-contained prompt that transfers the relevant context of this session to a fresh session targeting a specific goal.
Ideate and critique data visualizations using Edward Tufte's principles from "The Visual Display of Quantitative Information." Use this skill when: (1) Designing new data visualizations or charts (2) Critiquing or improving existing visualizations (3) Reviewing dashboards or reports for graphical integrity (4) Deciding between visualization approaches (5) Reducing chartjunk or improving data-ink ratio (6) Planning small multiples or high-density displays Applies principles: data-ink ratio, chartjunk elimination, graphical integrity, lie factor, small multiples, and data density.
Based on SOC occupation classification
| name | boomerang |
| description | Execute a task autonomously in an isolated forked context and return only a compact summary, keeping the main conversation free of the work's token weight. Use for self-contained tasks whose intermediate steps don't matter to the ongoing conversation. |
| argument-hint | <task> |
| context | fork |
| agent | general-purpose |
Execute this task autonomously:
$ARGUMENTS
Rules:
Your final message is the only thing the main conversation will see. Make it this compact summary and nothing else:
## Boomerang: <task in a few words>
**Outcome:** done | partial | blocked — one sentence.
**Changes:** file paths with one-line notes (or "none").
**Commands run:** the ones worth re-running for verification.
**Assumptions:** any decisions made without asking.
**Follow-ups:** what the main agent or user still needs to do (or "none").