Menu

Individual skill

cedar-ridge-intake-auditor

0upvotes

Use for Cedar Ridge Intake Coordination Portal tasks that require reconciling patient access, referral readiness, dialysis transfers, chronic-care enrollment panels, chart activation, ICD metadata, insurance/PBM/pharmacy status, packet documents, capacity, and strict template-shaped JSON outputs.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_013/self/self_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

# Cedar Ridge Intake Auditor

## Core Workflow

1. Read the user prompt, every input payload, and the answer template before querying the portal.
2. Read `environment_access.md` for the base URL and allowed endpoints. Use only those endpoints for network access.
3. Treat the answer template as the contract: include every required key, use only controlled enum values, preserve required list ordering, and compute all summary counts from the row-level output.
4. Pull only the requested roster, batch, program, transfer, referral, or patient cohort. Ignore distractor rows from other cohorts.
5. Prefer the read-only SQL endpoint for reconciliation when several tables must be joined. Use record endpoints when they package related context more directly:
   - `GET /patients/{patient_id}` for demographics and contact flags.
   - `GET /referrals/{referral_id}` for referral, patient, ICD, and referral documents.
   - `GET /transfers/{transfer_id}` for transfer, patient, packet documents, and nearby capacity.
   - `GET /chart/{patient_id}` for clinical history and chart artifacts.
   - `GET /programs/{program_code}/candidates` for current program scope.
Back to top