Menu

Individual skill

northstar-payer-ops

0upvotes

Structured JSON workflows for Northstar payer-operations tasks in the shared environment. Use when a prompt asks for an authorization summary, appeal and assistance disposition, claim repricing packet, peer-to-peer summary, or margin queue report that must be answered as one schema-valid JSON object.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_014/fewshot/fewshot_attempt_01/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, `input/payloads/task_context.json`, and `input/payloads/answer_template.json` first.
2. Identify the task family from the template keys.
3. Use the base URL and bearer token from the task context or prompt.
4. Query the live Northstar environment with `POST /sql/query`; use business endpoints when they expose the needed record directly.
5. Build the answer only from live records plus the task memo for scope and dates. Treat the memo as a locator, not as evidence.
6. Follow the template exactly. Preserve list order rules, enum spellings, number precision, and date formats. Emit one JSON object only.
7. Write `basis_audit` from the records that directly controlled the result. Put controlling records first, then gaps, stale records, or exclusions.

## Shared Rules
- Prefer current clinical, appeal, or benchmark records over stale exports or old schedules.
- Keep `null` for absent modifiers.
Back to top