Menu

Individual skill

northstar-payer-operations

0upvotes

Use when the task involves Northstar Health Plan payer operations — prior authorization, utilization management review, pharmacy appeals, payment integrity claim repricing, peer-to-peer clinical review, or UM-finance margin analysis. Always use this skill when the user references Northstar, a payer-operations environment, an authorization case, an appeal, a claim repricing, a P2P review, or a therapy margin queue, even when the domain terminology is partial or the task is framed as a JSON-structured determination, correction packet, or queue summary.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_014/fewshot/cc/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

Solve Northstar Health Plan payer-operations tasks by querying the shared
HTTP + SQL environment and returning a single JSON object that conforms to
the provided answer template.

## First steps — always do these

1. **Read the three task input files**:
   - `input/prompt.txt` — the business request in prose.
   - `input/payloads/task_context.json` — the target business id, requester
     role, reporting date, and any domain-specific hints under `local_memo`
     or a similar key.
   - `input/payloads/answer_template.json` — the exact required JSON shape.
Back to top