Individual skill

northstar-payer-operations

Northstar Health Plan payer operations task solver. Use when working on Northstar utilization management determinations, pharmacy coverage appeals, payment integrity claim repricing, peer-to-peer summaries, or therapy margin queue analysis. Connects to the shared Northstar payer environment (HTTP API + SQL endpoint) to gather case records, policies, documents, rate schedules, appeals, and service margin data for structured determinations.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_014/fewshot/codex/fewshot_attempt_01/SKILL.md

Read pinned source

Source commit 5082a777379156a048881e94940d640702e5e09a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 11, 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 connecting to the shared environment, querying business records, and returning structured JSON determinations.

## Connection

Every Northstar task uses the same environment. See [environment.md](references/environment.md) for the base URL, SQL endpoint, and bearer token. Read that file before making any network call.

## General Workflow

1. Read the task prompt and payloads for the target business ID, role, reporting date, and domain.
2. Read the answer template for the exact required JSON shape — every field, enum constraint, and ordering rule in the template is binding.
3. Query the environment for all relevant business records using both REST endpoints and SQL.
4. Apply the business rules for the task domain (see [workflow_patterns.md](references/workflow_patterns.md)).
Back to top