CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nex-medical-billing-priorauth

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.

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/nex-medical-billing-priorauth/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

32%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a marketing readme rather than operational guidance: it describes capabilities and limitations but provides almost no executable structure for building packets, classifying denials, or drafting appeals, and roughly a third of the tokens are promotional or FAQ padding. Section organization is decent, but the actual instruction content is thin.

Suggestions

Replace the promo blockquote, 'Use cases' section, and FAQ with concrete output templates: the required sections of a prior-auth packet and the full structure of an appeal letter (header fields, medical-necessity argument, policy citation, closing).

Add a step-by-step workflow with checkpoints, e.g. verify current payer medical policy → assemble packet with codes and clinical findings → submit; and for denials: classify code → route (corrected claim / reconsideration / formal appeal / peer-to-peer) → draft response → log outcome.

Define the denial tracking log explicitly — its file location, column schema (payer, denial code, reason, route, deadline, status), and update rules — since it is advertised as a core capability but never specified.

DimensionReasoningScore

Conciseness

Several sections are pure padding for a skill file: the 'Free skill by Nex AI' blockquote, the paid-catalog footer link, a 'Use cases' section duplicating the description's triggers, and a three-question FAQ that restates 'What it does'. This is noticeably verbose rather than mostly efficient, fitting the score-2 anchor.

2 / 5

Actionability

The body describes rather than instructs: 'Builds the prior authorisation request packet per payer…' gives no packet structure, appeal-letter template, tracking-log schema, or payer-lookup procedure. The only concrete guidance is the routing taxonomy ('corrected claim, reconsideration, formal appeal or peer-to-peer') and a sketch example, matching the minimal-concrete-guidance anchor.

2 / 5

Workflow Clarity

No step sequence is ever listed; the routing bullets imply a rough classify-then-respond flow with many gaps and no validation checkpoints, fitting the rough-sequence-present-but-poorly-defined anchor rather than the steps-missing anchor.

2 / 5

Progressive Disclosure

The ~54-line body has clear sections, no nested references, and no inlined bulk content, and no bundle files exist to organize. It falls short of a 5 because the body itself states 'Scripts, extension source, and templates from the original package are not in this folder', leaving the structure incomplete with external promo links standing in for real references.

4 / 5

Total

10

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: specific, third-person, with an explicit 'Use when:' clause and a well-defined US prior-auth/denial niche. The main gaps are trigger phrasing framed as actions rather than user intents and a few missing keyword variations.

DimensionReasoningScore

Specificity

The description names multiple concrete capabilities — 'payer requirement lookup, request packets, appeal letters and a denial tracking log' — covering the skill's full capability set, matching the comprehensive-coverage anchor.

5 / 5

Completeness

Both a clear 'what' (four named capabilities) and an explicit 'Use when:' clause are present, but the triggers are phrased as agent actions rather than user situations and omit the denial-tracking capability, so 'when' could be more specific.

4 / 5

Trigger Term Quality

Natural phrases like 'prior auth request packets', 'denial codes', and 'insurance appeal letters' are present, but common variations such as 'pre-auth', the US spelling 'prior authorization', and 'reconsideration' are missing, fitting the good-but-incomplete keyword anchor.

4 / 5

Distinctiveness Conflict Risk

'US prior authorisation and claim denials' with payer-specific triggers carves out a clear niche with distinct trigger phrases and minimal overlap risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

NexaiGuy/nex-ai-skills

Path

skills/nex-medical-billing-priorauth/SKILL.md

Reviewed

Table of Contents

Is this your skill?

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.