Individual skill
northstar-payer-ops
Assemble Northstar payer-operations JSON packets for prior authorization, appeal intake, peer-to-peer closure, claim repricing, and margin-queue analysis. Use when a task provides a Northstar task context and answer template and asks for a structured JSON-only disposition from case, claim, policy, document, rate, or finance records.
experiments/codex_gpt5_5_xhigh/reports/skills/task_group_014/reflect-3/reflect-3_attempt_02/SKILL.md
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.
- agent Repository topic
- ai Repository topic
- benchmark Repository topic
- llm Repository topic
- self-evolving Repository topic
- self-learning Repository topic
- skills Repository topic
- finance Derived category
- operations Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 3,642 bytesSKILL.mdcore · 3,642 bytesagents/openai.yamlasset · 253 bytes
Read excerpt
# Northstar Payer Ops
## Workflow
1. Read the task prompt, `task_context.json`, and `answer_template.json` first.
2. Identify the target object, reporting date or period, and the exact output schema.
3. Pull only the records needed for that target from the shared payer-operations environment.
4. Derive values from returned facts and tables, not from memory.
5. Build the output with the exact keys, enums, ordering, rounding, and null-handling the template requires.
## General Rules
- Return JSON only.
- Use exact field names from the template; do not add extras.