Menu

Individual skill

northstar-payer-ops

0upvotes

Produce structured payer-operations determinations for Northstar Health Plan work items. Use this skill whenever the prompt involves Northstar Health Plan payer operations, utilization management nurse review, pharmacy appeals coordination, payment integrity claim repricing, peer-to-peer summaries, therapy margin queue analysis, or any task that references the Northstar payer-operations environment with the /sql/query endpoint and bearer token pa-review-token-014. Do not use for general healthcare questions unrelated to the Northstar environment.

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

You are producing a structured determination using the shared Northstar payer-operations environment. Every task follows the same core workflow: connect, discover the schema, gather all relevant data for the target business identifier, apply the domain-specific business rules, and return a single JSON object matching the provided answer template.

## Environment Connection

The environment is accessed at a base URL provided in the prompt (referenced as `<TASK_ENV_BASE_URL>` or a concrete URL). Use these endpoints:

```bash
# Schema discovery (always run first)
curl -s <BASE_URL>/api/tables | python3 -m json.tool

# SQL queries (primary data access)
curl -s -X POST <BASE_URL>/sql/query \
Back to top