alirezarezvani/claude-skills / agent-launcher/skills/stage-launch
stage-launch
UnverifiedUse when a managed-agent build sheet is ready to launch ('launch it', 'deploy the agent'). Generates and validates API payloads with payload_generator.py and payload_validator.py and writes a resumable curl script with launch_script_writer.py that uses the user's own key.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 1.0 KB |
| SKILL.md | skill md | 3.4 KB |
| scripts/launch_script_writer.py | script | 4.2 KB |
| scripts/payload_generator.py | script | 4.5 KB |
| scripts/payload_validator.py | script | 6.5 KB |
SKILL.md
View on GitHub---
name: stage-launch
description: "Use when a managed-agent build sheet is ready to launch ('launch it', 'deploy the agent'). Generates and validates API payloads with payload_generator.py and payload_validator.py and writes a resumable curl script with launch_script_writer.py that uses the user's own key."
license: MIT
metadata:
version: 2.11.2
author: Alireza Rezvani
tags: [cma, launch, payloads, curl, byok, api-key-safety, environment, agent, session]
compatible_tools: [claude-code, codex-cli, cursor, antigravity, opencode, gemini-cli]
---
# Phase 2 — Stage → Launch
Turn the build sheet into runnable artifacts, then let the founder launch with
their own key. **No script here touches the network or the key** — the user runs
`launch.sh`.
## Workflow
1. **Generate payloads.**
```bash
python3 scripts/payload_generator.py \
--sheet ./my-agent/build-sheet.json --out-dir ./my-agent
# -> ./my-agent/payloads/{01-environment,02-agent,03-session,04-kickoff}.json
```
Agent toolset → `always_allow`; every MCP toolset → `always_ask` (baked into
the agent payload's `permission_policies`).
2. **Write the launch script.**
```bash
python3 scripts/launch_script_writer.py --out-dir ./my-agent
```
`launch.sh` creates environment → agent → session → kickoff **in order**,
chaining IDs, and **resumes** on re-run (each step skips if its `*.id` file
exists). It reads `$ANTHROPIC_API_KEY` at runtime.
3. **Validate before launch.**
```bash
python3 scripts/payload_validator.py --dir ./my-agent
```
FAIL blocks — especially a `key_leak` finding. Fix and re-run.
4. **Minimal key step (never in chat).** Check the shell first:
```bash
[ -n "$ANTHROPIC_API_KEY" ] && echo "key present" || echo "export ANTHROPIC_API_KEY=... first"
```
Point the founder to platform.claude.com → API keys. **Never print the key to
chat, never write it to a file.**
5. **Launch + watch the first poll.**
```bash
export ANTHROPIC_API_KEY=... # in their shell, not in chat
./my-agent/launch.sh
```
Mark checkpoints with Console deep links. Then `goal_state.py set --phase
grade-iterate` and advance.
## Hard rules (API-key safety)
- **The key never enters chat, a file, a payload, or a log.** `launch.sh` reads it
from the environment; `payload_validator.py` scans for `sk-ant-…` leaks and FAILs.
- **Sequential launch.** environment → agent → session → kickoff. Watch the first
poll foreground before declaring success.
- **Resumable.** Re-running `launch.sh` continues from the last created ID.
## Forcing-question library (recommend + cite)
1. "Is the key in your shell env already?" *Recommend:* check `$ANTHROPIC_API_KEY`
before anything. *Cite:* this SKILL, key-safety rules.
2. "Cloud or self-hosted environment?" *Recommend:* cloud for v0. *Cite:*
cma-primitives.md (environment).
3. "Any MCP server in the payload?" *Recommend:* keep it `always_ask`. *Cite:*
cma-primitives.md (permissions).
4. "Did the first poll return idle/running cleanly?" *Recommend:* watch it
foreground before moving on. *Cite:* cma-primitives.md (session lifecycle).
## Tools
- `scripts/payload_generator.py` — build sheet → 4 ordered API payloads.
- `scripts/launch_script_writer.py` — resumable BYOK curl launcher (no key handling).
- `scripts/payload_validator.py` — pre-launch check + API-key-leak scan.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |