Medical Billing & Revenue Cycle
v1.0.0Analyze medical billing workflows, identify revenue leaks, optimize claims, reduce denials, and improve revenue cycle KPIs for healthcare practices and billi...
⭐ 0· 431·1 current·1 all-time
by@1kalin
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (medical billing & revenue cycle) match the SKILL.md content: coding checks, denial analysis, KPIs, payer contract analysis, compliance, and charge-capture guidance. The README and SKILL.md reference AfrexAI resources which are relevant to the stated purpose. Minor inconsistency: registry metadata lists no homepage/source while the README/SKILL.md include AfrexAI links; this is a provenance gap but not a functional mismatch.
Instruction Scope
SKILL.md instructions are scoped to receiving practice-level inputs (specialty, payer mix, KPIs, problem area) and returning analyses and recommendations. It does not instruct the agent to read local files, environment variables, or call external endpoints beyond the documented AfrexAI links. However, the guidance can involve sensitive billing data; the skill does not include explicit instructions or warnings about PHI handling — users could be tempted to paste patient-level data into prompts, which would be inappropriate.
Install Mechanism
No install spec and no code files — this is an instruction-only skill, so nothing is downloaded or written to disk. This minimizes installation risk.
Credentials
The skill does not request any environment variables, credentials, or config paths. The declared requirements are minimal and proportional to the stated functionality.
Persistence & Privilege
always:false and default model-invocation behavior. The skill does not request elevated or persistent privileges, nor does it attempt to modify other skills or system settings.
Assessment
This skill is internally coherent for medical billing advice and is low-risk from a technical/install perspective. Before installing or using it: 1) Verify the publisher (follow the AfrexAI links and confirm the vendor identity) since registry metadata lacks a homepage; 2) Never paste PHI (patient identifiers, full claims with patient info) into prompts — test with de-identified or synthetic data only; 3) Treat clinical, legal, and compliance recommendations as advisory: have billing, compliance, or legal experts review any operational changes (Stark Law, False Claims Act, payer contract negotiations); 4) If you plan to run the skill autonomously or integrate it into workflows, document and audit what data you send and consider enabling usage restrictions; 5) If you need stronger assurance about provenance or accuracy, ask the publisher for a privacy/data-handling statement and references for the benchmarks and CARC/RARC mappings used.Like a lobster shell, security has layers — review code before you run it.
CPTvk9771v1qvm715jkfrbmmwxftwd81rt13ICD-10vk9771v1qvm715jkfrbmmwxftwd81rt13compliancevk9771v1qvm715jkfrbmmwxftwd81rt13denial managementvk9771v1qvm715jkfrbmmwxftwd81rt13healthcarevk9771v1qvm715jkfrbmmwxftwd81rt13latestvk9771v1qvm715jkfrbmmwxftwd81rt13medical billingvk9771v1qvm715jkfrbmmwxftwd81rt13revenue cyclevk9771v1qvm715jkfrbmmwxftwd81rt13
License
MIT-0
Free to use, modify, and redistribute. No attribution required.