Individual skill

northstar-payer-ops-json

Solve Northstar Health Plan payer-operations tasks that require a strict JSON answer from the shared task environment, including utilization-management determinations, pharmacy appeals and assistance intake, payment-integrity claim repricing, peer-to-peer outcomes, and UM-finance margin queues. Use when a prompt mentions Northstar, payer operations, a SQL/query endpoint, case/claim/appeal/queue records, answer_template.json, task_context.json, criteria results, source precedence, basis_audit, or returning JSON only.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_014/fewshot/opencode/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 Operations JSON

Use this skill to produce one schema-conforming JSON object for Northstar payer operations tasks. The stable challenge is not writing prose; it is retrieving the right operational records, applying the correct source-precedence rule, calculating/classifying fields exactly, and preserving an audit trail.

## Operating Boundary

- Use only the environment endpoints and credentials supplied by the task prompt or payload. Do not inspect task-environment source files, database files, generated data files, manifests, or setup scripts.
- Treat `input/payloads/answer_template.json` as the output contract. Read it before calculating final fields.
- Treat `input/payloads/task_context.json` as the scoped work order. Use target IDs, reporting dates/periods, queue row IDs, requester role, and any local finance or routing definitions from it.
- Return JSON only. Do not include Markdown fences, comments, or explanatory text outside the object.
- Do not copy fields from a local memo when environment records disagree. The memo scopes the task; current operational records supply the facts.

## One-Pass Workflow
Back to top