Individual skill

skill

Solve Northstar payer-operations tasks that require reading task_context and answer_template files, querying the shared environment, and returning exact JSON for UM nurse reviews, pharmacy appeals, claim repricing, peer-to-peer summaries, and margin-queue analyses.

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

## Workflow

1. Read the prompt, `task_context.json`, and `answer_template.json` together.
2. Identify the task family, target record IDs, reporting date or period, output contract, and any prompt-specific restrictions on local file inspection.
3. Use only the documented environment endpoints. Prefer `POST /sql/query` for joins, filters, and rollups; use case, policy, document, appeal, rate-schedule, portal, claim, or queue endpoints when they expose the controlling record directly.
4. Treat task-context memos as routing hints, not evidence. Build the answer from current controlling records only.
5. Follow the template exactly. Preserve required key order, nested key order, enum spellings, list ordering rules, and null handling. Round numbers only to the precision requested by the template.
6. Keep the output JSON-only. Do not add markdown, commentary, or extra keys unless the template explicitly allows them.

## Common Task Families

- UM nurse review: resolve case status, authorization details, therapy criteria, evidence documents, and excluded documents.
Back to top