Individual skill

cedar-ridge-intake

Complete intake coordination workflows for the Cedar Ridge Intake Coordination Portal. Use when a task references the Cedar Ridge portal, a task environment base URL with /patients /referrals /transfers /documents /chart /programs /icd /pharmacies endpoints, or any Cedar Ridge intake batch (patient access verification, referral audit, dialysis transfer review, chronic-care enrollment panel, or referral-to-chart activation). Covers all five intake workflows with business rules, SQL schema, and API navigation.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_013/fewshot/codex/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 Coordination

## Overview

The Cedar Ridge Intake Coordination Portal is a healthcare operations system for verifying patient access, auditing referrals, reviewing dialysis transfers, building chronic-care enrollment panels, and activating referral-to-chart workflows. It exposes both REST endpoints and a read-only SQL interface.

Every task follows the same pattern:
1. Identify the workflow from the prompt (batch ID, roster ID, program code).
2. Read the answer template (`input/payloads/answer_template.json`) for required output shape and controlled vocabularies.
3. Query the portal endpoints and/or SQL to gather all relevant records.
4. Apply the workflow's business rules to derive patient-level decisions.
5. Assemble the JSON exactly as the template specifies, using only controlled enum values.

## Portal Endpoints
Back to top