Menu

Individual skill

northstar-payer-json-review

0upvotes

Solve Northstar payer-operations tasks that require structured JSON from an HTTP task environment for authorization, appeal, claim repricing, peer-to-peer, or margin queue work.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_014/fewshot/naive/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 JSON Review

Use this skill when the task asks for a Northstar Health Plan or payer-operations JSON answer built from a shared task environment. The usual inputs are `prompt.txt`, `payloads/task_context.json`, and `payloads/answer_template.json`.

## Operating Boundary

- Return exactly one JSON object matching the provided answer template; include no markdown or explanatory prose.
- Use the task prompt and payloads for the target ID, reporting date/period, token, endpoint, row IDs, thresholds, and required output shape.
- If the prompt contains `<TASK_ENV_BASE_URL>`, read `environment_access.md` only to obtain the live base URL. Do not use it as business evidence.
- Use only environment HTTP endpoints such as `POST /sql/query` and documented business endpoints. Do not inspect source files, database files, generated data files, manifests, or setup scripts.
- Prefer SQL for broad discovery and exact joins; use business endpoints when they expose clearer case/document/policy records.
- For SQL discovery in SQLite-like environments, use the HTTP SQL endpoint to inspect table names and columns, then issue targeted queries. Keep the bearer token and base URL from the task input out of the final JSON unless the template asks for them.

## Environment Workflow
Back to top