Menu

Individual skill

intake-coordination-portal-audit

0upvotes

Produce the required normalized JSON audit for a Cedar Ridge Intake Coordination Portal task — patient access verification, referral readiness / referral-to-chart activation, dialysis transfer review, or program enrollment panel. Use when a task points at an intake-coordination portal base URL plus an answer_template.json and asks for a batch/roster/program-level JSON report of statuses, blockers, reason codes, and cohort counts. Covers how to discover the data, apply the classification rules, and emit template-conformant JSON.

experiments/claude_code_opus_4_8_xhigh/reports/skills/task_group_013/reflect-3/reflect-3_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

# Intake Coordination Portal Audit

## What this covers

A family of read-only clinical-operations audits served by an "Intake
Coordination Portal." Each task hands you:

- a **prompt** naming one target id — a roster, referral batch, transfer batch,
  or program code — and a portal **base URL** (given as a placeholder such as
  `<TASK_ENV_BASE_URL>`; read it from the task, never hardcode one);
- an **`input/payloads/answer_template.json`** describing the exact JSON you must
  return (required keys, per-item keys, allowed enum values, orderings, and
  summary/count structure);
- an **environment access note** listing the portal's available read endpoints.
Back to top