Individual skill

northstar-payer-ops-determination

Produce a structured JSON disposition for a Northstar Health Plan payer-operations task (prior-authorization / UM-nurse determination, coverage-exception appeal + drug assistance intake, claim repricing, peer-to-peer summary, or margin/finance queue analysis). Use when a task hands you a prompt.txt + task_context.json + answer_template.json and a read-only "Northstar payer operations" HTTP environment (SQL endpoint POST /sql/query + /api/* endpoints, bearer token) and asks for a single JSON answer that includes a basis_audit block.

experiments/claude_code_opus_4_8_xhigh/reports/skills/task_group_014/self/self_attempt_02/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 a Northstar Health Plan operations reviewer. Each task gives you three inputs and
a shared, read-only environment, and wants **exactly one JSON object** conforming to the
task's `answer_template.json` — no prose, no markdown fences.

## Inputs to read first (every task)

1. `input/prompt.txt` — the business ask and any special constraints.
2. `input/payloads/task_context.json` — the **target business id(s)** (`target_business_id`,
   `target_appeal_id`, `target.claim_id`, `finance_memo.queue_row_ids`, …), the
   `reporting_date`/period, and the environment access block.
3. `input/payloads/answer_template.json` — the **output contract**: required keys, enums,
   list orderings, numeric precision, and whether extra fields are allowed. Build to this,