Menu

Individual skill

reflect-3_attempt_02

0upvotes

Not available

experiments/claude_code_deepseek_v4_pro_max/reports/skills/task_group_014/reflect-3/reflect-3_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.

Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.

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.

Declared tags are partial or unavailable.

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 Skill

## Overview
Use this skill when solving Northstar Health Plan payer operations tasks — prior authorizations, appeals, payment integrity corrections, peer-to-peer summaries, and margin queue analysis. The environment is a shared read-only payer operations portal with REST endpoints and a SQL interface.

## Environment Setup
The task will provide a base URL and a bearer token. Use these to interact with the environment:
[Credential-related source omitted]
- The SQL endpoint is `POST /sql/query` with JSON body `{"sql": "<statement>"}` — note the key is `sql`, not `query`
- When neither REST nor SQL is specified, prefer the business REST endpoints first; they return pre-joined, comprehensive results

## Data Access Strategy

### Step 1: Use business REST endpoints first
Start with `GET /api/cases/{target_id}` — this returns a rich, pre-joined payload containing the case record, member details, provider info, plan context, request lines, criteria results (with fact traceability), documents (with facts), authorizations, claims with claim lines, appeals, drug trials, P2P events, and assistance screens all in a single call.
Back to top