Generate escalation

Skill Ibraheemolasupogit/google-adk-healthcare-pathway-escalation-agent/skills/generate_escalation

A secure Google ADK multi-agent system for synthetic NHS pathway assessment, MCP-based evidence retrieval, guardrails and human-in-the-loop escalation review.

Install

npx -y skills add Ibraheemolasupogit/google-adk-healthcare-pathway-escalation-agent --skill generate_escalation

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.5 KB, as published. Nobody here has run it

Generate Escalation Skill

Purpose

Generate a structured operational escalation draft from validated pathway assessment and evidence.

When To Use

Use to generate a structured operational escalation draft from validated case, assessment, evidence and action inputs.

When Not To Use

Do not use to submit escalation, provide clinical advice, or override deterministic values.

Inputs

Synthetic case, deterministic assessment, retrieved evidence and recommended actions.

Outputs

Structured draft sections, assumptions, warnings, review status and human_review_required=true.

Dependencies

Case Data, Pathway Rules and Policy Evidence MCP servers plus deterministic assessment services.

Deterministic vs Model Components

Numerical and status values are deterministic. Narrative organisation may be model-generated but must preserve values.

Failure Conditions

Invalid assessment, unsupported evidence, prohibited clinical language, failed review validation.

Example Invocation

python -m app.main run-skill --skill generate_escalation --case-id SYN-CANCER-2WW-001

Evaluation Criteria

Required sections present, no submission claim, human review pending, deterministic values preserved.

Current Limitations

No human approval UI and no autonomous submission.

Safety Requirements

Do not autonomously send or finalise escalation.
Avoid clinical diagnosis or treatment recommendations.
Include unsupported-claim checks.
Require human approval before finalisation.

Gives 0 of the 12 instructions most incident response skills give

Counted across 224 of the 224 authors here whose files we hold, read 2026-08-06

Conduct a blameless postmortem within 48 hoursin 24 of 224, across 14 files
perform root cause analysis using five whysin 24 of 224, across 20 files
write a blameless postmortemin 22 of 224, across 19 files
Update stakeholders every 15 to 30 minutesin 19 of 224, across 9 files
assign an owner and due date to every action itemin 18 of 224
Classify incident severity within 5 minutesin 17 of 224, across 7 files
Create a post-mortem documentin 17 of 224, across 14 files
Assign all action items with deadlinesin 14 of 224, across 6 files
Implement immediate mitigation prioritizing user restorationin 13 of 224, across 3 files
assign one incident commanderin 12 of 224
Stop and ask for clarification if inputs are missingin 10 of 224, across 2 files
Escalate earlyin 10 of 224, across 2 files

Said here and by no other author read

preserve deterministic numerical and status values
set human_review_required to true
include unsupported-claim checks
generate structured draft sections
output assumptions and warnings
output a pending review status

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.