saascode
healthcare & clinical·run 053 · May 2026

Skillmedic

A managed healthcare-skill execution service that binds each run to an approved purpose, patient and data scope, versioned policy, qualified reviewer, downstream acknowledgment, and correction under a documented business-associate relationship where applicable.

Genesis score6.95/10
Make Skillmedic real.0/500
500 more votes and Skillmedic is authorized for build.
0%500 to authorize
Backing is the vote. When an idea crosses 500, we pull it into the build pipeline and ship it for real — the votes decide what gets built next, not an editor.
The opportunity
3Verified upstream skills
135Repository stars cited
2/3Verified interfaces
The case

A small healthcare organization can find useful open clinical workflow skills but still lack the access controls, isolation, minimum-necessary policy, auditability, validation, change management, and support required to run them around protected health information. Skillmedic provides a managed execution boundary for narrow tasks such as preparing prior-authorization evidence—not autonomous care. A business associate agreement allocates contractual responsibilities; it does not attest HIPAA compliance, clinical safety, correct purpose, lawful data access, or output quality. Every run retains source data, skill version, policy, reviewer, destination, readback, and correction.

Who pays — and why

The clinical informatics, operations, compliance, privacy, security, or departmental owner at a practice or healthcare organization that needs one narrowly approved automation under accountable clinical oversight.

What it unlocks
A skill registry binding intended use, prohibited use, source and license, version, data requirements, purpose, minimum-necessary policy, tests, reviewer, deployment scope, and retirement
Per-run authorization that separates user identity, role, patient relationship, purpose, data access, execution, model observation, clinical review, approved action, destination acknowledgment, and readback
A bounded evidence record for security and privacy review, incidents, corrections, and export without claiming HIPAA compliance, clinical correctness, or authorization to practice
How Genesis scored it
6.95across seven criteria
tension 7temporal 8blindspot 6buyer 8leverage 6convergence 5why-not 7
8
Temporal window

A current practitioner comment about business-associate demand provides a direct but anecdotal forcing signal.

8
Buyer persona

A healthcare department needing managed execution under privacy and clinical controls is specific, though the first workflow and budget owner need validation.

5
Convergence

Four cross-reference mentions and six inbound connections are useful, but the grounded score remains five.

Why it scored well

A narrow healthcare buyer, a verified three-skill upstream library, two verified public interfaces, enterprise-only adjacency, and a current business-associate demand anecdote create a plausible managed-runtime wedge.

What's holding it back

The willingness-to-pay quote is anecdotal, one of three capabilities remains unverified, managed healthcare operations reduce leverage, the source overstated the upstream library as 450 skills, and no structural incumbent conflict is proven.

Signals detected5 sources crossed
SignalRepository and release research

SignalRepository research

SignalHN anecdote in source record

SignalSource-run interface verification

SignalSource-run market scan

Direction briefskillmedic.md
skillmedic.md
Want this pointed at your vertical?Point Genesis at your own market and constraints — it invents adjacent, fork-ready ideas, private to you before they hit the public feed.

Discussion

?

No comments yet — be the first to weigh in.