AI Blocks › Build and ship software
Error and recovery message writer
Describe a system and its operators. Get what the alarm says, what the person decides and how it recovers.
Error and recovery message writer is a free AI skill for the job "Build and ship software". Give the instructions to an AI assistant that supports the required files and tools, then review its output.
Free · No account · Made by AI Blocks · Level: advanced · Thinking: high
What it does
Plans often stop at "this mistake will not happen". Under pressure, with tired people and little time, it does. When it does, the system either carries on in a bad state or stops everything, and the person has no clear choice. This skill lists the mistakes people say cannot happen and treats each as likely. It decides how the system detects each one while running, then designs a safe restart point so key jobs keep going. It writes the alarm to interrupt normal work and name the decision, go or no-go. It makes sure the operator and the control room see the same message, adds a plain warning where the system refuses to block, and sets up a review by kind of error that changes the method that let it in.
You give it
- The system or process, and who operates it
- Findings from a readiness check or a past incident (optional)
- The mistakes people say cannot happen (optional)
You get
- A list of can't-happen mistakes with how each is detected and what the system does
- A safe restart point and the jobs kept running
- The alarm text, with the decision it asks for
- A plan to review errors by kind
Use it when
- You run something where a mistake costs a lot and people work under pressure.
- Your alerts are noisy and nobody knows what to do when one fires.
- A readiness check found joins that could fail and you need to plan for them.
How to use it
- Start a chat with the skill. Open it if you added it to your AI, or copy it and paste it in.
- Describe the system, who operates it and what they see. Paste the readiness findings if you have them.
- Add every "that can never happen" you have heard from the team.
- Read the alarm texts out loud to someone who runs the system and fix the words they trip on.
- Test the restart point on a small scale before you rely on it.