Menu

Individual skill

cedar-ridge-intake-json

0upvotes

Use for Cedar Ridge Intake Coordination Portal tasks that require strict JSON from patient, roster, insurance, PBM, pharmacy, referral, ICD, document, transfer, capacity, chart, or program-candidate records. Trigger whenever the prompt mentions Cedar Ridge intake coordination, TASK_ENV_BASE_URL, answer_template.json, access verification, referral readiness or activation, dialysis transfer review, chronic-care enrollment panels, or cohort summaries.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_013/fewshot/opencode/fewshot_attempt_03/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 Solver

Use this skill to turn Cedar Ridge Intake Coordination Portal records into the exact JSON shape requested by `input/payloads/answer_template.json`.

## Operating Rules

1. Read the task prompt and `answer_template.json` before fetching data. Treat the template as the output contract: required keys, controlled values, nullability, ordering, and count keys come from it.
2. Resolve `<TASK_ENV_BASE_URL>` from the prompt or environment access instructions. Use only the task environment endpoints needed for the requested scope.
3. Prefer scoped requests over broad listings. Use exact patient, referral, transfer, batch, roster, or program identifiers from the prompt/template. The SQL `/query` endpoint is useful when the REST endpoint does not expose a batch/roster listing directly.
4. Build an evidence table before writing JSON. Keep one row per requested patient, referral, transfer, or candidate with source fields, derived issue codes, status, priority, and summary buckets.
5. Return JSON only. Do not include prose, markdown fences, comments, or values outside the template's allowed enums.

## Portal Endpoints
Back to top