Asi nhero-nurse
Nurse approval email automation for nhero controlled substance slots. Gmail MCP integration with scrambled slot names — nurse sees only slot letters, never medication names. Dual-address routing to mantissa@gmail.com (primary) and ies@plurigrid.com (backup).
install
source · Clone the upstream repo
git clone https://github.com/plurigrid/asi
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/plurigrid/asi "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/nhero-nurse" ~/.claude/skills/plurigrid-asi-nhero-nurse && rm -rf "$T"
manifest:
skills/nhero-nurse/SKILL.mdsource content
nhero-nurse
Nurse approval workflow. Scrambled. Email-automated.
Flow
killdispenser(slot, HOLD) → queue nurse request → Gmail MCP creates draft (from mantissa@plurigrid.com) → Sent to mantissa@gmail.com (cc: ies@plurigrid.com) → Nurse replies APPROVED / DENIED → hero_email_monitor.py parses reply → killdispenser(slot, DISPENSE) or remains HOLD
Privacy
The nurse email contains:
- Slot letter (e.g., "Q")
- Proposed dosage (e.g., "30.0mg")
- Supply assessment
The nurse email does NOT contain:
- Medication name
- Patient identity
- Diagnosis
Email Architecture
| Role | Address |
|---|---|
| Hero registration | |
| Nurse approval TO | |
| Nurse backup CC | |
| Automation FROM | |
Parent
Part of the nhero hierarchy.