Individual skill

northstar-payer-determinations

Produces a correct structured-JSON determination for Northstar Health Plan payer-operations tasks — UM nurse authorization, pharmacy coverage appeal + manufacturer assistance, payment-integrity claim repricing, peer-to-peer (P2P) summary, and UM-finance margin-queue analysis — backed by records in the shared payer-operations environment. Use whenever a task gives a target business ID, a payer-operations role, a reporting date, and an answer_template.json, and asks you to return one JSON object conforming to that template.

experiments/claude_code_glm_5_2_max/reports/skills/task_group_014/reflect-3/reflect-3_attempt_02/SKILL.md

Read pinned source

Source commit 5082a777379156a048881e94940d640702e5e09a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 11, 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 Determinations

## What these tasks are
Each task gives you:
- `prompt.txt` — the request (your role, the target business ID, the reporting date, what to return).
- `payloads/task_context.json` — target IDs, role, dates, and any domain definitions (finance thresholds, packet items, appeal windows, etc.).
- `payloads/answer_template.json` — the **exact** JSON contract: required fields, types, enum choices, list-ordering rules, numeric precision, and null-handling rules.

The shared payer-operations environment holds the source records (cases, members, plans, providers, clinical documents, policies, criteria, authorizations, appeals, drug trials, assistance screens, claims, claim lines, rate schedules, P2P events, margin rows). Your job is to read the right records, apply the determination logic, and return **one JSON object** matching the template. Output JSON only — no prose, no markdown fence, no comments.

Produce the correct answer in a single pass: read the inputs carefully, derive each field exactly from environment records, and validate every field against the template before emitting JSON.

## Entry workflow (every task)
1. **Read all three inputs fully.** The template is the contract — note every required field, enum choice, list-ordering rule, numeric precision, and null rule before touching the environment.
Back to top