prism-shadow
- 1.7k skills
- 0 followers
- 5 days ago last updated
- ▌ Northwind Erp Desk · prism-shadow bundleSolve Northwind ERP memo-and-template tasks from live ERP data, including order release, mixed-warehouse allocation, replenishment planning, supplier incident scorecards, and supplier quality controls. Use when a task references the Northwind ERP API, staged payload files, or an answer template and requires strict JSON output.
- ▌ Northwind Erp Solver · prism-shadow bundleSolve Northwind Components ERP decision tasks that require live API lookups and exact JSON output. Use when a prompt provides a Northwind memo and answer template for expedite queues, kit replenishment plans, supplier incident scorecards, warehouse transfer allocation, or procurement-control decisions.
- ▌ Northwind Erp Decisions 2 · prism-shadow bundleSolve Northwind Components ERP decision tasks that require strict JSON output from live API data. Use when a prompt references the shared Northwind ERP API, a memo or answer template, and asks for order dispatch, replenishment, supplier incident scorecards, allocation decisions, or procurement controls.
- ▌ Northwind Erp Operations · prism-shadowSolve Northwind Components ERP API tasks that ask for strict JSON decisions for fulfillment waves, warehouse transfers, BOM replenishment, supplier incident scorecards, or procurement quality holds.
- ▌ Northwind Erp Control JSON · prism-shadowSolve Northwind Components ERP control tasks that require strict JSON answers from local memo/template payloads and the shared Northwind ERP API. Use for expedite dispatch, mixed-warehouse allocation, kit replenishment, supplier incident scorecards, and procurement quality-hold reviews where Codex must fetch live ERP records, apply memo/template rules, compute inventory or incident metrics, and return only schema-conforming JSON.
- ▌ Northwind Erp JSON Solver · prism-shadow bundleSolve Northwind Components ERP API tasks that require strict JSON answers from local prompt payloads, answer templates, and public ERP endpoints for orders, inventory, products, customers, suppliers, incidents, BOMs, purchase orders, warehouses, and shipping quotes.
- ▌ Wealth Advisory Planning 2 · prism-shadow bundleBuild client-specific private-wealth advisory JSON for Roth conversion and RMD summaries, ILIT Crummey funding cycles, GRAT versus CRAT comparisons, and estate-liquidity action plans from the staged advisory API. Use when a prompt asks for a strict JSON object that reconciles signed profiles, custodian exports, life-insurance policies, trust candidates, tax constants, and RMD factors.
- ▌ Advisory Planning JSON 2 · prism-shadow bundleGenerate structured JSON outputs for private wealth advisory planning tasks that use the task-group advisory API, including Roth/RMD conversion summaries, ILIT Crummey funding cycles, GRAT versus CRAT trust comparisons, and combined estate liquidity action plans. Use when the prompt provides API_BASE or an advisory API base URL, a client ID, request memo, and answer_template.json.
- ▌ Advisory Planning JSON 3 · prism-shadow bundleProduce private wealth advisory planning JSON from a task memo, answer template, and the advisory API. Use for Roth conversion/RMD summaries, ILIT Crummey funding cycles, GRAT versus CRAT comparisons, and estate liquidity action plans that require resolving conflicting client records and returning only structured JSON.
- ▌ Private Wealth Advisory JSON 2 · prism-shadow bundleSolve private wealth advisory JSON tasks using the task API, source-resolution rules, and deterministic estate, ILIT, trust, and Roth/RMD calculations.
- ▌ Wealth Advisory API Planning · prism-shadowSolve private wealth advisory task-group API planning outputs as schema-conforming JSON. Use when Codex must read a local prompt, request memo, and answer_template.json, fetch advisory records from the provided API, resolve conflicting client/source data, and compute Roth conversion/RMD, ILIT Crummey, GRAT/CRAT, or estate-liquidity action-plan fields.
- ▌ Wealth Advisory Planning JSON · prism-shadowSolve private wealth advisory planning tasks that require JSON outputs from the advisory API, including Roth/RMD projections, ILIT Crummey funding checks, GRAT/CRAT comparisons, and estate liquidity action plans.
- ▌ Crescent Finance Ops Reports · prism-shadow bundleSolve Crescent Finance Ops reporting tasks from the staged API data. Use when asked to prepare branch close packages, regional management views, current-year or forecast compensation summaries, or weekly payroll reviews from the Crescent Finance Ops environment.
- ▌ Finance Ops Reporting 7 · prism-shadow bundleSolve Crescent Finance Ops reporting tasks that provide prompt.txt plus payloads/request_memo.json, environment_access.json, and answer_template.json. Use for branch close, regional management, compensation current-year or forecast, and weekly payroll JSON answers from the Finance Ops API.
- ▌ Apexcloud Retention Ops 13 · prism-shadow bundleProduce exact JSON reports from the ApexCloud Retention Operations API and churn export files. Use when a prompt references the task environment, asks for renewal-risk, QBR, receivables, retention-board, or churn-validation outputs, or needs data assembled from /api/accounts, /api/opportunities, /api/finance/ar-aging, /api/hr/summary, /api/events/performance, or /exports/churn/*.csv.
- ▌ Apexcloud Retention Ops 14 · prism-shadowSolve ApexCloud Retention Operations API tasks that require JSON-only customer success, renewal risk, QBR, receivables, pipeline, operations, or churn-export outputs. Use when prompts mention the ApexCloud Retention Operations API, billing snapshots, A/R aging, account metrics, support tickets, NPS, opportunities, HR/event operations context, or churn CSV exports.
- ▌ Apexcloud Retention Ops 15 · prism-shadowSolve ApexCloud Retention Operations API tasks that require customer success, billing, receivables, pipeline, event, HR, or churn-export analysis and JSON-only business outputs.
- ▌ Apexcloud Retention Ops 16 · prism-shadowSolve ApexCloud Retention Operations API tasks that ask for customer success, renewal risk, QBR metrics, receivables, pipeline, event/HR context, or churn-ranking JSON outputs. Use when a prompt references the ApexCloud Retention Operations API, account metrics, tickets, NPS, billing snapshots, A/R aging, opportunities, HR summaries, event performance, churn CSV exports, or controlled retention policy/action codes.
- ▌ Apexcloud Retention Ops 17 · prism-shadow bundleSolve ApexCloud Retention Operations API tasks for customer success and revenue operations, including QBR metrics packets, renewal risk queues, high-touch retention boards, Q3 receivables and pipeline reviews, and churn validation or outreach ranking from ApexCloud account, metrics, support, NPS, billing snapshot, A/R aging, opportunities, HR/event, and churn export endpoints.
- ▌ Finance API Controls · prism-shadow bundleReconcile finance and compliance control batches against a runner-provided JSON API and return schema-conforming JSON. Use when a task asks Codex to decide AP reimbursement close status, stale AP snapshot corrections, vendor onboarding or payment-release controls, or prepaid schedule-versus-GL close results using TASK_ENV_BASE_URL and local payload templates.
- ▌ Erp Finance Risk Review · prism-shadow bundleSolve ERP/compliance JSON API finance-risk tasks for reimbursement/AP close review, stale AP export refresh, vendor onboarding release control, account-change payment release, and prepaid close reconciliation. Use when a prompt provides a runner API base URL plus local payloads or answer templates and asks for current-system JSON decisions from task_group_005-style claims, AP bills/payments, vendors, compliance, prepaids, GL balances, or close logs.
- ▌ Finance API Close Review · prism-shadow bundleSolve shared ERP finance API tasks that require JSON-only reimbursement/AP close decisions, stale AP snapshot correction, prepaid amortization and GL reconciliation, vendor onboarding finance-risk release calls, or account-change payment release reviews. Use when a task supplies TASK_ENV_BASE_URL or a local input payload plus an answer_template and asks Codex to reconcile current API evidence into a close, release, hold, block, or exception output.
- ▌ Task Group 005 Finance Reconciliation 2 · prism-shadowSolve task_group_005 finance close, AP reimbursement, prepaid, vendor onboarding, and payment-release tasks using local scope payloads plus the current ERP/compliance API.
- ▌ Erp Finance Review · prism-shadowSolve finance-review tasks against the shared ERP/compliance API, including reimbursement/AP close batches, stale AP snapshot reconciliation, vendor onboarding release control, account-change payment release reviews, and prepaid close reconciliations. Use when a prompt provides a TASK_ENV_BASE_URL plus local payload templates/scope files and asks for a JSON decision or close report from current API records.
- ▌ API Finance Close Review · prism-shadowSolve API-backed finance close, reimbursement/AP release, vendor compliance release, account-change review, and prepaid reconciliation tasks using local payload scope plus a runner-provided JSON API.
- ▌ Procureops Task Solver · prism-shadow bundleSolve ProcureOps task-group JSON packets from local memos and the shared task API. Use when prompts reference ProcureOps, the task environment, and templates for nomination readiness, receiving closeout, AP close, change-control, or AP release decisions.
- ▌ Procureops Reconciliation 3 · prism-shadow bundleSolve ProcureOps sourcing nomination, receiving closeout, AP close, change-control, and release JSON tasks from a local packet or memo plus the live ProcureOps API. Use when a prompt asks for a strict JSON object that reconciles procurement records, budgets, approvals, receipts, invoices, vendor risk, or chargebacks.
- ▌ Procureops Reconciliation 4 · prism-shadow bundleSolve ProcureOps sourcing, receiving, AP close, change-control, and invoice-release reconciliation tasks. Use when a task provides a local memo or answer_template and asks Codex to query the read-only ProcureOps API, join suppliers, items, programs, contracts, requisitions, purchase orders, receipts, AP invoices/payments, approvals, budgets, and vendor-risk records, compute USD or quantity decisions, and return exact JSON only.
- ▌ Solve Procureops JSON · prism-shadowSolve ProcureOps operational reconciliation tasks that require JSON-only answers from a task prompt, local payload files, an answer template, and the shared ProcureOps API. Use for procurement sourcing readiness, receiving/AP variance closeout, AP payment holds, change-control budget/approval checks, supplier risk checks, chargeback net-release files, and similar tasks involving suppliers, items, programs, contracts, purchase requisitions, purchase orders, receipts, AP invoices, payments, approvals, budget snapshots, or vendor risk events.
- ▌ Harborcrm Prepare · prism-shadow bundlePrepare HarborCRM event handoff, trade-show prospecting, and import-cleanup JSON outputs from task API data and a provided template. Use when a prompt names HarborCRM records, asks for sponsor status reconciliation, exhibitor qualification, contact import cleanup, normalization, exclusion counts, due dates, or any other strict JSON handoff from the HarborCRM task environment.
- ▌ Harborcrm Reconciliation 2 · prism-shadowSolve HarborCRM API-backed CRM handoff, trade-show prospecting, and import-batch cleanup tasks that require exact JSON output from an answer template.
- ▌ Harborcrm Handoff Solver 2 · prism-shadowSolve HarborCRM CRM handoff, trade-show prospecting, and import-cleanup tasks by fetching the public API data, applying CRM qualification rules, and returning template-shaped JSON only.
- ▌ Harborcrm Reconciliation 3 · prism-shadowSolve HarborCRM API tasks that require CRM, event, tradeshow, sponsor, campaign-member, or import-batch reconciliation into an exact JSON answer template.
- ▌ Medbridge Sales Ops 5 · prism-shadow bundleUse for MedBridge Sales Ops API tasks that require account-ready JSON matching a provided answer template, including RFQ or quote pricing, EXW and freight decision packages, catalog tier selection, quote policies, opportunity milestone reconciliation, payments, revenue recognition, events, vouchers, and follow-up actions.
- ▌ Medbridge Sales Ops 6 · prism-shadow bundleSolve MedBridge Sales Ops API tasks that require account-ready JSON for quotes, RFQs, freight decisions, opportunities, invoices, payments, revenue journals, events, and vouchers. Use when the prompt asks Codex to query a shared MedBridge Sales Ops task API and return JSON matching an answer_template.json.
- ▌ Medbridge Sales Ops 7 · prism-shadow bundlePrepare MedBridge Sales Ops quote, freight, RFQ module, and account reconciliation JSON using the task environment API. Use when the prompt mentions the MedBridge Sales Ops API, quote or RFQ decision packages, EXW pricing, freight comparison, catalog tiers, policies, opportunity milestones, invoices, payments, revenue journals, events, vouchers, or an answer_template JSON.
- ▌ Medbridge Sales Ops JSON 3 · prism-shadowPrepare JSON-only MedBridge Sales Ops quote and engagement reconciliation packages from the task API.
- ▌ Medbridge Sales Ops JSON 4 · prism-shadow bundleSolve MedBridge Sales Ops API tasks that require account-ready JSON for quote/RFQ pricing, freight decisions, opportunity reconciliation, invoice/payment/revenue-recognition status, and event or voucher follow-up actions using a provided answer template.
- ▌ Medbridge Sales Ops Solver · prism-shadow bundleSolve MedBridge Sales Ops API tasks that require quote/freight decisions or account, invoice, revenue, event, and voucher reconciliations.
- ▌ Support Console Batch Solver · prism-shadow bundleResolve staged support-console batch tasks by querying the task environment API, joining ticket, case, line, device, bill, plan, outage, diagnostics, troubleshooting, and enterprise records, and returning exact JSON that matches the provided answer template. Use when the prompt points to the shared support console and asks for ticket triage, mobile queue actions, queue-quality review, or enterprise export response packages.
- ▌ Support Console · prism-shadow bundleResolve structured support-console tasks from staged payloads and task-environment API evidence, including offline ticket triage, contact-center case routing, queue-quality reviews, enterprise export complaint packages, and mobile-data recovery. Use when prompts mention the support-console API, the task-environment base URL, support records, or an exact JSON answer template.
- ▌ Support Console Resolver 2 · prism-shadow bundleResolve support-console tasks that require using a shared support console API to classify service tickets, mobile/contact-center cases, mobile-data recovery worklists, or enterprise export incidents and return strict JSON answers matching a provided answer_template.json. Use when prompts mention support operations, support-console records, same-day ticket batches, queue-quality handoff, mobile support queues, mobile data recovery, or enterprise export complaint response packages.
- ▌ Support Console Operations 2 · prism-shadowSolve support-console operations tasks that require API-backed JSON decisions for service tickets, mobile cases, and enterprise export incidents.
- ▌ Support Console Resolution · prism-shadowSolve support-console ticket, mobile case, and enterprise export response tasks that require payload parsing plus read-only API evidence.
- ▌ Support Console Operations Solver · prism-shadowSolve support-console ticket, mobile case, and enterprise export response tasks by querying the read-only task API and filling the provided JSON template.
- ▌ Apexcloud Retention Ops 12 · prism-shadow bundleBuild strict JSON reports from the ApexCloud Retention Operations API for customer success QBR metrics, renewal risk queues, receivables and pipeline operations reviews, retention action boards, and churn export validation or outreach ranking. Use when a task mentions ApexCloud, Retention Operations API, account health metrics, billing snapshots, A/R aging, support/NPS, opportunities, HR/event context, or churn CSV exports.
- ▌ Asteria Fleet Audit · prism-shadow bundleAudit Asteria Fleet Data Quality Hub tasks and produce strict JSON reconciliation answers for fleet contacts, field rosters, fuel or freight transactions, source snapshots, maintenance history, duplicate resolution, quarantine, mismatch reporting, normalized totals, rankings, certification gates, and opaque control-code panels. Use when a prompt references Asteria Fleet, TASK_ENV_BASE_URL, case_scope.json, answer_template.json, source snapshots, or the Hub query API.
- ▌ Asteria Fleet Dq Audit 4 · prism-shadow bundleSolve Asteria Fleet Data Quality Hub reconciliation, normalization, and certification tasks. Use for prompts mentioning the Asteria Fleet Data Quality Hub, source snapshots, authoritative snapshots, duplicate logical records, contact readiness, fuel or freight transaction audits, maintenance history integrity, quarantine rows, compact internal control codes, or strict JSON answer contracts.
- ▌ Asteria Hub Reconciliation · prism-shadow bundleUse this skill for Asteria Fleet Data Quality Hub audit tasks that ask Codex to reconcile contacts, fuel transactions, freight charges, or maintenance events from task payloads, environment_access.md, and a JSON answer template. It guides schema-first hub extraction, snapshot selection, deduplication, quarantine handling, unit and FX normalization, contact readiness, maintenance history validation, ranking panels, and compact Asteria control-code decisions.
- ▌ Atlas Commerce Ops 3 · prism-shadow bundleUse this skill for Atlas Commerce Operations workplace tasks that ask for strict JSON answers from an authenticated TASK_ENV_BASE_URL service, /api/schema, /api/data-dictionary, /api/sql, or /api/sql/transaction. It is especially relevant for cutoff-based fulfillment, refund, carrier quality, warehouse productivity, inventory, payments, support-health, and controlled correction tasks that require SQL over the Atlas Commerce Operations database and saving answer.json.
- ▌ Atlas Ops SQL Solver · prism-shadow bundleUse this skill for Atlas Commerce Operations tasks that require exact JSON answers from prompt payloads and the authenticated Atlas database, including cutoff-based fulfillment scorecards, refund reconciliation, carrier-scan canonical corrections, warehouse productivity reviews, support health reviews, and similar operational analytics. It guides schema discovery, SQL against the Atlas API, de-duplication of source imports, event-timeline logic, controlled corrections, rounding, ordering, risk/status rules, and answer.json validation.
- ▌ Atlas Commerce Ops SQL · prism-shadow bundleUse this skill whenever a task asks for Atlas Commerce Operations workplace analysis, scorecards, reconciliations, SLA reviews, warehouse or fulfillment metrics, refund/payment exposure, carrier scan corrections, inventory operations, or strict answer.json generation from the task environment SQL APIs. It guides schema discovery, safe SQL, controlled correction transactions, metric construction from payload rules, and exact JSON output validation.
- ▌ Pho Observatory Audits · prism-shadow bundleUse this skill for Public Health Observatory audit tasks that provide an analysis_request.json and answer_template.json, require evidence only from the PHO Web portal, or mention exact PHO protocols such as 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 audits. It helps produce the final JSON answer with strict release resolution, ordered statistical diagnostics, reproducibility checkpoints, and controlled decisions.
- ▌ Public Health Observatory Audits · prism-shadow bundleUse this skill for Public Health Observatory tasks that require solving registered state, county, or country audit analyses from a read-only PHO Web portal and returning a strict JSON answer_template result. Trigger on prompts mentioning PHO, Public Health Observatory, protocol_id values such as PHO_STATE_TRANSPORT_AUDIT_V1, PHO_COUNTY_MEDIATION_TRANSPORT_V1, PHO_STATE_ROBUSTNESS_TRANSPORT_V1, PHO_COUNTY_PANEL_TRANSPORT_V1, or country burden revision audits, especially when the task asks for publication/cohort resolution, jackknife, nested ridge or elastic-net, wild bootstrap, grouped conformal calibration, PCA clustering, source perturbation, or controlled decisions.
- ▌ Pho Algorithmic Audits 2 · prism-shadow bundleUse for Public Health Observatory portal tasks that require a JSON-only answer from analysis_request.json and answer_template.json, especially PHO_* protocol_id audits, registered multi-module statistical audits, release/cohort reconciliation, bootstraps, grouped validation, PCA/clustering, source perturbation, or controlled decision gates.
- ▌ Engineering Portfolio Review 2 · prism-shadow bundleSolve engineering portfolio environment review tasks that ask for JSON answers from shared work-item APIs, including portfolio mix, SLA aging, release readiness, blockers, dependencies, duplicate handling, and stale mirror field avoidance. Use this skill whenever a task mentions work items, mix targets, SLA policy, release readiness, blockers, dependencies, or a shared task environment with an answer_template.json.
- ▌ Engineering Portfolio Env · prism-shadowSolve JSON audit tasks against the shared engineering portfolio task environment. Use for portfolio mix reviews, SLA aging and breach audits, release readiness assessments, milestone completion, blocker and dependency analysis, duplicate/cancelled exclusions, stale mirror/export field handling, and exact answer_template.json output from work-items, mix-targets, SLA policy, releases, milestones, blockers, dependencies, or restricted query endpoints.
- ▌ Engineering Portfolio Auditor 2 · prism-shadow bundleSolve endpoint-backed engineering portfolio audit tasks that ask for JSON calculations over work items, portfolio mix targets, SLA aging, duplicate clusters, blockers, dependencies, milestones, or release readiness. Use this skill whenever the prompt mentions a shared task environment, work items, mix targets, SLA policy, release readiness, portfolio categories, stale mirror fields, or duplicate/cancelled engineering records.
- ▌ Harborcrm JSON Handoff 2 · prism-shadow bundleSolve HarborCRM API tasks that ask Codex to produce CRM-ready JSON handoffs from event, trade-show, sponsor, finance, badge, import-batch, CRM account, contact, campaign-member, policy, or meeting-interest data. Use when a prompt references HarborCRM, answer_template.json, CRM import cleanup, event sponsor or badge reconciliation, trade-show prospect qualification, duplicate or suppression handling, lead handoff, or campaign-member action summaries.
- ▌ Harborcrm Audit · prism-shadow bundleAudit HarborCRM event handoffs, trade-show prospecting lists, and import batches. Use when a prompt asks to reconcile sponsor finance, badge scans, campaign members, exhibitors, duplicates, suppression, contact hygiene, or other HarborCRM API records and return structured JSON.
- ▌ Ehr Quality JSON 2 · prism-shadow bundleUse this skill for EHR quality-governance tasks that require reading a read-only task environment API and returning normalized JSON packets, especially duplicate-chart merge readiness, referral coordination, care-transition handoffs, ServiceRequest validation, ICD-10/service-code checks, provider contact lookup, and referral batch audits. Use it whenever the prompt mentions EHR, referrals, duplicate candidates, patient active lists, handoff packets, audit queues, ICD validation, or strict answer_template JSON.
- ▌ Synthetic Clinic Protocol JSON 5 · prism-shadow bundleUse this skill whenever a task asks for a structured JSON clinical decision-support, protocol assessment, care-management routing, potassium/lab gate, respiratory, or pediatric head-injury response from the synthetic clinic runtime environment. It is especially relevant when the prompt mentions Harborview Synthetic Clinic, a CASE-* id, input/payloads/answer_template.json, environment_access.md, or a requirement to return only one JSON object.
- ▌ Clinic Protocol JSON 6 · prism-shadow bundleSolve synthetic clinic runtime tasks that ask for protocol-bound clinical decision-support or care-management results as a strict JSON object. Use this whenever a prompt provides a TASK_ENV_BASE_URL, environment_access.md, a target clinic case id, and an input/payloads/answer_template.json schema for respiratory, head-injury, potassium, lab-window, care-management, or similar structured clinic protocol assessments.
- ▌ Synthetic Clinic JSON · prism-shadow bundleSolve synthetic clinic decision-support tasks that require reading a runtime clinic API, applying case-specific protocol material, and returning only a schema-conformant JSON object. Use for prompts mentioning synthetic clinic cases, TASK_ENV_BASE_URL, answer_template.json, protocol-bound routing or assessment, lab window gates, medication/repletion decisions, red flags, disposition, or evidence identifiers.
- ▌ Investigation Review Hub Remediation JSON · prism-shadow bundleUse this skill whenever a task asks for a structured JSON gap analysis, production-readiness review, retention/preservation review, or cross-system remediation dashboard from an Investigation Review Hub. It is tailored for legal subpoena or regulatory-review matters where the answer must use hub record IDs, request category codes, privilege/QC/retention/source evidence, numeric metrics, prioritized actions, and a provided answer_template.json.
- ▌ Investigation Review Hub Remediation 4 · prism-shadow bundleUse this skill whenever a task asks for a structured JSON legal review, production-readiness review, retention or preservation gap analysis, privilege/QC remediation dashboard, or subpoena response dashboard using the Investigation Review Hub. It is especially relevant when the prompt mentions matter IDs, subpoena categories, custodial sources, retention events, privilege logs, QC findings, remediation actions, or an answer_template.json that must be followed exactly.
- ▌ Investigation Review Hub Gap Analysis 10 · prism-shadow bundleUse this skill whenever a task asks for a structured JSON legal or eDiscovery analysis from an Investigation Review Hub, especially subpoena, grand jury, SEC, DOJ, production readiness, remediation dashboard, retention gap, privilege-log, QC, or custodian-source gap tasks with TASK_ENV_BASE_URL and input/payloads/answer_template.json. It guides Codex to query the hub as source of record, normalize stable IDs and category impacts, compute metrics, and return schema-valid JSON only.
- ▌ Court Closeout Reconciliation 8 · prism-shadowUse this skill for clerk-ready court closeout, disposition register, traffic citation, sentencing packet, financial petition, probation referral, license suspension, payment-plan, fee reconciliation, or Court Operations Portal JSON tasks. Trigger whenever the user asks to reconcile local court payloads with portal records and return a structured JSON answer for criminal or traffic matters.
- ▌ Court Operations Closeout 4 · prism-shadow bundleReconcile court closeout, disposition register, traffic citation, payment-plan, probation referral, and license/order packets from local case materials plus a Court Operations Portal API. Use for strict JSON clerk workflows involving sentencing closeouts, criminal financial registers, traffic violation payments, fee schedules, payment policies, forms, financial petitions, unsupported-fee exclusions, and missing-field placeholders.
- ▌ Court Closeout JSON · prism-shadow bundlePrepare structured court clerk closeout JSON from local payloads and a Court Operations Portal. Use for criminal disposition registers, traffic violation payment plans, sentencing closeout packets, probation or license-suspension forms, financial petitions, fee-schedule reconciliation, unsupported-fee exclusions, placeholder handling, and exact answer_template-driven JSON outputs.
- ▌ Licensing Data Review · prism-shadow bundleUse this skill for state licensing or regulatory review tasks that require querying a task environment and returning strict JSON decisions, staff packages, or manual-review queues. It is especially relevant for contractor application eligibility batches, restricted liquor-license transfer or renewal packages, and alcohol renewal release queues involving policies, applications, bonds, insurance, license history, violations, correspondence, settlements, privileges, incidents, site evidence, or renewal rules.
- ▌ Licensing Env Review · prism-shadow bundleSolve structured licensing review tasks against a provided task environment. Use this skill when Codex is asked to return schema-constrained JSON for contractor application eligibility batches, restricted liquor-license staff packages, alcohol or liquor renewal manual-review queues, or similar licensing endpoint reviews involving /api/policies, contractor, liquor, alcohol, renewal, or optional SQL endpoints plus input/payloads/answer_template.json.
- ▌ Licensing JSON Review · prism-shadow bundleUse this skill for structured licensing-environment JSON tasks involving contractor application eligibility batches, restricted liquor-license staff packages, or alcohol renewal manual-review queues. Use it when the prompt mentions TASK_ENV_BASE_URL, licensing API endpoints, answer_template.json, policy-backed deficiency or control codes, or renewal queue ranking.
- ▌ Ma Deal Workbench JSON 8 · prism-shadow bundleAnalyze M&A deal workbench records and draft APA, SPA, merger, carveout, or committee terms against buyer, seller, or committee playbooks/policies, then return schema-conforming JSON issue registers, closing packages, transition reviews, escalation memos, or deviation matrices. Use when a task mentions TASK_ENV_BASE_URL, deal workbench APIs, deal IDs, playbook or policy thresholds, indemnity, escrow, survival, consents, HSR, employees, material contracts, or M&A legal JSON outputs.
- ▌ Ma Workbench JSON · prism-shadow bundleUse this skill for M&A deal workbench tasks that require a strict JSON answer from a running TASK_ENV_BASE_URL, answer_template.json, deal IDs, draft terms, playbooks, policy thresholds, consents, employees, material contracts, benchmarks, risk estimates, diligence findings, documents, or notes. Use it for counsel-style issue registers, closing/economics packages, committee escalation packages, carveout transition reviews, and SPA deviation matrices, even when the user only says to review a project or produce a deal package.
- ▌ Ma Deal Workbench 4 · prism-shadow bundleUse this skill for M&A deal workbench tasks that ask counsel to prepare structured JSON issue registers, closing or economics packages, committee escalation memos, transition reviews, SPA or APA deviation matrices, or playbook/policy comparisons from deal APIs. Trigger whenever the prompt mentions a deal ID, buyer-side or seller-side counsel, APA, SPA, M&A Committee, consents, HSR, cap tables, material contracts, risk estimates, benchmarks, or an answer_template JSON.
- ▌ Asteria Portfolio JSON · prism-shadow bundleUse this skill for Asteria Investment Office tasks that require strict JSON portfolio, credit, correlation, allocation, rebalance, or committee decisions from the shared Asteria environment. Trigger when prompts mention Asteria, PF-* portfolio ids, answer_template.json, current environment records, energy-credit trades, fixed-income rotations, HY/watchlist constraints, non-US equity correlations, index levels, macro signals, active allocation views, or committee decision files.
- ▌ Asteria Portfolio Decision JSON · prism-shadowBuild Asteria Investment Office portfolio decision JSON from the shared task environment. Use when the user asks for energy-credit trade packages, regional correlation reviews, allocation-view refreshes, fixed-income rebalances, or committee packets for PF-* portfolios, especially when the prompt mentions stale worksheets, live portfolio records, policies, prior views, macro signals, bonds, issuers, or index levels.
- ▌ Credit Office API JSON · prism-shadow bundleSolve public credit-office API tasks that require a JSON-only committee packet for branch regrades, lending allocations, credit-union segment posture, watch-list stress packets, or competing CRE decisions. Use this skill whenever the prompt mentions <TASK_ENV_BASE_URL>, answer_template.json, branch metrics, loans, applications, sector exposures, credit-union segments, or FDIC/NCUA benchmark comparisons.
- ▌ Credit Office Committee JSON · prism-shadow bundleUse this skill whenever a task asks for committee-ready JSON from the shared credit office API, especially prompts mentioning <TASK_ENV_BASE_URL>, branch_id, segment_id, lending committee, credit risk, risk-rating migration, pending application allocation, CRE comparisons, watch-list stress, CDFI scoring, FDIC/NCUA benchmarks, sector exposures, or an answer_template.json.
- ▌ Credit Office JSON · prism-shadow bundleUse this skill for credit office committee tasks that require JSON answers from the shared public API, including branch loan regrades, watch-list stress packets, pending application allocation, competing CRE decisions, FDIC or NCUA benchmark variance, concentration flags, CDFI factor scores, and schema/enums in answer_template.json. Trigger whenever the prompt mentions TASK_ENV_BASE_URL, branch_id, segment_id, credit policy, lending committee, or committee-ready JSON from a credit-office API.
- ▌ Peopleops Console Reconciliation 3 · prism-shadowSolve PeopleOps Console reconciliation tasks that require verifying leave, payroll, recruitment, policy-case, folder, notice, or audit records and returning a normalized JSON answer from the provided template. Use this skill whenever the prompt mentions PeopleOps Console, employee leave precedence, payroll assignment readiness, recruitment outcome packets, case folder readiness, formal notice defects, audit evidence, or any task that asks you to choose authoritative submitted or approved records and exclude drafts or stale summaries.
- ▌ Peopleops Console · prism-shadowInspect PeopleOps Console casework and return exact JSON for onboarding closeout, leave-source precedence, recruitment reconciliation, payroll readiness, and document or notice reviews. Use when prompts mention the PeopleOps Console, employee leave or payroll records, recruitment openings, case folders, notices, audits, or ask for normalized business labels from a provided answer template.
- ▌ Peopleops Reconciliation · prism-shadow bundleReconcile PeopleOps Console tasks and produce exact JSON answers from provided answer templates for onboarding, leave, payroll, recruitment, approval, notice, and audit/source-precedence cases. Use when a prompt points to a task runner URL or task environment and asks for authoritative records, exclusion lists, normalized enum labels, or final control results.
- ▌ Cedar Ridge Intake Audit 7 · prism-shadowUse this skill for Cedar Ridge Intake Coordination Portal tasks that require a JSON audit or activation file from a TASK_ENV_BASE_URL, including new-patient access verification, referral readiness, referral-to-chart activation, dialysis transfer packet review, and chronic-care program enrollment panels. Use it whenever a prompt mentions Cedar Ridge intake rosters, referrals, transfers, program candidates, chart artifacts, ICD metadata, or answer_template.json-controlled output.
- ▌ Cedar Ridge Intake 4 · prism-shadow bundleSolve Cedar Ridge Intake Coordination Portal tasks that require reconciling portal patient, referral, dialysis transfer, program candidate, chart, coverage, PBM, pharmacy, document, capacity, or ICD data into strict answer_template.json outputs. Use for prompts mentioning Cedar Ridge, TASK_ENV_BASE_URL, access verification, referral readiness, pulmonary or orthopedic intake batches, dialysis transfer reviews, chronic-care enrollment panels, or JSON-only intake activation files.
- ▌ Cedar Ridge Intake Reconciler · prism-shadowReconcile Cedar Ridge Intake Coordination Portal tasks into exact JSON answer-template outputs. Use for patient access verification, referral readiness or chart activation, dialysis transfer packet review, chronic-care program enrollment panels, and similar Cedar Ridge portal tasks that require joining API or SQL data, applying controlled reason codes, ordering rows, and computing cohort summaries.
- ▌ Northstar Payer Ops JSON · prism-shadow bundleUse this skill for Northstar Health Plan payer-operations tasks that require a strict JSON answer from the shared task environment, including prior authorization determinations, pharmacy appeals, manufacturer assistance intake, peer-to-peer summaries, payment integrity claim repricing, and UM-finance margin queues. Use it whenever a task mentions Northstar, payer operations, authorization cases, appeals, claims, service margins, policies, criteria, or answer_template JSON.
- ▌ Northstar Payer Ops JSON 2 · prism-shadow bundleProduce strict JSON determinations and operations packets for Northstar Health Plan payer-operations tasks using the shared task environment. Use when the prompt asks for prior authorization or UM review, pharmacy appeal or assistance intake, peer-to-peer closure, payment integrity claim repricing, benchmark selection, or service margin queue summaries that must conform to an input/payloads/answer_template.json schema.
- ▌ Northstar Payer Ops 12 · prism-shadow bundleResolve Northstar Health Plan payer-operations tasks against the shared task environment and return exact JSON outputs. Use for prior authorization, pharmacy appeal, peer-to-peer, claim repricing, payment-integrity, rate-schedule, and therapy margin queue prompts that provide an answer_template.json and Northstar environment access.
- ▌ Ehr Quality Packet Solver · prism-shadow bundleUse this skill for EHR quality-governance tasks that ask for normalized JSON packets from a read-only task API, including duplicate-chart merge readiness, referral coordination or audit packets, care-transition summaries, ServiceRequest quality review, ICD/service-code validation, active-list reconciliation, document evidence selection, provider contact lookup, and packet readiness classification. Use it whenever the prompt mentions an EHR/referral/quality environment, TASK_ENV_BASE_URL, answer_template.json, patient/referral/duplicate/service-request IDs, or returning normalized JSON from healthcare API records.
- ▌ Ehr Quality JSON · prism-shadow bundleUse this skill for EHR quality-governance tasks that require normalized JSON from a read-only healthcare API, including duplicate-chart merge packets, referral coordination, referral batch audits, care-transition packets, ServiceRequest validation, active clinical-list reconciliation, ICD-10 checks, provider lookups, and answers constrained by input/payloads/answer_template.json. Use whenever the prompt mentions an EHR/referral environment, <TASK_ENV_BASE_URL>, duplicate candidates, patient active lists, referral batches, ServiceRequests, or normalized packet JSON.
- ▌ Task Group 005 Finance Controls · prism-shadow bundleUse this skill for task_group_005 shared ERP, AP, compliance, vendor onboarding, prepaid close, reimbursement close, stale AP export, account-change release, or finance-risk JSON tasks that require calling a runner-provided task API and returning an answer_template-shaped JSON object. It guides API discovery, current-record reconciliation, close-control decisions, and strict schema output.
- ▌ Erp Finance Control Review 2 · prism-shadow bundleUse this skill for finance close, AP reimbursement release, vendor onboarding, account-change payment release, prepaid reconciliation, or other task_group ERP/compliance reviews that require querying a runner-provided JSON API and returning a strict JSON answer. Trigger when the user mentions claims, AP bills, payments, stale AP exports, close logs, vendors, compliance objects, UBOs, licenses, bank mismatches, prepaid schedules, GL balances, or an answer_template.json schema.
- ▌ Task Group 005 Finance Reconciliation · prism-shadowUse this skill for task_group_005 finance, ERP, AP, reimbursement, prepaid close, vendor onboarding, compliance, or account-change release tasks that require using the shared JSON API plus local payload templates to return a decision JSON. Trigger whenever the prompt mentions the runner-provided API base URL, current ERP/compliance evidence, AP bills/payments, claims, vendors, UBOs, bank/tax/license screening, GL balances, or prepaid schedules.
- ▌ Procureops Packets · prism-shadow bundleSolve ProcureOps packet tasks that ask for a readiness packet, closeout reconciliation, change-control decision, AP release file, AP close, or similar structured JSON output built from the shared ProcureOps API and task-local payloads. Use this whenever a prompt mentions ProcureOps, TASK_ENV_BASE_URL, input/payloads/answer_template.json, or one of those packet types.
- ▌ Procureops Casework · prism-shadowResolve ProcureOps procurement casework into strict JSON from a task memo and the live ProcureOps API. Use this whenever the user asks for a sourcing nomination packet, receiving or AP closeout, contract or budget change-control file, invoice release decision, or any similar procurement reconciliation grounded in live ProcureOps records, even if they only mention AP holds, receipts, purchase orders, vendor risk, or budget snapshots.
- ▌ Procureops JSON Reconciler · prism-shadowSolve ProcureOps packet tasks that combine a local memo/packet with the shared ProcureOps API and require exact JSON output for nomination readiness, receiving closeout, AP close, change-control, or release/hold decisions. Use this whenever a prompt asks for a structured JSON answer from ProcureOps records, especially when the packet names target IDs, a date slice, or an answer template.
- ▌ Northwind Erp Decisions · prism-shadowSolve Northwind Components ERP decision tasks that combine local memos/templates with live API lookups and require exact JSON output. Use this whenever the prompt mentions the Northwind ERP API, orders, inventory, warehouses, customers, products, BOMs, purchase orders, incidents, suppliers, shipping quotes, expedite queues, replenishment plans, mixed-warehouse transfer decisions, supplier scorecards, or procurement quality holds, even if it does not explicitly say "Northwind" or "JSON".
- ▌ Northwind Erp Decision JSON · prism-shadow bundleUse this skill whenever a task asks for a Northwind Components or shared ERP API dispatch, allocation, replenishment, procurement-control, supplier incident scorecard, BOM, inventory, purchase order, shipping quote, or answer_template JSON. It helps Codex read local task payloads, query the public ERP API, compute decisions and summaries, and return strict JSON matching the provided template.