Menu

Individual skill

cedar-ridge-intake-coordination

0upvotes

Solving Cedar Ridge Intake Coordination Portal audit/intake tasks — reconcile patient, referral, transfer, chart, and program data into a strictly-templated JSON answer. Use whenever a task points at the Cedar Ridge portal (batches like NPI-JUN-01, ORTHO-JUN-01, DIAL-WINTER-01, DMHTN-2026A, PULM-JUN-02) and asks for a JSON activation/audit/enrollment file.

experiments/claude_code_glm_5_2_max/reports/skills/task_group_013/reflect-3/reflect-3_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 Coordination — Task Solving Skill

## What these tasks are

Each task targets one **batch** (a roster, referral batch, transfer batch, or program) in the Cedar
Ridge Intake Coordination Portal and asks you to produce **one JSON object** that follows a provided
`answer_template.json`. The portal is a shared, read-only store of intake, referral, transfer, chart,
and program data. The portal base URL is given in the task prompt as `<TASK_ENV_BASE_URL>`; the
per-task `environment_access.md` documents the available endpoints (treat that doc as the source of
truth for endpoint mechanics — do not hardcode URLs).

The work is **deterministic reconciliation + rule application**, not free-form narration. Every output
field is a controlled enum, a code from a fixed set, an ID, a count, or a date. There is no prose.
Back to top