Menu

Individual skill

cedar-ridge-intake-coordination

0upvotes

Produce schema-compliant JSON answers for Cedar Ridge Intake Coordination Portal tasks. Use when a task asks Codex to reconcile portal data for new-patient access verification, specialty referral readiness or chart activation, dialysis transfer packet and capacity review, or chronic-care program enrollment panels using TASK_ENV_BASE_URL and an answer_template.json.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_013/fewshot/fewshot_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
Yes
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 Coordination

## Core Workflow

1. Read the user prompt and `input/payloads/answer_template.json` first. Treat the template as the output contract: required keys, allowed enum values, ordering, nullability, and count keys come from the current task.
2. Read any other payload files in `input/payloads/`. Use payload IDs, roster IDs, batch IDs, program codes, requested dates, and patient/referral/transfer lists from the current task only.
3. Get the base URL from the task or environment access instructions. Use the portal endpoints and, when helpful, the read-only SQL endpoint:
   - `GET /patients`, `/patients/{patient_id}`
   - `GET /referrals?batch_id=...`, `/referrals/{referral_id}`
   - `GET /transfers?batch_id=...`, `/transfers/{transfer_id}`
   - `GET /documents`
   - `GET /chart/{patient_id}`
   - `GET /programs/{program_code}/candidates`
   - `GET /icd/{code}`
Back to top