Menu

Individual skill

cedar-ridge-intake-json

0upvotes

Use this skill for Cedar Ridge Intake Coordination Portal tasks that ask Codex to verify access, audit referral batches, review dialysis transfers, prepare chronic-care enrollment panels, reconcile referral-to-chart activation work, or return a schema-controlled JSON object from TASK_ENV_BASE_URL. It is especially relevant when prompts mention Cedar Ridge, intake coordination, rosters, referrals, transfers, program candidates, chart artifacts, ICD metadata, documents, authorization, pharmacy/PBM, readiness, blockers, or cohort summaries.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_013/fewshot/opencode/fewshot_attempt_01/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 this skill to solve Cedar Ridge portal reconciliation tasks and return one valid JSON object that matches the task's `input/payloads/answer_template.json`.

## Core Workflow

1. Read the prompt, every file in `input/payloads/`, and especially `answer_template.json`.
2. Identify the target object and required population from the prompt/template:
   - roster or patient-access task: target roster and patient IDs
   - referral task: target `batch_id` and all referrals in that batch
   - transfer task: target transfer `batch_id` and all transfers in that batch
   - program task: target `program_code` and all current candidates
3. Resolve `<TASK_ENV_BASE_URL>` from the prompt. If it is a placeholder, read `environment_access.md` if present and use its `base_url`.
4. Fetch portal evidence for every target record. Prefer exact detail endpoints and filtered SQL over broad dumps.
Back to top