Menu

Individual skill

northstar-payer-ops

0upvotes

Structured JSON disposition and correction packets for Northstar payer-operations tasks. Use when a prompt provides task_context.json and answer_template.json and asks for UM determination, pharmacy appeal, claim repricing, peer-to-peer, or finance queue processing against the shared Northstar environment.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_014/self/self_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
Yes
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

Use this skill to turn a Northstar task context into a schema-matched JSON packet.

1. Read `task_context.json` and `answer_template.json` first.
2. Extract the target IDs, dates, requested work type, environment base URL, token, and memo constraints.
3. Query the shared Northstar environment only. Prefer SQL for joins and filtering; use business endpoints when they expose the needed record directly. Do not inspect local databases, manifests, generated data, or setup scripts unless the prompt explicitly allows it.
4. Gather only the records needed to decide the packet. Pull current case, claim, appeal, authorization, policy, document, P2P, assistance, rate schedule, or queue rows as required by the template.
5. Apply the family-specific playbook in [playbooks.md](references/playbooks.md) before resolving conflicts or gaps.
6. Build JSON that matches the template exactly. Preserve required key order when the template implies one, respect enum spellings and list ordering, use ISO dates, round currency to cents, use `null` for absent modifiers, and return JSON only.
7. Populate `basis_audit` with the precedence label, ordered record trail, controlling record IDs, and exception record IDs.
8. Add no extra keys unless the template explicitly allows them.
Back to top