MedSkills
Prior-auth packets, denial appeals, and eligibility checks — packaged as skills your billing team can verify before they run.
Listings are curated, not crowdsourced. Each entry publishes who reviewed it, against what, and when. PHI never touches this platform.
Browse by what it does for your claims
Filter by vertical. Each skill carries a visible vetting record — badges aren't bought, they're earned in review.
We replaced ratings with a review record.
A curated catalog has no crowd to generate stars. So the differentiator is the trail: who reviewed it, against what, and when.
Source check
Skill is first-party or submitted by a known partner. Provenance and maintainer are recorded — no anonymous publishing.
Compliance review
Reviewed for HIPAA handling, PHI boundaries, and a documented Business-Associate posture before listing.
EHR / payer test
Where applicable, run against real EHR/PM sandboxes and payer transaction sets (270/271, 837, 835).
Published record
The vetting log lives on the skill page — reviewer, date, scope. Re-reviewed when the skill or rules change.
The PHI boundary, stated plainly
MedSkills is a catalog, not a runtime. We store skill descriptions, metadata, and packages — never patient data. Skills execute inside your environment, against your EHR and payer connections. Protected health information never touches this platform.
New vetted skills, as they land.
We add skills only after they clear review — so the list moves slowly and deliberately. Get a note when a new one is published or a vertical opens up.
Stop hand-building the same prior-auth packet twice.
Install a vetted skill, point it at your stack, and keep the revenue cycle moving. Claude-first today — the metadata is built to travel.