Handles US prior authorisation and claim denials: payer requirement lookup, request packets, appeal letters and a denial tracking log. Use when: Generate formatted prior auth request packets for US payers; Classify denial codes into administrative or medical necessity routes; Draft structured first-level insurance appeal letters.
66%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./plugins/nex-business-operations/skills/nex-medical-billing-priorauth/SKILL.mdThe canonical home for this skill is nex-medical-billing-priorauth in NexaiGuy/nex-ai-skills
Free skill by Nex AI. This file is the public guide from Agensi. Scripts, extension source, and templates from the original package are not in this folder.
US payers only. Payer policies change constantly, so verify the current medical policy before submitting. Output is a working draft for a billing specialist or clinician to review, not clinical or legal advice.
Request
Draft a first-level appeal for patient John Doe, Member ID 12345, for a denied CPT 64493. The payer says it lacks medical necessity, but the notes show he failed PT for 6 weeks.
Result
Appeal Letter: Level 1 Patient: John Doe (ID: 12345) Denied Service: CPT 64493 Basis: Medical Necessity
Summary: The provider documents the patient failed 6 weeks of conservative physical therapy (see notes dated 10/01-11/15) prior to this request. We request a reversal of this denial.
No. This skill only uses codes and clinical findings provided by the practice to ensure accuracy and compliance.
It helps classify if a denial is administrative or based on medical necessity and routes the workflow accordingly.
The skill creates a structured tracking log to monitor pending authorizations and deadlines for every case.
Built by Nex AI. More skills, including the paid catalog: https://www.agensi.io/creators/ch1n4-g3nd4x
NexaiGuy/nex-ai-skills
4034c84
Canonical home
since Nov 1, 2026
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.