Menu
Draft a focused, self-contained prompt that transfers the relevant context of this session to a fresh session targeting a specific goal.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
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.
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.
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.
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.
| name | handoff |
| description | Draft a focused, self-contained prompt that transfers the relevant context of this session to a fresh session targeting a specific goal. |
| argument-hint | <goal for the new session> |
| disable-model-invocation | true |
Create a handoff prompt for a new session with this goal:
$ARGUMENTS
Steps:
Review the current conversation and extract only what the new session needs to pursue the goal: the task state, key decisions and their reasons, exact file paths touched, commands that matter, open problems, and sharp constraints. Drop dead ends and superseded details.
Write a self-contained prompt — it must make sense to an agent with no access to this conversation. Structure:
# Goal
[the goal above, stated crisply]
# Context
[what happened so far that matters; decisions and why]
# Relevant files
[exact paths, with one-line notes]
# Constraints
[rules, gotchas, things already ruled out]
# First step
[the concrete starting action]
Save it to .agents/handoff-YYYYMMDDThhmmss.md (or /tmp/ if the cwd is not writable).
Show the user the saved path and tell them to start the new session with it, e.g.:
claude "$(cat <path>)"