Individual skill

cedar-ridge-intake-json

Solve Cedar Ridge Intake Coordination Portal tasks that require reconciling healthcare intake data and returning a controlled JSON object. Use for new-patient access verification, referral readiness or chart activation, dialysis transfer review, chronic-care program enrollment, and similar portal tasks involving answer_template.json, patient/referral/transfer/program records, ICD metadata, documents, benefits, pharmacies, capacity, chart artifacts, or cohort summaries.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_013/fewshot/codex/fewshot_attempt_02/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

## Workflow

1. Read the task prompt and `input/payloads/answer_template.json` completely.
2. Identify the target identifier from the prompt: roster ID, referral batch ID, transfer batch ID, program code, or explicit patient/referral/transfer IDs.
3. Read any other payload files in `input/payloads/`; treat them as constraints, not as optional hints.
4. Collect portal data from the task environment. For the domain rules and endpoint/table map, read [domain_rules.md](references/domain_rules.md).
5. Build the answer against the template, using only allowed enum/code values and preserving required keys.
6. Recompute all summary counts from the final emitted rows.
7. Validate JSON syntax locally before final response. Return JSON only when the prompt asks for JSON only.

## Portal Snapshot Helper