Individual skill

cedar-ridge-intake-json

Solve Cedar Ridge Intake Coordination Portal tasks that require strict JSON from read-only portal records and answer_template schemas, including new-patient access verification, referral readiness and chart activation, dialysis transfer packet and capacity review, and chronic-care enrollment panels.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_013/fewshot/naive/fewshot_attempt_03/SKILL.md

Read pinned source

Source commit 5082a777379156a048881e94940d640702e5e09a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
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

## Core Workflow

1. Read the user prompt, `input/payloads/answer_template.json`, and any other payload files before querying the portal.
2. Extract the target identifier, target type, output ordering, required keys, allowed enum values, count keys, and any fixed values from the template. Treat the template as the output contract.
3. Use only the read-only Cedar Ridge portal endpoints supplied by the task. Never call a judge or evaluator endpoint.
4. Fetch only records relevant to the target roster, referral batch, transfer batch, or program code. Prefer the SQL endpoint or the bundled helper for complete, filterable snapshots.
5. Build an intermediate work table with one row per required patient, referral, transfer, or candidate. Record the raw facts that justify every status and reason code.
6. Emit exactly one JSON object. Do not include prose, comments, markdown fences, or fields not requested by the template.
7. Validate with `jq` or Python JSON parsing, then verify required keys, enum values, list ordering, nulls, and summary counts.

## Portal Snapshot Helper