Incident reporting assistant

Converts patient-safety incident accounts into factual, blame-free structured reports.

49|11|Updated Jul 31, 2026
One-click install
npx skills add https://github.com/vstorm-co/agenticos --skill incident-reporting-assistant-vstorm-co
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Incident reporting assistant
Source: https://github.com/vstorm-co/agenticos/tree/main/backend/app/core/catalog/skill_gallery/healthcare/incident-reporting-assistant
Command: npx skills add https://github.com/vstorm-co/agenticos --skill incident-reporting-assistant-vstorm-co

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Patient-safety incident reports are often written under stress, mixing facts with blame, speculation, and missing details. This Skill turns a raw account of an incident into a complete, factual, blame-free report that investigators can rely on months later. ## Core Features & Use Cases - Structured collection order: Captures what happened, when, where, who was involved by role, resulting harm, immediate actions, and mitigating factors. - Blame-free register: Strips attributions of cause, blame, and intent so the report contains only facts and observations. - Near-miss coverage: Treats incidents that reached no patient with the same structure, explicitly recording that no harm occurred. - Gap identification: Finishes every report with what the account does not establish, guiding the investigator's follow-up questions. - Use Case: A charge nurse describes an infusion running at 40 ml/h against a prescribed 10 ml/h; the Skill produces a factual report noting roles, times, and actions taken, without naming individuals or grading severity. ## Quick Start Use the incident reporting assistant to write up this patient-safety incident account as a factual, blame-free report.

Frequently Asked Questions about Incident reporting assistant

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a patient-safety incident report?▼

Collect facts in a fixed order: what happened, when with times, where, who was involved by role, resulting harm, immediate actions, and mitigating factors. Record only facts and observations, and finish by listing what the account does not establish.

How to keep an incident report free of blame?▼

Write in a facts-and-observations register only, removing every attribution of cause, blame, and intent. For example, state that the infusion ran at 40 ml/h against a prescribed 10 ml/h rather than saying a nurse was rushing.

Should near misses be reported as incidents?▼

Yes, an incident that reached nobody is still an incident and the cheapest kind to learn from. Write it up with the same structure and state explicitly that no harm occurred.

What should an incident report never include?▼

Never name individuals, speculate about cause, or grade severity. Identifying people and judging seriousness are decisions reserved for the reviewer and the formal investigation.

Why does an incident report need a gaps section?▼

The gaps section records what the account does not establish, so the investigator knows what to ask next rather than assuming missing details were not relevant. It prevents silent assumptions from shaping the investigation.