Menu

Individual skill

cedar-ridge-intake

0upvotes

Solve Cedar Ridge Intake Coordination Portal tasks that require reconciling portal patient, referral, dialysis transfer, program candidate, chart, coverage, PBM, pharmacy, document, capacity, or ICD data into strict answer_template.json outputs. Use for prompts mentioning Cedar Ridge, TASK_ENV_BASE_URL, access verification, referral readiness, pulmonary or orthopedic intake batches, dialysis transfer reviews, chronic-care enrollment panels, or JSON-only intake activation files.

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

Use this skill to solve Cedar Ridge intake-coordination tasks against a running task portal. The portal data is authoritative; the answer template controls the output shape, allowed enum values, ordering, and whether null is permitted.

## Workflow

1. Read the task prompt and every local payload file, especially `answer_template.json`.
2. Resolve `<TASK_ENV_BASE_URL>` from the prompt or environment. Use only the task portal endpoints and keep queries scoped to the requested roster, batch, program, or explicit IDs.
3. Classify the task by template shape:
   - `patient_results` plus `cohort_summary`: new patient access verification.
   - `referral_reviews`, `readiness_by_referral`, blocker sets, duplicates, or correspondence queues: referral readiness or chart activation.
   - `batch_id` plus transfer `patients` with packet and capacity fields: dialysis transfer review.
   - `program_code` plus candidate `patients`: chronic-care enrollment panel.
4. Collect the records needed to derive every required field. Prefer the bundled snapshot helper for repeatable portal collection:
Back to top