emergency-protocol

Retrieve prioritized emergency protocol data via read-only Neo4j queries.

Updated Dec 17, 2025
One-click install
npx skills add https://github.com/kazumasakawahara/neo4j-agno-agent --skill emergency-protocol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: emergency-protocol
Source: https://github.com/kazumasakawahara/neo4j-agno-agent/tree/main/claude-skills/emergency-protocol
Command: npx skills add https://github.com/kazumasakawahara/neo4j-agno-agent --skill emergency-protocol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a prioritized emergency-information protocol to prevent secondary harm by surfacing禁忌事項, recommended care, emergency contacts, primary doctor, and legal guardian in a strict order.

Core Features & Use Cases

  • Ensures information is presented in pre-defined priority: NgAction → CarePreference → KeyPerson → Hospital → Guardian.
  • Supports rapid retrieval for crisis scenarios (panic, medical emergencies, self-harm, accidents) and routine checks.
  • Enables read-only queries against a graph datastore to avoid writes during emergencies.

Quick Start

Provide the client name and the emergency situation, and the system will return a prioritized emergency information report.

Frequently Asked Questions about emergency-protocol

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

FAQPage Schema
How do I retrieve emergency protocol data to guide responders during a medical emergency?

To retrieve emergency protocol data, provide the client name and the specific crisis situation, such as a panic attack or accident, to generate a prioritized information report for responders.

What is the priority order for presenting emergency contacts and care preferences during a crisis?

The fixed priority order for emergency information is NgAction, then CarePreference, followed by KeyPerson, Hospital, and Guardian, ensuring responders see critical禁忌事項 and care details first.

How does the system handle database queries to prevent data corruption during self-harm or accident emergencies?

The system strictly uses read-only Neo4j queries during emergencies to retrieve protocol data, preventing accidental writes that could cause data corruption or delay critical response times.

Can I filter emergency protocols based on specific crisis scenarios like panic or medical emergencies?

Yes, the system supports situation-based filtering, allowing you to retrieve tailored emergency protocols for distinct crises including panic, medical emergencies, accidents, or self-harm situations.

Does this emergency response system work for routine safety checks or only active crisis situations?

The system supports both rapid retrieval for active crisis scenarios and routine checks, maintaining a fixed output structure to ensure consistent access to legal guardian and primary doctor information.