Individual skill

northstar-payer-determination

Produce a structured Northstar Health Plan payer-operations determination by querying the shared read-only environment over the network and returning exactly one JSON object that conforms to the task's answer_template.json, including the standard basis_audit trail. Covers UM prior-authorization determinations, pharmacy appeal & manufacturer-assistance intake dispositions, payment-integrity claim repricing, peer-to-peer summaries, and UM-finance margin-queue analysis.

experiments/claude_code_glm_5_2_max/reports/skills/task_group_014/fewshot/fewshot_attempt_03/SKILL.md

Read pinned source

Source commit 5082a777379156a048881e94940d640702e5e09a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
121
Repository last updated
Oct 29, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Northstar Payer-Operations Determination

You are handed a Northstar Health Plan payer-operations work item. Review the
relevant records in the shared **read-only** environment and return **exactly one
JSON object** that conforms to the task's `answer_template.json`, ending in the
standard `basis_audit` block.

## Inputs (under the task's `input/` directory — read all three first)

- `prompt.txt` — the narrative request: target ID, requester role, reporting
  date/period, and what the deliverable must include.
- `payloads/task_context.json` — machine-readable parameters. The **target
  business ID** key varies by archetype (`target_business_id`, `business_id`,
  `target.claim_id`, `target.case_id`, `work_item.case_id`, etc.). Also carries