Bytesagain Clinical Brief
v1.0.0Summarize clinical case notes into specialty briefs. Input: raw case notes or lab results. Output: structured specialty brief, differential diagnosis list, k...
⭐ 0· 32·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (clinical brief generation) match the included SKILL.md and the bash script behavior: summarize notes, generate differentials, interpret labs, and format case presentations. No unrelated services or credentials are requested.
Instruction Scope
SKILL.md explicitly instructs running the included scripts/script.sh with command arguments; the script only reads the provided arguments and writes output to stdout. It does not attempt to read other system files or call external endpoints. It will use HOME to create a data directory and may persist files there.
Install Mechanism
No install spec is present (instruction-only with an included script), so nothing is downloaded or installed by the registry. The script is shipped with the skill; no external downloads or package installs are performed.
Credentials
The skill declares no required env vars or credentials (appropriate). The script implicitly depends on standard Unix tools (bash, grep, sed, date, tr, head) and python3 for lab parsing — these tools are not declared in metadata. It also uses HOME to create ~/.local/share/bytesagain-clinical-brief; this is expected but worth noting.
Persistence & Privilege
always:false (default) and it does not modify other skills. The script creates a per-user data directory (~/.local/share/bytesagain-clinical-brief) at runtime which could be used to store state or logs; this is limited but you should be aware it writes to your home directory.
Assessment
This appears to be a straightforward local CLI skill: it runs a bundled bash script that prints structured summaries and runs an inline Python parser for lab values. Before installing/using: 1) Review the script (already included) to confirm nothing networked or unexpected is present — it does not perform network requests in its current form. 2) Consider privacy: the tool processes clinical notes and will write to ~/.local/share/bytesagain-clinical-brief; do not run it on protected health information (PHI) you are not authorized to process, or run it in a controlled/sandboxed environment if you have PHI concerns. 3) Ensure required binaries are available (bash, grep, sed, python3); the skill metadata does not declare these dependencies. 4) Validate clinical output with qualified professionals; the skill itself warns that AI output is for assistance only.Like a lobster shell, security has layers — review code before you run it.
latestvk973sktfjvhzvf79a2japv7r6h848a2s
License
MIT-0
Free to use, modify, and redistribute. No attribution required.