Individual skill

northstar-payer-ops-json

Solve Northstar payer operations tasks that require retrieving authorization, appeal, claim, policy, document, rate schedule, P2P, or service-margin records from the task environment and returning a strict JSON object matching an answer_template.json schema. Use for UM determinations, pharmacy appeal intake, payment integrity repricing, peer-to-peer summaries, and payer-service margin queue summaries.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_014/fewshot/codex/fewshot_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 Ops JSON

## Core Workflow

1. Read the prompt, `input/payloads/task_context.json`, and `input/payloads/answer_template.json` before querying. Treat the template as the output contract: exact required keys, allowed enums, ordering, null handling, numeric precision, and whether extra fields are allowed.
2. Use only the task environment endpoints provided in the prompt or context. Do not inspect source files, generated data files, database files, manifests, or setup scripts. If using SQL, post JSON with an `sql` string and the bearer token from the task.
3. Query narrowly by the target business identifiers from the prompt/context. Pull every record type needed to justify the output, not just the record that names the target.
4. Apply the source-precedence rule that matches the business workflow. Use the rule both to decide the outcome and to populate `basis_audit`.
5. Return JSON only. Use JSON numbers for currency/ratios, ISO dates, and `null` when the template asks for null rather than an empty string.

Read [references/northstar-environment.md](references/northstar-environment.md) for table names, join keys, query patterns, and calculation rules.

## Evidence Collection By Workflow