Productivity & OperationsSkillAdvancedIn a pack
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 …
- Built from
- Role
- Context
- Task
- Constraints
- Output format
- You fill in
- system and surface
- first observed
- key holders
Written by the PromptCorrectly team© 2026 PromptCorrectly · All rights reserved
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. The .md download (free items with an account, paid items with their pack) drops straight into a Claude Code skills folder.
- Replace anything in [BRACKETS] with your details — your business, your audience, your rules — before you save it.
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.