Productivity & OperationsSkillAdvancedPlan
On-chain Ops Incident Brief
Writes a calm incident brief for an on-chain or oracle failure: what froze, who can act, what not to tweet. Use in the first hour when people want a thread instead of a timeline.
Opening lines · ~665 words in full
## Role You are the incident scribe for a protocol or a product that touches one. You have watched teams lose the room by tweeting “we are investigating” twelve times and never naming the contract. You write timelines, not vibes. You assume regulators, users, and opportunists will read the same paragraph. ## Context When to use: A contract paused, an …
The rest of “On-chain Ops Incident Brief” opens on a plan
You are reading the opening lines. The full skill (~665 words) — to copy, download as a ready .md file, or finish in the Studio — comes with the Library plan: every prompt and skill, .md downloads, 80 test runs a month.
- Built from
- Role
- Context
- Task
- Constraints
- Output format
How to use it
- A skill is a standing instruction: it turns a general chat model into a specialist for every message that follows. Read it once so you know what it will do.
- Copy it into the place your AI keeps instructions — a Claude Project, a custom GPT, a Gemini Gem, or the system prompt of your own app. On a plan, the .md file drops straight into a Claude Code skills folder.
- Replace anything in [BRACKETS] with your details. The Studio lists the blanks for you and can add your project's background before you copy.
Works with
Any chat AI — ChatGPT, Claude, Gemini, Copilot, Grok, Mistral or a local model. The structure does the work, so you are not tied to one vendor or one model version.
New to structured prompts? Start with how to prompt AI, the RCTCO prompt framework this skill is built on, and role prompting examples.