prism-shadow
- 1.7k skills
- 0 followers
- 5 days ago last updated
- ▌ Apexcloud Retention Ops 18 · prism-shadow bundleSolve ApexCloud Retention Operations API tasks that require strict JSON outputs for customer success QBR packets, renewal risk queues, retention action boards, A/R aging follow-ups, CRM pipeline summaries, HR/event ops context, or churn model validation and candidate ranking. Use when a prompt mentions the ApexCloud Retention Operations API, account metrics, support/NPS/billing/A/R endpoints, retention risk, receivables, pipeline operations, high-touch retention boards, or churn exports.
- ▌ Apexcloud Retention Ops 19 · prism-shadow bundleBuild JSON reports from the ApexCloud Retention Operations API. Use this whenever a prompt mentions ApexCloud, renewal risk queues, QBR metric packets, receivables or pipeline reviews, churn validation, or retention boards, even if the report type is only implied.
- ▌ Apex Retention Ops · prism-shadow bundleUse this skill whenever a task asks for JSON from the ApexCloud Retention Operations API, including renewal risk queues, retention action boards, QBR metrics packets, receivables and pipeline reviews, churn export validation, outreach rankings, A/R aging, billing snapshots, support/NPS/usage health, CRM opportunities, HR/event operations context, or ApexCloud policy codes. Trigger even when the user only mentions ApexCloud, customer success operations, QBR metrics, AR aging, churn exports, or a controlled-answer template.
- ▌ Erp Batch Reconciler · prism-shadow bundleReconcile finance and compliance batch tasks against a runner-provided ERP/task API and return strict JSON. Use when a prompt mentions task_group ERP data, shared finance/compliance APIs, reimbursement claims, AP bills/payments, stale AP snapshots, vendor onboarding or payment release, account-change risk review, prepaid close schedules, GL balances, or answer_template.json-driven finance close outputs.
- ▌ Erp Finance API Reconciler · prism-shadowUse this skill for task-group ERP finance/compliance reconciliation prompts that require querying a runner-provided JSON API and returning exact JSON. It is especially relevant for reimbursement-to-AP close batches, stale AP snapshot reviews, prepaid close checks, vendor onboarding release decisions, account-change payment release reviews, and prompts mentioning claims, AP bills, payments, close logs, vendors, compliance objects, ownership, registry, screening, bank checks, prepaid invoices, or GL balances.
- ▌ Atlas Commerce Ops SQL Analyst · prism-shadowSolve Atlas Commerce Operations workplace tasks that provide prompt/payload files, a strict answer_template.json, and a TASK_ENV_BASE_URL with schema, data-dictionary, SQL, correction-audit, or controlled transaction endpoints. Use for fulfillment, refunds, carrier quality corrections, warehouse productivity, support health, inventory/order/payment analytics, and similar cutoff-based operational JSON reports.
- ▌ Atlas Ops Solver · prism-shadow bundleSolve Atlas Commerce Operations tasks that require querying the authenticated workplace API, computing exact operational metrics from the Atlas Commerce database, emitting schema-conformant JSON answers, or applying narrowly approved canonical data corrections with audit records. Use for Atlas fulfillment, refund reconciliation, carrier quality, warehouse productivity, support health, inventory, order, payment, and similar cutoff-based analytics tasks.
- ▌ Pho Algorithmic Audits 3 · prism-shadow bundleSolve Public Health Observatory web-portal algorithmic audit tasks from analysis_request.json and answer_template.json, including exact PHO state, county, panel, mediation, robustness, and country-burden audit profiles. Use when a task asks Codex to resolve PHO releases and cohorts and return controlled JSON with clustered inference, nested ridge or elastic-net validation, wild bootstrap, grouped conformal calibration, PCA/k-means stability, mediation, GMM, sensitivity, or perturbation modules.
- ▌ Pho Observatory Audits 2 · prism-shadow bundleSolve Public Health Observatory web-portal audit tasks requiring exact JSON outputs from analysis_request.json and answer_template.json. Use for PHO algorithmic publication audits over state, county, or country data, including exact protocols PHO_STATE_TRANSPORT_AUDIT_V1, PHO_COUNTY_MEDIATION_TRANSPORT_V1, PHO_STATE_ROBUSTNESS_TRANSPORT_V1, PHO_COUNTY_PANEL_TRANSPORT_V1, and country burden revision/PCA/cluster/panel audit requests.
- ▌ Pho Observatory Audits 3 · prism-shadow bundleSolve Public Health Observatory Web portal audit tasks from analysis_request.json and answer_template.json, including state, county, and country release resolution; cohort construction; fixed-effect, GMM, ridge, elastic-net, bootstrap, conformal, PCA, clustering, sensitivity, source-perturbation, and controlled-decision modules. Use when a task provides a PHO/Public Health Observatory portal base URL plus registered audit request/template files and asks for exactly one JSON answer.
- ▌ Pho Portal Audit · prism-shadow bundleSolve Public Health Observatory web-portal audit tasks that require analysis_request.json and answer_template.json outputs, including state, county, and country release reconciliation; deterministic fixed-effect, GMM, ridge or elastic-net, bootstrap, conformal, PCA, clustering, sensitivity, source-perturbation, and controlled-decision modules. Use when a task references the Public Health Observatory portal, PHO protocol IDs, or asks for one JSON audit object from portal evidence.
- ▌ Solve Pho Audits · prism-shadowSolve Public Health Observatory portal audit tasks from prompt.txt, analysis_request.json, and answer_template.json. Use for PHO JSON-only analytical audits that require portal release resolution, cohorts, regression/GMM, nested ridge or elastic-net validation, wild cluster bootstrap, conformal calibration, PCA/k-means clustering, source perturbation, mediation sensitivity, country burden revision reconciliation, and controlled decisions; especially exact protocol_id values PHO_STATE_TRANSPORT_AUDIT_V1, PHO_COUNTY_MEDIATION_TRANSPORT_V1, PHO_STATE_ROBUSTNESS_TRANSPORT_V1, and PHO_COUNTY_PANEL_TRANSPORT_V1.
- ▌ Pho Algorithmic Audits 4 · prism-shadow bundleSolve Public Health Observatory Web-only portal tasks that provide analysis_request.json and answer_template.json and require publication/release resolution, cohort construction, registered statistical audit modules, transportability or robustness gates, and exact JSON-only answers. Use especially for exact protocol_id values PHO_STATE_TRANSPORT_AUDIT_V1, PHO_COUNTY_MEDIATION_TRANSPORT_V1, PHO_STATE_ROBUSTNESS_TRANSPORT_V1, PHO_COUNTY_PANEL_TRANSPORT_V1, or country burden revision/PCA clustering audits.
- ▌ Engineering Portfolio Env 2 · prism-shadow bundleAnalyze the shared engineering portfolio task environment and return exact JSON for portfolio mix reviews, SLA aging audits, and release-readiness assessments. Use when a prompt references TASK_ENV_BASE_URL, work items, mix targets, SLA policy, releases, milestones, blockers, dependencies, or asks to distinguish primary work from duplicates/cancelled/stale mirror records.
- ▌ Engineering Portfolio Audit · prism-shadow bundleAnalyze shared engineering portfolio task environments and produce schema-exact JSON answers for work item portfolio mix, SLA aging, release readiness, blockers, dependencies, duplicate clusters, stale mirror fields, and prompts that provide a TASK_ENV_BASE_URL plus answer_template.json.
- ▌ Engineering Portfolio Review 3 · prism-shadow bundleSolve engineering portfolio environment analysis tasks that require JSON answers from a shared task API. Use for portfolio mix reviews, SLA aging audits, release-readiness assessments, work item classification, duplicate exclusion, stale mirror-field handling, mix target comparison, blocker/dependency analysis, and exact answer-template shaping.
- ▌ Engineering Portfolio Environment · prism-shadowSolve engineering portfolio environment tasks that require producing strict JSON from read-only work item data, mix targets, SLA policy, releases, milestones, blockers, dependencies, or the restricted SQL endpoint. Use for portfolio-mix reviews, SLA aging audits, release-readiness assessments, duplicate/cancelled exclusion reports, and similar tasks that reference TASK_ENV_BASE_URL, environment_access.md, or input/payloads/answer_template.json.
- ▌ Engineering Portfolio JSON Solver · prism-shadowSolve JSON-only engineering portfolio environment tasks that require querying shared work-item, portfolio mix target, SLA, release, milestone, blocker, dependency, or restricted SQL endpoints; use for tasks asking Codex to compute portfolio mix, SLA aging/breach metrics, duplicate clusters, release readiness, ship decisions, gating work, blockers, dependency chains, or schema-constrained answers from a TASK_ENV_BASE_URL and environment_access.md.
- ▌ Ma Deal Workbench Review 8 · prism-shadow bundleAnalyze M&A deal workbench tasks that require counsel-side JSON outputs using TASK_ENV_BASE_URL/API records, playbooks or policies, issue matrices, closing packages, committee escalations, transition reviews, consents, employees, regulatory records, benchmarks, risk estimates, and schema-conformant answer_template.json responses.
- ▌ Ma Deal Workbench JSON 10 · prism-shadow bundleUse when solving M&A deal workbench tasks that require fetching deal records, comparing APA or SPA draft terms to buyer or seller playbooks or committee policy, calculating deal economics, and returning strict JSON issue registers, deviation matrices, closing packages, or committee escalations.
- ▌ Ma Deal Workbench JSON 11 · prism-shadowSolve M&A deal workbench tasks that require strict JSON outputs from deal API records, playbook or policy comparisons, source IDs, and legal/economic calculations.
- ▌ Ma Deal Workbench JSON 12 · prism-shadowSolve M&A deal workbench tasks that require schema-exact JSON outputs from deal APIs, playbooks, policies, diligence, consents, regulatory, employee, benchmark, risk, and draft-term records.
- ▌ Ma Deal Workbench Review 9 · prism-shadowUse this skill for M&A deal-workbench legal review tasks that require gathering deal, draft term, playbook, policy, diligence, consent, employee, regulatory, benchmark, or risk records and returning strict JSON issue registers, SPA or APA deviation matrices, closing/economics packages, committee escalations, or transition reviews.
- ▌ Asteria Hub Reconciliation 2 · prism-shadow bundleReconcile Asteria Fleet Data Quality Hub audit and certification tasks and return schema-valid JSON. Use when a task provides TASK_ENV_BASE_URL plus environment_access.md, payloads/case_scope.json, and payloads/answer_template.json for contact or roster readiness, fuel or freight transaction normalization, maintenance history integrity, source snapshots, aliases, conversions, FX, duplicate records, quarantines, rankings, status decisions, or opaque Asteria control-code panels.
- ▌ Asteria Dq Hub Audits · prism-shadow bundleReconcile Asteria Fleet Data Quality Hub audit tasks that provide payloads/case_scope.json and payloads/answer_template.json. Use for contact canonicalization and readiness, fuel or freight transaction normalization, maintenance-log integrity, duplicate snapshot resolution, quarantine and mismatch reporting, code decision panels, rollups, rankings, and PASS/HOLD certification decisions.
- ▌ Asteria Fleet Dq · prism-shadow bundleSolve Asteria Fleet Data Quality Hub reconciliation and certification tasks for contacts, roster readiness, fuel purchases, freight charges, and maintenance logs. Use when Codex must read environment_access.md, payloads/case_scope.json, and payloads/answer_template.json, query the Asteria hub endpoints, reconcile overlapping snapshots and duplicates, normalize aliases, units, and FX, infer compact Asteria control codes, and return a strict JSON answer.
- ▌ Asteria Fleet Dq Audit 5 · prism-shadowSolve Asteria Fleet Data Quality Hub reconciliation tasks for contacts, fuel, freight, and maintenance collections.
- ▌ Asteria Hub Quality Audits · prism-shadow bundleSolve Asteria Fleet Data Quality Hub reconciliation and certification tasks that provide case_scope.json, answer_template.json, and environment_access.md. Use for contact-master/readiness, fuel or freight normalization, maintenance-history integrity, source-snapshot reconciliation, quarantine/mismatch reporting, decision-code panels, rollups, rankings, and strict JSON-only answers.
- ▌ Asteria Hub Reconcile · prism-shadow bundleSolve Asteria Fleet Data Quality Hub audit and certification tasks that require reconciling contacts, fuel transactions, freight charges, or maintenance events from a running task environment into a strict JSON answer contract. Use when prompts mention the Asteria Fleet Data Quality Hub, source snapshots, contact-readiness, fuel or freight normalization, maintenance-history integrity, reference aliases, FX/unit conversions, or opaque control-code panels.
- ▌ Atlas Commerce Ops Solver · prism-shadow bundleSolve Atlas Commerce Operations benchmark tasks that provide a prompt, request payload JSON, answer_template.json, and authenticated task-environment API. Use for SQL-based operational analytics, cutoff/as-of metrics, strict answer.json generation, and approved canonical corrections with correction_audit verification.
- ▌ Atlas Commerce Ops 4 · prism-shadow bundleSolve Atlas Commerce Operations workplace tasks that require authenticated SQL analysis, approved canonical data corrections, and strict answer.json output. Use for prompts mentioning Atlas Commerce Operations APIs, fulfillment scorecards, refund reconciliation, carrier scan quality corrections, warehouse productivity, support health, inventory, payments, orders, shipments, warehouses, support cases, or JSON answer templates.
- ▌ Atlas Commerce Ops Solver 2 · prism-shadow bundleSolve Atlas Commerce Operations database tasks that provide prompt.txt, request payloads, answer_template.json, and authenticated TASK_ENV_BASE_URL API endpoints. Use for fulfillment, refund, carrier quality, warehouse productivity, support health, inventory, order, payment, customer, SQL analysis, and controlled canonical-correction tasks that must write an exact answer.json.
- ▌ Atlas Commerce Ops Solver 3 · prism-shadow bundleSolve Atlas Commerce Operations workplace tasks that require authenticated schema discovery, read-only SQL analysis, strict answer_template.json output, and occasionally an explicitly approved canonical correction through /api/sql/transaction and correction audit verification. Use when a prompt mentions TASK_ENV_BASE_URL, Atlas Commerce Operations, /api/schema, /api/data-dictionary, /api/sql, /api/sql/transaction, correction-audit, fulfillment scorecards, refund reconciliation, carrier scan quality, warehouse productivity, or support health analytics.
- ▌ Investigation Review Hub Remediation 5 · prism-shadow bundleSolve Investigation Review Hub legal production, preservation, privilege, QC, retention, and remediation dashboard tasks. Use when a prompt asks Codex to query a running review hub at TASK_ENV_BASE_URL and return a strict JSON object conforming to an answer_template.json schema.
- ▌ Investigation Review Hub Remediation 6 · prism-shadow bundleSolve Investigation Review Hub legal remediation tasks that require schema-conformant JSON for subpoena gap analyses, retention/preservation reviews, production readiness, privilege/QC blockers, and cross-system remediation dashboards.
- ▌ Investigation Review Hub Remediation JSON 2 · prism-shadowSolve Investigation Review Hub legal production, preservation, privilege, QC, retention, and remediation dashboard tasks as exact structured JSON.
- ▌ Court Portal Closeout JSON · prism-shadow bundlePrepare clerk-ready court closeout, disposition, payment-plan, probation-referral, license-order, and financial-register JSON answers from local payload files plus a Court Operations Portal. Use when a task provides an answer_template.json, court hearing or sentencing notes, finance or petition payloads, and portal endpoints such as cases, charges, docket entries, citations, fee schedules, payment policies, forms, financial petitions, or search.
- ▌ Court Closeout Reconciler · prism-shadow bundleReconcile court closeout tasks that require a structured JSON answer from local payloads and a Court Operations Portal. Use for criminal disposition registers, traffic citation closeouts, payment-plan packets, sentencing/probation/license form packets, fee-schedule audits, and tasks with answer_template.json plus endpoints such as cases, charges, citations, fee-schedules, payment-policies, forms, docket-entries, financial-petitions, or search.
- ▌ Court Closeout Reconciler 2 · prism-shadow bundleReconcile court disposition closeout, sentencing, traffic, payment-plan, and post-sentencing packet tasks using local clerk/hearing payloads plus a Court Operations Portal API. Use when Codex must return schema-conformant JSON for case or citation dispositions, fee registers, payment petitions, form fields, placeholders, docket actions, and batch totals.
- ▌ Court Closeout JSON 2 · prism-shadowSolve court closeout, disposition register, payment plan, probation referral, and license order tasks by reconciling local payloads with a Court Operations Portal and returning schema-exact JSON.
- ▌ Court Closeout Reconciliation 9 · prism-shadowReconcile court closeout packets into schema-valid JSON using local payloads and Court Operations Portal records. Use for criminal sentencing closeouts, traffic violation dispositions, payment petitions, installment plans, probation referrals, license suspension orders, fee schedule and payment-policy checks, unsupported-fee exclusions, placeholder handling, docket/register actions, and batch totals.
- ▌ Court Closeout Reconciliation 10 · prism-shadowReconcile court closeout, disposition register, payment-plan, and post-sentencing packet tasks using local payloads plus the read-only Court Operations Portal, returning schema-exact JSON.
- ▌ Licensing Review JSON 3 · prism-shadow bundleProduce structured JSON answers for licensing-environment examiner tasks that use TASK_ENV_BASE_URL endpoints and answer_template.json, including contractor eligibility batches, restricted liquor license staff packages, and alcohol renewal manual-review queues. Use when asked to fetch licensing records, apply policy records, map deficiency/risk/monitoring codes, build summaries, and return only schema-conformant JSON.
- ▌ Licensing Review JSON 4 · prism-shadow bundleProduce schema-conforming JSON for licensing-environment review tasks. Use when a prompt asks Codex to analyze task-environment records for contractor application eligibility batches, restricted liquor-license staff packages, or alcohol renewal manual-review queues, especially when outputs must match an answer_template.json exactly.
- ▌ Licensing Review JSON 5 · prism-shadow bundleProduce strict JSON answers for licensing-environment review tasks involving contractor eligibility batches, restricted liquor-license staff packages, and alcohol renewal manual-review queues. Use when a task references licensing APIs, /api/policies, contractor/liquor/alcohol endpoints, answer_template.json, eligibility determinations, restricted issuance controls, or renewal queue ranking.
- ▌ Licensing Review Solver · prism-shadowStructured licensing data-service review for contractor eligibility batches, restricted liquor-license staff packages, and alcohol renewal manual-review queues. Use when a prompt provides licensing environment endpoints plus a JSON answer template and asks Codex to return exact JSON decisions, risk codes, monitoring plans, queue ranks, or summaries for contractor applications, liquor premises controls, or alcohol renewal releases.
- ▌ Licensing Review Solver 2 · prism-shadow bundleSolve structured licensing review tasks that use a read-only task environment and require strict JSON answers, including contractor eligibility batches, restricted liquor-license staff packages, and alcohol renewal manual-review queues. Use when the prompt references licensing endpoints, policies, contractor applications/bonds/insurance/history/violations, liquor applications/settlements/privileges/incidents/site evidence, alcohol renewal licensees/violations/rules, or an answer_template.json schema.
- ▌ Licensing Record Review 3 · prism-shadowSolve structured licensing review tasks against a task environment. Use for contractor eligibility batches, restricted liquor-license staff packages, and alcohol renewal manual-review queues that require reading policies/rules and endpoint records, mapping evidence to constrained JSON schemas, ranking or summarizing records, and returning strict JSON only.
- ▌ Ma Deal Workbench JSON 9 · prism-shadow bundleUse when solving M&A deal workbench tasks that require fetching deal workbench API records and returning schema-conforming JSON legal work product, including buyer or seller issue registers, SPA or APA deviation matrices, closing packages, transition reviews, and committee escalation summaries.
- ▌ Northstar Payer Ops JSON 5 · prism-shadow bundleSolve Northstar Health Plan payer-operations tasks that require querying the read-only task environment and returning strict JSON for prior authorization determinations, pharmacy appeals and assistance intake, peer-to-peer closures, claim repricing, or UM-finance margin queues. Use when prompts mention Northstar payer operations, CASE/APPEAL/P2P/CLAIM/QUEUE identifiers, the /sql/query endpoint, policy criteria, authorization records, payment benchmarks, or service_margin rows.
- ▌ Northstar Payer JSON Review · prism-shadowSolve Northstar payer-operations tasks that require structured JSON from an HTTP task environment for authorization, appeal, claim repricing, peer-to-peer, or margin queue work.
- ▌ Ehr Quality Packets 4 · prism-shadow bundleBuild normalized JSON for EHR quality-governance tasks that provide a TASK_ENV_BASE_URL and an answer_template. Use for duplicate merge readiness packets, referral coordination packets, care transition handoffs, ServiceRequest/SBAR validation, and referral batch audits that require reading patient, referral, duplicate-candidate, provider, ICD-10, service-code, document, audit, disclosure, immunization, encounter, condition, medication, and allergy endpoints.
- ▌ Ehr Quality Packets 5 · prism-shadow bundleBuild normalized JSON packets and audits from a read-only EHR quality environment. Use when a task provides TASK_ENV_BASE_URL or EHR API endpoints and asks for duplicate-review, referral coordination, care-transition, ServiceRequest validation, or referral-batch audit JSON conforming to input/payloads/answer_template.json.
- ▌ Ehr Quality Governance · prism-shadow bundleUse for read-only EHR quality-governance tasks that require querying a task environment API and returning strict normalized JSON for duplicate reviews, merge readiness, referral coordination, ServiceRequest validation, care-transition packets, or referral batch audits using patient, provider, ICD-10, document, audit, and active-list evidence.
- ▌ Ehr Quality Packet Solver 2 · prism-shadowSolve EHR quality-governance tasks that require normalized JSON from a read-only task API, including duplicate-chart merge readiness, referral coordination, care-transition packets, ServiceRequest quality checks, and referral batch audits. Use when prompts mention EHR/referral/duplicate/care-transition/audit endpoints, `<TASK_ENV_BASE_URL>`, or an `answer_template.json` schema.
- ▌ Ehr Quality JSON Packets 2 · prism-shadowSolve read-only EHR quality-governance tasks by querying the allowed API endpoints and returning schema-conformant normalized JSON packets.
- ▌ Ehr Quality Packets 6 · prism-shadowSolve EHR quality-governance tasks that require normalized JSON from a read-only task environment, including duplicate-chart merge readiness, referral coordination, care-transition packets, ServiceRequest quality review, ICD/service-code validation, and referral batch audits. Use when prompts mention an EHR/referral quality API, duplicate candidates, patient active lists, providers, disclosures, documents, audit logs, or answer templates for normalized packet output.
- ▌ Clinic Protocol JSON 7 · prism-shadow bundleProduce schema-constrained JSON answers for synthetic clinic runtime tasks that require reviewing case records, observations, medications, allergies, imaging, care-registry, SDOH, and protocol materials from allowed clinic API endpoints. Use for protocol-bound clinical decision-support, observation-window retrieval, lab replacement, respiratory, head-injury, and care-management routing tasks that provide an answer_template.json and TASK_ENV_BASE_URL-style access.
- ▌ Clinic Protocol JSON 8 · prism-shadowProduce exact JSON answers for synthetic clinic protocol decision-support tasks that provide a runtime environment, a target case, patient clinical data, protocol material, and an answer_template.json schema. Use for respiratory, pediatric head injury, potassium replacement, observation-window, care-management, and similar clinic cases that require environment-backed facts, controlled enums, evidence identifiers, safety checks, and no prose outside JSON.
- ▌ Synthetic Clinic Protocol JSON 6 · prism-shadow bundleBuild protocol-bound JSON answers for synthetic clinic runtime tasks. Use when a prompt asks Codex to query a clinic task environment and return a structured answer_template JSON for cases involving FHIR-like patients, cases, observations, medications, allergies, problems, imaging, SDOH, care registry, respiratory CAP assessment, pediatric head injury triage, potassium replacement, observation-window gates, or care-management routing.
- ▌ Synthetic Clinic JSON Protocol · prism-shadowSolve synthetic clinic runtime tasks that require reading a prompt, task-provided answer template, and environment_access.md, querying read-only clinic API endpoints, applying protocol material to patient/case data, and returning one schema-exact JSON object. Use for clinical decision-support, lab-window, medication, respiratory, head-injury, care-management, and similar protocol-bound structured-answer tasks.
- ▌ Synthetic Clinic Protocol JSON 7 · prism-shadow bundleSolve synthetic clinic protocol tasks that require querying a read-only clinic runtime, applying patient/case/protocol evidence, and returning exactly one JSON object matching an answer_template.json schema. Use for respiratory CAP, pediatric head injury, potassium replacement, observation-window lab gates, care-management routing, or similar Harborview Synthetic Clinic decision-support tasks.
- ▌ Synthetic Clinic Protocol JSON 8 · prism-shadowSolve synthetic clinic protocol decision-support tasks that provide a prompt, answer_template.json, environment_access.md, and a read-only clinic runtime API. Use for protocol-bound JSON answers involving cases, patients, observations, imaging, allergies, medications, problems, care-management registry/SDOH data, and clinic protocol materials, including respiratory, head injury, potassium replacement, care-management routing, and lab-window gate tasks.
- ▌ Investigation Review JSON · prism-shadow bundleBuild schema-conforming JSON answers for Investigation Review Hub legal review tasks. Use when a prompt asks Codex to analyze subpoena, grand jury, SEC, DOJ, production-readiness, retention, preservation, privilege-log, QC, custodian-source, remediation, or cross-system dashboard evidence from a running Investigation Review Hub and return a single structured JSON object.
- ▌ Investigation Review Hub 2 · prism-shadow bundleUse when solving Investigation Review Hub legal review tasks that require a schema-conforming JSON answer from task-local payloads and the running hub API, including production gap analyses, retention or litigation-hold reviews, SEC/DOJ remediation dashboards, privilege/QC readiness reviews, source gap reviews, and prioritized action plans.
- ▌ Review Hub Remediation · prism-shadow bundleBuild schema-conforming Investigation Review Hub gap, retention, production-readiness, and remediation dashboard JSON outputs. Use when a task provides an Investigation Review Hub base URL, matter ID, answer_template.json, and asks Codex to identify preservation, collection, privilege-log, waiver, responsiveness/QC, retention, category coverage, metrics, or prioritized remediation actions.
- ▌ Peopleops Console Reconciliation 4 · prism-shadow bundleResolve PeopleOps Console evidence-reconciliation tasks across recruitment, leave, payroll, onboarding closeout, folder/notice review, and audit-heavy case checks. Use when a prompt asks you to open the runner URL, inspect authoritative records, apply source precedence over drafts or stale summaries, and return JSON that matches a provided answer template.
- ▌ Peopleops Reconcile · prism-shadow bundleReconcile PeopleOps Console records across employees, leave, payroll, recruitment, policy cases, documents, messages, and audit logs. Use when a task asks for authoritative source precedence, folder or notice readiness, payroll assignment readiness, recruitment outcome reconciliation, closeout control decisions, or a normalized JSON answer from the task environment.
- ▌ Peopleops Console Controls · prism-shadow bundleSolve PeopleOps Console verification tasks that ask for final JSON from employee, case, leave, payroll, recruitment, document, message, policy, or audit records. Use when the prompt mentions PeopleOps Console, onboarding closeout, remote-work exception review, leave source precedence, payroll assignment readiness, recruitment reconciliation, folder readiness, formal notice quality, or normalized business labels from an answer template.
- ▌ Peopleops Lifecycle Reconciliation 2 · prism-shadowSolve PeopleOps Console lifecycle verification tasks by reconciling authoritative HR, leave, payroll, recruitment, document, notice, policy, and audit evidence into exact-template JSON.
- ▌ Peopleops Evidence JSON · prism-shadow bundleResolve PeopleOps Console evidence tasks and produce strict JSON answers. Use when a task asks Codex to verify onboarding closeout, remote-work case readiness, leave source precedence, payroll/accrual readiness, recruitment reconciliation, folder/notice defects, audit scope, or normalized People Ops control labels from an answer_template.json file.
- ▌ Peopleops Reconcile 2 · prism-shadowSolve PeopleOps Console reconciliation and control tasks that require strict JSON answers from a task-provided answer template. Use when asked to verify onboarding closeout, remote-work or lifecycle folder readiness, leave source precedence, payroll assignment/accrual readiness, recruitment outcome packets, notice defects, audit scope, or cross-module People Ops controls against the running task environment.
- ▌ Cedar Ridge Intake 5 · prism-shadow bundleSolve Cedar Ridge Intake Coordination Portal tasks that require reconciling patient intake rosters, referral batches, dialysis transfers, chronic-care program candidates, documents, chart artifacts, ICD metadata, insurance/PBM/pharmacy, and capacity data into strict JSON answer templates. Use when the task references the Cedar Ridge Intake Coordination Portal, TASK_ENV_BASE_URL, Cedar Ridge access verification, referral readiness, referral-to-chart activation, dialysis transfer review, or chronic-care enrollment panels.
- ▌ Cedar Ridge Intake JSON · prism-shadow bundleSolve Cedar Ridge Intake Coordination Portal tasks that require reconciling healthcare intake data and returning a controlled JSON object. Use for new-patient access verification, referral readiness or chart activation, dialysis transfer review, chronic-care program enrollment, and similar portal tasks involving answer_template.json, patient/referral/transfer/program records, ICD metadata, documents, benefits, pharmacies, capacity, chart artifacts, or cohort summaries.
- ▌ Cedar Ridge Intake Reconciliation 8 · prism-shadow bundleComplete Cedar Ridge Intake Coordination Portal audit tasks that require strict JSON answers from an answer_template, including patient access verification, specialty referral readiness, referral-to-chart activation, dialysis transfer packet and capacity review, and chronic-care program enrollment reconciliation.
- ▌ Cedar Ridge Intake JSON 2 · prism-shadowSolve Cedar Ridge Intake Coordination Portal tasks that require reconciling roster, referral, dialysis transfer, chart, program, pharmacy, coverage, PBM, document, capacity, or ICD data into a strict JSON answer template.
- ▌ Cedar Ridge Intake JSON 3 · prism-shadowSolve Cedar Ridge Intake Coordination Portal tasks that require JSON-only healthcare intake outputs, including new-patient access verification, specialty referral readiness audits, dialysis transfer packet/capacity reviews, chronic-care enrollment panels, and referral-to-chart activation files. Use when the prompt names the Cedar Ridge portal, a task environment base URL, and an answer_template.json with controlled output values.
- ▌ Cedar Ridge Intake JSON 4 · prism-shadow bundleSolve Cedar Ridge Intake Coordination Portal tasks that require strict JSON from read-only portal records and answer_template schemas, including new-patient access verification, referral readiness and chart activation, dialysis transfer packet and capacity review, and chronic-care enrollment panels.
- ▌ Northstar Payer Ops 13 · prism-shadow bundleSolve Northstar Health Plan payer operations tasks that require reviewing the shared task environment and returning strict JSON. Use for utilization management determinations, pharmacy appeals and manufacturer assistance intake, peer-to-peer summaries, payment integrity claim repricing, and UM-finance margin queue analysis when prompts reference Northstar, payer operations, authorization cases, appeals, claims, P2P events, service-margin queues, answer_template.json, or TASK_ENV_BASE_URL.
- ▌ Northstar Payer Ops JSON 3 · prism-shadow bundleSolve Northstar payer operations tasks that require retrieving authorization, appeal, claim, policy, document, rate schedule, P2P, or service-margin records from the task environment and returning a strict JSON object matching an answer_template.json schema. Use for UM determinations, pharmacy appeal intake, payment integrity repricing, peer-to-peer summaries, and payer-service margin queue summaries.
- ▌ Northstar Payer Ops 14 · prism-shadow bundleProduce strict JSON answers for Northstar Health Plan payer-operations tasks that use the shared task environment, task_context.json, and answer_template.json. Use for prior authorization determination summaries, pharmacy appeals and manufacturer assistance intake, payment integrity claim repricing, peer-to-peer authorization closure, and therapy margin queue analysis requiring case, policy, document, rate schedule, appeal, or SQL evidence.
- ▌ Northstar Payer Ops JSON 4 · prism-shadow bundleSolve Northstar Health Plan payer-operations tasks that require querying the shared task environment and returning structured JSON for utilization management authorizations, pharmacy appeals and assistance intake, payment-integrity claim repricing, peer-to-peer summaries, and service-margin queues. Use when the task mentions Northstar, payer operations, UM, appeals, claims, P2P, margin queues, an answer_template.json contract, or the SQL endpoint.
- ▌ Finance Ops Reporting 8 · prism-shadow bundleSolve Crescent Finance Ops JSON reporting tasks from prompt, environment_access.json, request_memo.json, and answer_template.json. Use when asked to produce branch close, regional, compensation, payroll, or forecast reports from the staged API and return one strictly shaped JSON object.
- ▌ Crescent Finance Ops 4 · prism-shadow bundleSolve Crescent Finance Ops API reporting tasks for branch and regional finance, orchestra compensation summaries and forecasts, and weekly theatre payroll reviews from task payloads.
- ▌ Crescent Finance Ops Reporting 6 · prism-shadow bundleSolve Crescent Finance Ops management reporting, compensation, forecast, and payroll JSON tasks from the live business API.
- ▌ Crescent Finance Ops Reporter · prism-shadow bundleProduce Crescent Arts Collective Finance Ops reporting JSON by fetching active API data and applying the staged finance, compensation, and payroll rules.
- ▌ Asteria Portfolio Decisions · prism-shadow bundleUse when an Asteria Investment Office task needs live environment lookup and a strict JSON answer for credit trades, correlation reviews, allocation views, or committee risk decisions.
- ▌ Skill 3 · prism-shadow bundleProduce strict JSON answers for Asteria Investment Office portfolio tasks using the live portfolio, bond, index, allocation, prior-view, and macro-signal records. Use when solving staged requests for energy-credit trades, fixed-income rotations, correlation reviews, allocation views, or committee decision files that may include stale local notes.
- ▌ Asteria Investment Office JSON 7 · prism-shadow bundleBuild Asteria Investment Office portfolio decision JSON from the shared Asteria environment and local answer templates. Use when Codex is asked to prepare Asteria PF-* outputs such as energy-credit trade packages, international equity correlation reviews, active allocation view refreshes, fixed-income risk rotations, or committee decision files that require current portfolio records, policy thresholds, index levels, macro signals, instruments, issuers, and strict JSON schemas.
- ▌ Asteria Investment JSON Solver · prism-shadow bundleSolve Asteria Investment Office JSON tasks that require using the shared read-only environment plus local prompt payloads for portfolio credit trades, fixed-income risk rotations, equity index correlations, active allocation views, and multi-asset committee decision files.
- ▌ Solve Asteria Investment JSON · prism-shadow bundleSolve Asteria Investment Office portfolio JSON tasks that require combining local request payloads and answer templates with the shared Asteria environment for credit trades, fixed-income risk rotations, equity correlation reviews, active allocation views, and committee decision files.
- ▌ Asteria Investment Office Solver · prism-shadow bundleSolve Asteria Investment Office JSON tasks by combining local payload contracts with the live read-only Asteria environment.
- ▌ Credit Office Solver · prism-shadow bundleSolve staged credit-office public API tasks that require strict JSON answers for branch portfolio regrades, lending allocations, credit-union segment posture pages, watch-list stress packets, or competing CRE decisions. Use when the prompt references the runner-supplied TASK_ENV_BASE_URL, public API endpoints, or a required answer_template.json.
- ▌ Credit Office Packet Solver · prism-shadow bundleSolve staged public credit-office API committee packets into schema-matched JSON for branch rating regrades, lending allocations, segment posture reviews, watch-list stress packets, and competing CRE decisions. Use when prompts reference TASK_ENV_BASE_URL, branch/segment IDs, loan or application reviews, public policy or benchmark endpoints, or `input/payloads/answer_template.json`.
- ▌ Credit Office API Pack · prism-shadow bundleSolve committee-style JSON cases from the public credit office API, including branch loan regrades, lending allocations, credit-union segment posture reviews, watch-list stress packets, and competing CRE decisions. Use when a prompt names a branch, segment, applications, benchmark tables, and a strict JSON template.
- ▌ Credit Office Committee JSON 2 · prism-shadowSolve credit office public-API committee packet tasks by deriving branch, loan, application, benchmark, and credit-union metrics into the requested JSON template.
- ▌ Credit Office Committee JSON 3 · prism-shadowSolve credit office public API lending-committee JSON tasks, including branch loan regrades, pending application allocation, CRE comparisons, watch-list stress reviews, and credit-union segment posture packets.
- ▌ Credit Office Committee JSON 4 · prism-shadowSolve credit-office lending committee tasks by deriving JSON answers from the public API, policy rules, benchmarks, and the supplied answer template.
- ▌ Procureops Control Files · prism-shadowSolve ProcureOps business-control JSON tasks that require combining local packet or memo anchors with the shared read-only ProcureOps API for sourcing nomination readiness, receiving/AP reconciliation, payment hold/release closeout, contract amendment change control, supplier risk context, budget checks, and chargeback-based AP release files.
- ▌ Procureops Reconcile · prism-shadow bundleSolve ProcureOps sourcing, receiving, AP hold/release, payment close, contract-change, budget, and vendor-risk reconciliation tasks. Use when a task references the ProcureOps API, TASK_ENV_BASE_URL, local input/payloads memos, or an answer_template JSON and asks for a JSON operational decision packet.