SKILLEMALL.ai

AC prior-auth-review-skill

Automate payer review of prior authorization (PA) requests. This skill should be used when users say "Review this PA request", "Process prior authorization for [procedure]", "Assess medical necessity", "Generate PA decision", or when processing clinical documentation for coverage policy validation and authorization decisions.

FreedomIntelligence/OpenClaw-Medical-Skills Agent Skills author: FreedomIntelligence 7 files body ≈ 3 160 tokens Open the sourcegithub.com↗ analyzed 14 h ago

Automate payer review of prior authorization (PA) requests.

As a process C 51/100 · Has gaps — References files that are not bundled: assets/sample/

AnalyzerAI and agentsWriting and documentstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
95/100
safety, quality, tests
Safety 60%
100
Quality 40%
87
Run on models
none yet
Process rating
C
51/100
Has gaps
References files that are not bundled: assets/sample/
Tools and files w 18
0
Result and completion w 14
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: assets/sample/

Process rating: all ten parameters 51/100

Will not run. References files that are not bundled: assets/sample/
  • 0Tools and files. 1 referenced file(s) missing: assets/sample/
  • 0Result and completion. Does not say what the result is
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 85Steps. 121 steps, 1 vague phrases
  • 100Failures and branches. 4 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3160 tokens
  • 100Running it twice. Mutating operations check current state
  • low 10 top-level sections: this looks like several domains in one skill

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 4 example trigger phrases
  • +3Description length 327: enough signal without eating the budget
  • +4Structure: 26 headings
  • +3Step-by-step instructions: 121 items
  • +4Has examples (6 code blocks)
  • +4Reference files are cited in the instructions (3 of 5)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.