Individual skill
northstar-payer-ops-json
Solve Northstar Health Plan payer-operations tasks that require querying the shared task environment and returning structured JSON for utilization management authorizations, pharmacy appeals and assistance intake, payment-integrity claim repricing, peer-to-peer summaries, and service-margin queues. Use when the task mentions Northstar, payer operations, UM, appeals, claims, P2P, margin queues, an answer_template.json contract, or the SQL endpoint.
experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_014/fewshot/naive/fewshot_attempt_01/SKILL.md
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.
- agent Repository topic
- ai Repository topic
- benchmark Repository topic
- llm Repository topic
- self-evolving Repository topic
- self-learning Repository topic
- skills Repository topic
- legal Derived category
- operations Derived category
- data Derived category
- data-databases Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 9,265 bytesSKILL.mdcore · 9,265 bytesSKILL.mdcore · 9,265 bytesSKILL.mdcore · 9,265 bytesreferences/northstar-data-map.mddoc · 5,232 bytes
Read excerpt
# Northstar Payer Ops JSON
## Core Workflow
1. Read the user prompt, `input/payloads/task_context.json`, and `input/payloads/answer_template.json` before querying.
2. Treat the answer template as the output contract. Return exactly one JSON object, with no markdown or explanatory prose.
3. Use only the task environment business endpoints and SQL endpoint. Do not inspect environment source files, database files, generated data, manifests, setup scripts, judge APIs, test answers, or unrelated local files.
4. Resolve the target identifiers from the prompt/context: case ID, appeal ID, claim ID, queue ID, row IDs, reporting date, and reporting period.
5. Query narrowly for records tied to those identifiers, then join outward by stable IDs such as `case_id`, `member_id`, `plan_id`, `policy_id`, `claim_id`, `appeal_id`, and row IDs.
6. Compute fields from current environment records. Do not infer from record names alone when table fields, criteria rows, documents, or benchmark rows provide the value.
7. Build `basis_audit` last from the evidence that actually controlled the output.
8. Validate the JSON against the template: required keys, enums, nullability, ordering, numeric precision, and no extra fields when disallowed.
For endpoint syntax, table names, and query patterns, read [Northstar data map](references/northstar-data-map.md) when working a task.