Menu

Individual skill

cedar-ridge-intake

0upvotes

Query the Cedar Ridge Intake Coordination Portal REST API to complete healthcare intake-coordination workflows. Use this skill whenever the task involves the Cedar Ridge portal, Cedar Ridge intake, patient access verification, referral batch audits, dialysis transfer review, chronic-care enrollment panels, referral-to-chart activation, or any prompt that mentions a TASK_ENV_BASE_URL pointing to a Cedar Ridge Intake Coordination Portal. The skill documents every available endpoint, response shapes, and the decision-logic patterns needed to produce compliant JSON answers from portal data.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_013/fewshot/opencode/fewshot_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
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 Portal

Use the shared read-only REST API at the base URL provided in the task prompt (typically `<TASK_ENV_BASE_URL>`) to retrieve patient, referral, transfer, chart, coverage, pharmacy, document, and program-candidate records. The portal also includes a read-only SQL endpoint for ad-hoc reconciliation.

Every task follows the same core pattern:

1. Read the answer template (always supplied as `input/payloads/answer_template.json` or described in the prompt) to understand the exact output shape and controlled vocabularies.
2. Pull all relevant records from the portal via the endpoints documented below.
3. Apply the decision logic for the workflow type (see [references/decision-logic.md](references/decision-logic.md)).
4. Assemble the JSON response using only values from the template's enumerated sets.
5. Return JSON only — no prose outside the JSON object unless the template or prompt explicitly allows it.

Do not guess at controlled values. Every status, reason code, tier, and channel must be drawn from the enumerated sets defined in the answer template. When the template specifies ordering (ascending by ID, alphabetical, unordered set), follow it exactly.
Back to top