Individual skill

cedar-ridge-intake-json

Solve Cedar Ridge Intake Coordination Portal tasks that require JSON-only healthcare intake outputs, including new-patient access verification, specialty referral readiness audits, dialysis transfer packet/capacity reviews, chronic-care enrollment panels, and referral-to-chart activation files. Use when the prompt names the Cedar Ridge portal, a task environment base URL, and an answer_template.json with controlled output values.

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

Use the portal data as the source of truth and the provided `input/payloads/answer_template.json` as the output contract. Return exactly one JSON object and no prose.

## First Pass

1. Read the prompt and template. Extract the task family, identifiers, required top-level keys, controlled values, and ordering rules.
2. Replace `<TASK_ENV_BASE_URL>` with the actual base URL from the prompt or environment access notes.
3. Pull only records related to the requested roster, batch, program, transfer IDs, referral IDs, and linked patient IDs.
4. Prefer `/query` with read-only `SELECT` statements for joins and grouping. The useful tables are:
   `patients`, `intake_rosters`, `coverage`, `pbm`, `patient_pharmacy`, `pharmacies`, `lifestyle`, `clinical_history`, `referrals`, `icd_codes`, `documents`, `transfer_requests`, `facility_capacity`, `chart_artifacts`, and `program_candidates`.
5. Build results in the exact template shape. Include required keys with zero counts or empty arrays when no records qualify.
6. Recompute summaries from the per-item rows after all statuses are assigned. Validate counts and ordering before answering.