Individual skill

cedar-ridge-intake-coordination

Solve Cedar Ridge Intake Coordination Portal tasks — query the read-only portal (REST + SQL), map the evidence to the supplied answer_template.json, and return a single JSON object. Use whenever a task names the Cedar Ridge Intake Coordination Portal and provides an answer_template.json: new-patient access verification (roster), referral readiness/activation audit (batch), dialysis transfer review (batch), or chronic-care enrollment panel (program).

experiments/claude_code_glm_5_2_max/reports/skills/task_group_013/self/self_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 Coordination

The Cedar Ridge Intake Coordination Portal is a shared, read-only store of intake,
referral, transfer, chart, and program data. A task in this family gives you a
**prompt** (`prompt.txt`) and an **answer template** (`input/payloads/answer_template.json`),
and asks for one JSON object built from portal evidence.

The work is always the same shape: **scope → gather → map → summarize → emit JSON**.
The rules below are reusable across every batch, roster, and program. Do not hardcode
any task-specific final values (statuses, reason codes, counts, dates) — derive every
value from the portal and the template.

## 1. Read the contract first