Individual skill

cedar-ridge-intake

Complete Cedar Ridge Intake Coordination Portal intake workflows – new-patient access verification, referral batch audit, dialysis transfer review, chronic-care program enrollment, and referral-to-chart activation. Use whenever the user mentions Cedar Ridge, intake coordination, patient access verification, referral audit, transfer review, program enrollment, or chart activation in a healthcare portal context, or when a task references the (TASK_ENV_BASE_URL) placeholder or cedar ridge intake coordination portal.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_013/fewshot/cc/fewshot_attempt_02/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

This skill covers the five intake workflows available through the Cedar Ridge
Intake Coordination Portal, a REST API at a configurable base URL. Every
workflow follows the same skeleton: read the answer template, fetch records
from the portal, cross-reference and classify, and return structured JSON.

## Workflow skeleton

1. **Read the answer template.** The prompt references a file under
   `input/payloads/answer_template.json`. Read it first -- it defines every
   required key, allowed value, and sort order. If there is an additional
   payload file (e.g. a target roster), read that as well.
Back to top