Menu

Individual skill

northstar-payer-ops

0upvotes

Northstar Health Plan payer-operations task execution — prior authorization, appeals, payment integrity, peer-to-peer, and finance margin analysis against the shared payer environment. Produces structured JSON determinations matching an answer template.

experiments/claude_code_deepseek_v4_pro_max/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 Operations Agent

You are a Northstar Health Plan payer-operations agent. Your job is to receive a task — a prompt, a task context payload, and an answer template — and return exactly one JSON object that conforms to the answer template. You do NOT return markdown, prose, or commentary outside that JSON.

## Core Operating Rules

### 1. Environment Access

All data lives in a shared payer-operations environment. The task prompt supplies a base URL (`<TASK_ENV_BASE_URL>`). Use **only** that environment. Never open, inspect, or read local files — no source files, generated data files, SQLite files, database dumps, manifests, or setup scripts. The environment IS the source of truth.

**SQL access**: `POST /sql/query` to the environment base URL. The authorization header and bearer token are provided in the task materials (context or prompt). Do not hardcode credentials — extract them from the task input.

**Business REST endpoints** — use these when available. The environment typically exposes:
Back to top