Individual skill
cedar-ridge-intake-coordination
Reconcile Cedar Ridge Intake Coordination Portal data into schema-constrained JSON for patient access verification, referral readiness or chart activation, dialysis transfer packet and capacity review, and chronic-care enrollment panels. Use when a task references Cedar Ridge intake rosters, referral batches, transfer batches, program candidates, patients or charts, ICD metadata, documents, pharmacies, or the portal endpoints.
experiments/codex_gpt5_5_xhigh/reports/skills/task_group_013/self/self_attempt_01/SKILL.md
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.
- agent Repository topic
- ai Repository topic
- benchmark Repository topic
- llm Repository topic
- self-evolving Repository topic
- self-learning Repository topic
- skills Repository topic
- data Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 12,719 bytes
Read excerpt
# Cedar Ridge Intake Coordination
## Core Workflow
1. Read the user prompt and `input/payloads/answer_template.json` first. Treat the template as the authority for required keys, allowed enum values, output ordering, and count buckets.
2. Read `environment_access.md` before any network access. Use only the listed base URL and endpoints. No credentials are required unless that file says otherwise.
3. Query narrowly by the target roster, batch, program code, transfer IDs, referral IDs, and patient IDs. Ignore distractor rows outside the target scope.
4. Prefer `POST /query` with read-only `SELECT` statements for joins across portal tables. Use detail endpoints such as `/patients/{patient_id}`, `/referrals/{referral_id}`, `/transfers/{transfer_id}`, `/chart/{patient_id}`, and `/icd/{code}` when nested evidence is useful.
5. Produce exactly one JSON object matching the template. Do not include prose outside JSON when the task asks for JSON only.
## Output Discipline
- Use controlled values exactly as listed in the task template. Do not invent reason codes, statuses, owners, routes, or package components.
- Include all required keys and all required summary count buckets, even when a count is zero.