Individual skill
cedar-ridge-intake-reconciliation
Reconcile Cedar Ridge Intake Coordination Portal worklists into strict controlled-value JSON. Use when a task references Cedar Ridge roster access verification, referral readiness or chart activation, dialysis transfer packet and capacity review, chronic-care program enrollment panels, answer_template.json payloads, or the shared intake coordination portal.
experiments/codex_gpt5_5_xhigh/reports/skills/task_group_013/self/self_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
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# Cedar Ridge Intake Reconciliation
## Core Workflow
1. Read the task prompt and `input/payloads/answer_template.json` first. Treat the template as the output contract for keys, enums, ordering, nullability, and counts.
2. Use the portal base URL supplied by the task. Prefer `POST /query` with `SELECT` statements for exact joins; use detail endpoints such as `/referrals/{id}`, `/transfers/{id}`, `/patients/{id}`, `/chart/{patient_id}`, and `/icd/{code}` to spot-check bundled records.
3. Extract target identifiers from the prompt/template instead of hard-coding train IDs. For rosters use `intake_rosters`; for referrals use `referrals.batch_id`; for transfers use `transfer_requests.batch_id`; for programs use `/programs/{program_code}/candidates` or `program_candidates`.
4. Build results from source rows only. Ignore distractor batches and patients unless needed to detect shared IDs or duplicates within the target set.
5. Preserve template ordering exactly: usually ascending item IDs, unordered code sets as stable sorted arrays, and ranked priority lists highest priority first.
6. Emit one JSON object only. Do not add prose, comments, unrequested fields, or enum values not present in the template.
## Useful Tables
- `patients`: demographics, contact availability, `existing_chart`, preferred contact, emergency contact.