Menu

Individual skill

cedar-ridge-intake-reconciler

0upvotes

Reconcile Cedar Ridge Intake Coordination Portal tasks into exact JSON answer-template outputs. Use for patient access verification, referral readiness or chart activation, dialysis transfer packet review, chronic-care program enrollment panels, and similar Cedar Ridge portal tasks that require joining API or SQL data, applying controlled reason codes, ordering rows, and computing cohort summaries.

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

Use this skill when a task asks for a JSON-only Cedar Ridge intake, referral, transfer, or program-panel response from `<TASK_ENV_BASE_URL>`.

## Core Workflow

1. Read the prompt and `input/payloads/answer_template.json` first. Treat the template as the contract for keys, allowed values, ordering, constants, and summary fields.
2. Identify the target entity from the prompt: roster ID, referral batch ID, transfer batch ID, program code, explicit patient IDs, or explicit referral IDs.
3. Query only the relevant portal records. Prefer endpoint reads for small targets and `POST /query` with SQL for batch reconciliation.
4. Build row-level findings before summaries. Every count in a summary should be derived from the final row objects.
5. Emit one JSON object only. Do not add prose, comments, markdown fences, or values outside the template's controlled vocabulary.

## Portal Access
Back to top