prism-shadow
- 1.7k skills
- 0 followers
- 3.2k repo stars
- 5 days ago last updated
- ▌ M A Deal Workbench · prism-shadow bundleM&A deal analysis using the deal-workbench REST API at a configured base URL. Use when the task involves deal records (PRJ_ identifiers), draft terms, playbook rules, policy thresholds, risk estimates, benchmarks, cap tables, consents, employees, material contracts, regulatory records, diligence findings, or deal notes. Covers seller-side playbook issue registers, buyer-side SPA economics and closing packages, M&A committee escalation memos, carveout APA transition reviews, and SPA deviation matrices. Trigger on any request mentioning M&A, deal workbench, purchase agreement, APA, SPA, issue register, closing conditions, playbook review, escalation memo, deviation matrix, or deal analysis against the deal-workbench API.
- ▌ Asteria Data Quality Hub 3 · prism-shadow bundleReconcile, audit, and certify data-quality records from the Asteria Fleet Data Quality Hub REST API (contacts, fuel, freight, maintenance, and roster collections). Use when the task mentions the Asteria Fleet Data Quality Hub, a task-environment base URL with endpoints such as /api/catalog/collections, /api/catalog/schema, /api/contacts, /api/transactions/fuel, /api/transactions/freight, /api/maintenance/events, /api/reference/aliases, /api/reference/conversions, /api/reference/fx, /api/source-snapshots, or /api/query, or any Asteria Fleet certification, audit, reconciliation, or readiness workflow.
- ▌ Asteria Dq Hub 4 · prism-shadow bundleAudit, reconcile, and certify domain data collections against the Asteria Fleet Data Quality Hub REST API. Use when a task references the Asteria Fleet Data Quality Hub at the TASK_ENV_BASE_URL placeholder, involves reconciling overlapping source snapshots, detecting data-quality issues (mismatches, unrecognized entries, ambiguities, invalid measures), or assigning opaque internal control codes (IC-*, OR-*, FP-*, RB-*, SB-*, LD-*, MS-*, HR-*). Use when a task requires producing a structured certification or reconciliation JSON answer conforming to a supplied answer_template.json.
- ▌ Asteria Fleet Data Quality Hub 5 · prism-shadow bundleData quality audit, reconciliation, and certification for the Asteria Fleet Data Quality Hub. Use when the task involves auditing, reconciling, normalizing, or certifying fleet operational data (contacts, fuel transactions, freight charges, or maintenance events) against a read-only Hub API, or when the task requires assigning Asteria opaque control codes (IC, OR, FP, RB, SB, LD, MS, HR) based on data evidence. Trigger on phrases like 'Fleet Data Quality Hub', 'Asteria fleet', 'partner onboarding certification', 'fuel ledger audit', 'freight accrual reconciliation', 'maintenance log integrity', 'field service roster readiness', 'contact-readiness brief', or any task referencing environment_access.md with Asteria API endpoints.
- ▌ Atlas Ops Analyst 2 · prism-shadow bundleOperational analytics against the Atlas Commerce Operations REST API. Query read-only business data, apply controlled canonical corrections, and verify audit trails. Use when the task environment provides an Atlas API base URL with /api/schema, /api/data-dictionary, /api/sql, /api/sql/transaction, or /api/correction-audit endpoints and the prompt involves querying or correcting a shared commerce database spanning orders, shipments, refunds, payments, carrier scans, support cases, warehouse work, inventory, campaigns, accounts, products, FX rates, or facilities.
- ▌ Atlas Ops Analytics 4 · prism-shadow bundleAtlas Commerce Operations analytics platform access for business scorecards, operational reconciliations, quality reviews, productivity reports, and support health reviews. Use when working with the Atlas Commerce Operations API to query business records through schema discovery and SQL analysis, compute operational metrics from business request definitions, apply business classification rules to produce structured answer templates, or execute controlled data corrections with audit records. Trigger when a task references an Atlas Commerce Operations workplace, the /api/schema or /api/sql endpoint, answer_template.json, a cutoff-based operational scorecard, or payloads containing business definitions and classification rules.
- ▌ Atlas Ops Scoring · prism-shadow bundleAnalytical scoring and data correction for the Atlas Commerce Operations database through an authenticated REST API. Use when a task asks to compute production-shipping scorecards, refund-settlement reconciliations, carrier quality corrections, warehouse productivity reviews, or enterprise support health reports against Atlas records. Covers both read-only SQL analytics (cutoff-based eligibility, tiered classification, ranking, breach detection, leakage candidate identification) and single-field transactional corrections with audit verification. Trigger when the workspace mentions Atlas Commerce Operations, an atlas-ops API, cutoff-based business metrics, or any of the five named review types.
- ▌ Pho Audit Solver 4 · prism-shadow bundleSolve Public Health Observatory (PHO) registered algorithmic audit tasks. Use when a task references a PHO portal, PHO protocol IDs (PHO_STATE_TRANSPORT_AUDIT_V1, PHO_COUNTY_MEDIATION_TRANSPORT_V1, PHO_STATE_ROBUSTNESS_TRANSPORT_V1, PHO_COUNTY_PANEL_TRANSPORT_V1), registered six-module or multi-module audits, algorithmic transportability or robustness analyses, burden-stratification briefings, or PHO publication-board decisions. Handles state, county, and country data across health, socioeconomic, and revision endpoints.
- ▌ Pho Audit 5 · prism-shadow bundleComplete reproducible algorithmic audits for the Public Health Observatory (PHO). Use this skill when the user presents a PHO analysis request with a protocol_id, an answer_template.json, and a task-environment base URL for retrieving public health data. Covers state-level, county-level, and country-level audits across longevity, mediation, burden stratification, and weighted-robustness protocols. Handles release resolution, cohort construction, cross-validated regularized regression, jackknife and wild bootstrap inference, grouped conformal calibration, PCA trajectory clustering, sensitivity surfaces, source perturbation, and controlled decision gates.
- ▌ Pho Audit Portal · prism-shadow bundlePublic Health Observatory algorithmic audit protocol execution. Use when an analysis_request.json or prompt references a PHO registered audit protocol, when the task involves executing multi-module transportability audits for state/county/country health data via the PHO web portal, or when the solver must implement deterministic statistical methods (fixed-effects jackknife, nested ridge/elastic-net CV, wild cluster bootstrap, grouped split conformal, trajectory PCA clustering, source/year perturbation, difference GMM mediation, sensitivity analysis) from raw portal CSV data. Covers all PHO protocol families: PHO_STATE_TRANSPORT_AUDIT_V1, PHO_COUNTY_MEDIATION_TRANSPORT_V1, PHO_COUNTY_PANEL_TRANSPORT_V1, and country burden stratification audits.
- ▌ Eng Portfolio Review 3 · prism-shadow bundleEngineering portfolio intelligence for mixed work-tracking environments. Use when preparing portfolio mix reviews, SLA aging audits, release readiness assessments, or any analysis of work items across teams and product areas. Handles: (1) portfolio category classification of work items into NewFeature, TechDebt, Reliability, and Security, (2) target-vs-actual mix gap analysis, (3) SLA overdue and aging bucket calculations with severity-based policies, (4) release readiness scoring from milestone completion, blocker, and dependency data, (5) detection and exclusion of duplicates, cancelled items, stale mirror fields, and legacy category signals. Trigger on phrases like 'portfolio mix review', 'SLA aging audit', 'release readiness assessment', 'closed work portfolio', 'engineering portfolio', 'mix target analysis', or when working with work item data from the shared task environment API.
- ▌ Portfolio Review 3 · prism-shadow bundlePortfolio review, SLA aging audit, and release readiness assessment for engineering work-item environments. Use when the task involves (1) closed-work portfolio-mix review with target-comparison and gap analysis, (2) SLA compliance audit with overdue detection, aging distribution, and breach-rate calculation, or (3) release readiness assessment with ship/no-ship decisions, milestone completion, blocker analysis, and dependency-chain traversal.
- ▌ Engineering Portfolio 2 · prism-shadow bundlePortfolio-mix review, SLA aging audit, and release-readiness assessment for an engineering work-item environment exposed through a REST API. Use when a task asks you to classify closed work items into portfolio categories (NewFeature, TechDebt, Reliability, Security), compare actual mix against target mix, audit SLA breaches and overdue aging, assess release readiness against milestones and blockers, or produce structured JSON answers from work-item, release, milestone, blocker, dependency, mix-target, and SLA-policy endpoints. Also use when the task references scope_id-based mix targets, as-of-date SLA windows, release gating, or duplicate/cancelled exclusion logic in an engineering-portfolio context.
- ▌ Clinic Decision Support 9 · prism-shadow bundleProtocol-bound clinical decision support for a synthetic FHIR-like clinic REST API. Use when a prompt references a clinic case ID, a structured answer template with controlled enums, and a task environment base URL for fetching patient data, observations, protocols, and related clinical resources. Covers respiratory assessment, pediatric head injury, potassium replacement, care-management routing, observation-window retrieval, and similar protocol-driven structured-answer tasks.
- ▌ Clinic Protocol · prism-shadow bundleStructured clinical protocol decision support for synthetic clinic FHIR-like REST APIs. Use when the task directs you to a clinic runtime with TASK_ENV_BASE_URL and a case ID to produce protocol-bound structured JSON answers for respiratory assessment (RESP-CAP-2026), pediatric head injury (PEDS-HEAD-2026), potassium replacement (K-REPLETION-2026), care management routing (CM-HIGH-RISK-2026), or observation-window retrieval (OBS-WINDOW-2026). Also use for any task that requires reading a clinic case endpoint, applying a protocol from /api/protocols, and returning an answer conforming to a JSON template with controlled enum values.
- ▌ Clinic Decision Support 10 · prism-shadow bundleProtocol-bound clinical decision support for synthetic clinic environments with a FHIR-like REST API. Use when the task involves a clinic case ID, structured answer templates, and a clinic runtime API at a base URL for respiratory assessment, head-injury protocols, potassium replacement, care-management routing, or lab-window retrieval. Triggers on prompts mentioning answer_template.json, protocol assessment, clinical decision support, order-entry support, care-management routing, or synthetic clinic case identifiers.
- ▌ Investigation Review Hub 12 · prism-shadow bundleStructured gap, risk, and remediation analysis for legal eDiscovery matters using an Investigation Review Hub REST API. Use when the task requires: (1) rolling production gap analysis, (2) retention and litigation-hold gap review, (3) production-readiness review, (4) cross-system remediation dashboards, (5) privilege-log completeness checks, (6) QC finding triage, or (7) any structured eDiscovery dashboard delivered as JSON against a provided answer template. Triggers include references to matters, subpoena categories, productions, custodian sources, privilege logs, QC findings, retention events, remediation actions, or an Investigation Review Hub base URL.
- ▌ Investigation Review Hub 13 · prism-shadow bundleCollect evidence from the Investigation Review Hub REST API, analyze structured answer templates, and produce strictly-typed JSON outputs for legal/regulatory review workflows. Use when the task provides an Investigation Review Hub base URL, a template JSON schema, and asks for a gap analysis, remediation dashboard, retention review, privilege review, or production-readiness deliverable. Trigger on prompts containing TASK_ENV_BASE_URL, Investigation Review Hub, answer_template.json, or structured investigation deliverables with enumerated JSON schemas.
- ▌ Investigation Review Hub 14 · prism-shadow bundleStructured gap analysis, remediation dashboards, production-readiness reviews, and retention-hold assessments using the Investigation Review Hub REST API for eDiscovery and legal hold matters. Use when the task provides a matter_id and asks for a structured JSON deliverable covering privilege log gaps, responsive coding defects, personal source gaps, retention events, QC findings, production stats, or cross-system remediation action plans. Trigger phrases include gap analysis, remediation dashboard, production readiness review, retention hold review, privilege log supplement, rolling production assessment, and any task directing the agent to the Investigation Review Hub via TASK_ENV_BASE_URL.
- ▌ Court Clerk Closeout 4 · prism-shadow bundleComplete court clerk closeout, disposition, and financial-reconciliation packet preparation for circuit and traffic courts. Reconciles hearing notes, worksheets, audit memos, petition summaries, and other local court materials against a Court Operations Portal providing cases, charges, citations, docket entries, fee schedules, payment policies, forms, financial petitions, and search endpoints. Produces structured JSON answer objects matching a supplied answer template with exact enum values, ISO dates, and two-decimal currency. Use when the task involves: (1) criminal sentencing or traffic-violation closeout packages, (2) post-disposition financial and supervision packet preparation, (3) fee reconciliation across conflicting court records, (4) payment-plan schedule computation, or (5) audit-driven register/ledger closeout with disposition-status decisions.
- ▌ Court Clerk Reconciliation 2 · prism-shadow bundleCourt clerk reconciliation of local case materials (hearing notes, audit memos, finance extracts, petition summaries) against a Court Operations Portal REST API. Produces structured JSON closeout packets matching supplied answer templates. Use when the task involves: (1) sentencing or disposition closeout for a batch of criminal or traffic cases, (2) post-sentencing field packets with probation referrals and installment orders, (3) post-disposition financial and supervision packets, (4) reconciling conflicting identity, counsel, fee-schedule, or departure records between local materials and a portal, (5) constructing payment-plan schedules from portal policy bands and petitioner budgets, (6) identifying unsupported fees to exclude from financial entries, or (7) filling structured JSON answer templates with enumerated field values.
- ▌ Court Clerk Reconciliation 3 · prism-shadow bundleCourt-clerk reconciliation and financial closeout workflow for criminal, traffic, and post-sentencing dockets. Use when a deputy clerk task requires: (1) cross-referencing local hearing notes, audit memos, finance worksheets, petition summaries, or form excerpts against a Court Operations Portal REST API, (2) resolving identity/counsel/fee/status/departure conflicts across conflicting sources, (3) computing per-case financial totals (fines, costs, assessments, user fees, surcharges), (4) structuring approved post-disposition payment plans with installment math, (5) preparing CC-1375 probation referrals, CC-1379 license-suspension/installment orders, or local payment-plan forms, (6) identifying unsupported or stale charges for exclusion, or (7) assembling docket-register entries with batch totals from a multi-case closeout batch.
- ▌ Licensing Review 21 · prism-shadow bundleStructured eligibility decisions for state licensing board tasks involving contractor applications, liquor license reviews, and alcohol renewal queues. Use when the task requires cross-referencing REST endpoint data against policy thresholds, identifying deficiency codes and required actions from live records, and producing JSON outputs that conform to a supplied answer template. Triggers on licensing examiner, contractor board, liquor license, alcohol renewal, batch eligibility, or staff review package phrasing.
- ▌ Licensing Review 22 · prism-shadow bundleStructured licensing review for state licensing board operations. Covers contractor application batch eligibility review (bond, insurance, endorsement, experience, violation, inspection, correspondence analysis), restricted liquor license staff packages (risk coverage, verification gaps, standard obligations, location-specific controls, 90-day monitoring plans, escalation triggers), and alcohol license renewal manual-review queues (violation matching, boundary-date filtering, risk-tier ranking, next-step routing). Use when the task involves contractor licensing decisions, liquor license transfer or issuance review, alcohol renewal screening, or any structured licensing board workflow that requires REST API data fetching from board endpoints and structured JSON output with determination codes, risk tiers, and summary statistics.
- ▌ Licensing Review 23 · prism-shadow bundleState licensing board batch review for contractor eligibility, restricted liquor license staff packages, and alcohol renewal manual-review queues. Use this skill when the task involves: (1) batch eligibility determinations (APPROVE/HOLD/DENY) for contractor or professional license applications, (2) preparing a restricted liquor license staff package with risk coverage, verification gaps, obligations, 90-day monitoring plan, and escalation triggers, (3) building a ranked manual-review queue for alcohol license renewals based on violation recency and severity, or (4) any prompt that mentions licensing examiners, contractor applications, liquor license transfers, or renewal screening.
- ▌ Ma Deal Workbench 9 · prism-shadow bundleWork with the M&A deal workbench API to produce structured deal-analysis deliverables for M&A transactions. Use when the task requires gathering deal records, draft terms, playbook rules, policy thresholds, and supporting data (consents, employees, regulatory, risk estimates, benchmarks, material contracts, diligence findings) from the workbench and producing a structured JSON deliverable that compares draft positions against playbook or policy requirements. Triggers on tasks involving SPA/APA issue registers, closing packages, committee escalation memos, transition reviews, deviation matrices, or any M&A deal-review output that references the workbench API.
- ▌ Ma Deal Workbench 10 · prism-shadow bundleM&A deal workbench REST API for transactional practice tasks. Use when the task references a configurable base URL for deal endpoints, requires gathering structured M&A data (deals, terms, playbooks, policies, employees, consents, material contracts, regulatory records, diligence findings, risk estimates, benchmarks, notes, cap tables, documents), comparing draft terms against playbook or policy thresholds, and producing structured JSON output conforming to a provided answer template. Covers seller-side APA reviews, buyer-side SPA closing packages, committee escalation memos, carveout transition reviews, and deviation matrices. Use when the prompt mentions an M&A deal workbench, deal IDs like PRJ_*, playbooks like PB_SELLER_A or PB_BUYER_A, or read-only SQL tokens.
- ▌ Credit Risk Committee 7 · prism-shadow bundleCredit risk committee lending workflow for a shared credit office REST API. Handles rating migration reviews, lending-committee allocations, credit-union segment postures, watch-list stress packets, and competing CRE decisions. Use when a prompt mentions a credit risk committee, lending committee, branch rating review, branch allocation package, credit-union segment posture, watch-list stress or workout, competing CRE decision, or any task that references the shared credit office API at a base URL like TASK_ENV_BASE_URL. Also use when the prompt references branch review, FDIC/NCUA benchmarks, CDFI scoring, DSCR stress, policy re-rating, sector concentration, or committee-ready JSON answers for branch_id, segment_id, or application_id comparisons.
- ▌ Credit Risk Committee 8 · prism-shadow bundleCredit risk committee analysis for bank and credit union lending operations using a shared public credit office API. Supports rating migration reviews, lending-committee allocation packages, credit-union segment posture pages, watch-list stress packets with CDFI risk classes, and competing CRE decisions. Use when the user asks to prepare committee-ready credit analysis, review a branch loan portfolio with risk-rating re-derivation, allocate lending capacity across pending applications, assess a credit-union segment against NCUA benchmarks, stress-test an adverse watch list, or compare competing CRE applications. Triggers on phrases like rating migration review, lending committee, allocation package, segment posture, watch-list stress, competing CRE, FDIC benchmark, NCUA benchmark, CDFI risk class, risk rating review, credit risk committee, or when a task references a branch_id with a shared credit office API.
- ▌ Peopleops Console 10 · prism-shadow bundleNavigate the PeopleOps Console REST API to complete HR operations workflows: onboarding closeout verification, leave-source precedence checks, payroll assignment and accrual readiness, policy-case folder and formal-notice review, and recruitment outcome reconciliation. Use when the task involves: (1) an employee lifecycle or onboarding closeout check, (2) leave policy or payroll assignment verification, (3) reviewing remote-work or policy-case folder readiness and formal notice quality, (4) reconciling a recruitment pipeline with candidate outcomes and costs, (5) cross-module audit inspection for PeopleOps, or when the prompt references the PeopleOps Console, employee IDs like EMP-\d+, case IDs like CASE-\w+, or recruitment openings like REQ-\w+.
- ▌ Peopleops Console 11 · prism-shadow bundlePeopleOps HR console solver for employee onboarding closeout, case folder/notice review, recruitment reconciliation, leave source precedence, and payroll assignment readiness. Use when the task references PeopleOps Console, TASK_ENV_BASE_URL, ops.lead@peopleops.local, onboarding, leave policy, payroll assignment, case review, recruitment reconciliation, notice quality, or audit scoping.
- ▌ Peopleops Console 12 · prism-shadow bundleSolver for Northwind People Lifecycle Portal (PeopleOps Console) tasks. Handles verification and reconciliation across employees, leave, payroll, recruitment, policy cases, documents, messages, and audit logs. Use when working with PeopleOps business tasks that involve determining leave source precedence, payroll assignment readiness, recruitment reconciliation, remote-work case review, onboarding closeout, or cross-module lifecycle control.
- ▌ Cedar Ridge Intake 18 · prism-shadow bundleCedar Ridge Intake Coordination Portal workflows covering patient access verification, referral auditing, dialysis transfer review, chronic-care enrollment panels, and referral-to-chart activation. Use when the task references the Cedar Ridge Intake Coordination Portal, a TASK_ENV_BASE_URL, or any Cedar Ridge intake batch/roster (e.g. NPI-, ORTHO-, DIAL-, PULM-, DMHTN-). Trigger on phrases like intake coordination, Cedar Ridge, patient access verification, referral readiness, transfer review, enrollment panel, chart activation, or when a JSON answer template requires controlled healthcare-intake vocabularies.
- ▌ Cedar Ridge Intake 19 · prism-shadow bundleHealthcare intake coordination workflow for processing patient rosters, referral batches, transfer reviews, and chronic-care enrollment panels against the Cedar Ridge Intake Coordination Portal API. Use when the task involves: (1) verifying patient access or insurance, (2) auditing referral readiness or chart activation, (3) reviewing dialysis or other transfer packets, (4) preparing chronic-care enrollment panels, (5) any batch workflow that follows a JSON answer template with controlled vocabularies, or (6) tasks referencing the Cedar Ridge Intake Coordination Portal or a task environment base URL with patients/referrals/transfers/chart endpoints.
- ▌ Cedar Ridge Intake 20 · prism-shadow bundleNavigates the Cedar Ridge Intake Coordination Portal, a read-only REST API with optional SQL query endpoint used for healthcare intake tasks. Use when a task references Cedar Ridge, the intake coordination portal, or asks to work with patient rosters, referral batches, transfer packets, program enrollment panels, chart activation, or patient access verification against a read-only healthcare API. Covers five intake workflows: patient access verification, referral readiness auditing, dialysis transfer review, chronic-care program enrollment, and referral-to-chart activation.
- ▌ Northstar Payer Ops 24 · prism-shadow bundleNorthstar Health Plan payer operations structured determination workflows. Use when working as a Northstar payer operations role (UM nurse reviewer, pharmacy appeals coordinator, payment integrity analyst, peer-to-peer coordinator, or UM-finance analyst) to produce structured JSON determinations against the Northstar task environment. Supports five business domains: (1) prior authorization UM nurse determination, (2) pharmacy coverage appeal and assistance intake, (3) claim repricing and payment integrity correction, (4) peer-to-peer discussion finalization, (5) therapy margin queue analysis. Uses REST business endpoints and a bearer-token SQL endpoint. Triggers on Northstar case IDs, appeal IDs, claim IDs, or payer ops role names with a bearer-token SQL environment.
- ▌ Northstar Payer Ops 25 · prism-shadow bundleNorthstar Health Plan payer operations environment for utilization management, pharmacy appeals, payment integrity, peer-to-peer review, and therapy margin analysis. Use when the task involves Northstar prior authorization case review, coverage appeal and manufacturer assistance intake, cardiac imaging claim repricing, P2P authorization summaries, or UM-finance therapy margin queue analysis — any structured determination against the payer operations API and SQL backend.
- ▌ Northstar Payer Ops 26 · prism-shadow bundleNorthstar Health Plan payer operations environment for utilization management, appeals, payment integrity, peer-to-peer review, and margin analysis. Use this skill when working with the Northstar shared payer-operations API at the task-provided base URL. Covers: (1) UM nurse prior-authorization determinations with criteria review, document classification, and authorization issuance, (2) pharmacy coverage-exception appeals with drug-trial evaluation, packet-gap analysis, and manufacturer-assistance screening, (3) payment integrity claim repricing against current benchmarks with line-level correction, (4) peer-to-peer coordinator summaries after completed P2P discussions including adverse-determination deadlines, and (5) UM-finance therapy margin queue analysis with threshold and charge-sensitivity flagging. Every task produces a structured JSON answer with a basis_audit trail.
- ▌ Ehr Governance 2 · prism-shadow bundleFHIR EHR quality-governance workflows: duplicate-chart merge readiness, referral coordination packets, care-transition handoff summaries, ServiceRequest quality review, and referral batch audits. Navigates a read-only FHIR API (patients, conditions, medications, allergies, encounters, immunizations, documents, disclosures, service requests, audit logs, duplicate candidates, referrals, ICD-10 codes, providers, service codes) and produces normalized JSON packets. Use when the task involves EHR data quality, merge packets, referral audits, care transitions, FHIR resource reconciliation, or clinical governance reporting against a structured quality-governance FHIR environment.
- ▌ Ehr Quality Governance 13 · prism-shadow bundleNavigate a FHIR-style EHR quality-governance REST API to produce normalized clinical packets. Use when a task involves preparing merge-readiness packets, referral coordination documents, care-transition summaries, service-request quality reviews, or batch referral audits against a healthcare API. Covers duplicate-chart review, active clinical-list reconciliation, ICD-10 validation, identity-signal analysis, encounter selection for handoffs, allergy-readiness checks, authorization tracking, provider-directory lookup, document/audit evidence gathering, and risk-flag derivation. Recognize triggers like EHR quality governance, duplicate merge packet, referral coordination, care transition packet, orthopedic referral audit, or any prompt referencing a TASK_ENV_BASE_URL healthcare API with patient/condition/medication/allergy/encounter/document/ICD-10/provider endpoints.
- ▌ Ehr Governance Solver · prism-shadow bundleSolve EHR quality-governance tasks against a FHIR-like REST API. Use when the prompt references an EHR/clinical governance API, patient duplicate merge readiness, referral coordination packets, care transition packets, duplicate-review with ServiceRequest validation, referral batch audits, answer templates with normalized_key arrays, ICD-10 code validation, or active clinical list reconciliation. Covers API endpoint usage patterns, normalized JSON output rules, and evidence-based reconciliation workflows.
- ▌ Northwind Erp 7 · prism-shadow bundleInteract with the Northwind Components shared ERP REST API to solve operations desk tasks including dispatch/expedite decisions, replenishment/kit-build planning, supplier incident scorecards, cross-warehouse allocation, and procurement quality-risk controls. Use when working with Northwind operations, ERP queries, order fulfillment, inventory analysis, BOM/kit replenishment, supplier quality review, purchase-order decisions, or shipping quotes. Triggers on Northwind Components, expedite queue, kit build, replenishment, supplier scorecard, allocation desk, procurement control, or any task referencing a shared ERP API at a task environment base URL.
- ▌ Northwind Erp 8 · prism-shadow bundleNorthwind Components ERP operations and fulfillment decision support. Use when working with the Northwind ERP API at a task-environment base URL to resolve supply-chain desk decisions: expedite-queue order triage, line-level allocation and transfer planning, BOM replenishment, supplier incident scorecards, and procurement quality hold reviews. Triggers on Northwind, Northwind Components, ERP, fulfillment, expedite, allocation, replenishment, BOM, supplier incident, scorecard, procurement quality, inventory status, customer exception, shipping quote, or answer-template JSON tasks.
- ▌ Northwind Erp 9 · prism-shadow bundleNorthwind Components ERP operations for supply-chain decision tasks. Use when the task involves dispatch control (expedite queues), multi-warehouse allocation, kit-build replenishment planning, supplier quality incident scorecards, or procurement quality-control reviews against the Northwind ERP REST API. The skill covers inventory classification, customer exception mapping, decision matrices, shipping quotes, BOM-based component planning, supplier recommendation policies, and purchase-order hold/release logic. Trigger when the user references Northwind Components, Northwind ERP, order waves, expedite queues, allocation desks, replenishment desks, supplier scorecards, procurement control, or any operational decision file using ERP live records.
- ▌ Private Wealth Advisory 9 · prism-shadow bundlePrivate wealth advisory planning output for high-net-worth clients. Produces structured JSON planning summaries covering: (1) Roth conversion and RMD tax projections, (2) ILIT Crummey funding-cycle implementation, (3) GRAT versus CRAT trust comparisons, (4) estate liquidity action plans combining ILIT and trust strategies. Use when a task requests advisory planning output for a client with a private-wealth advisory API, when a request memo specifies an engagement type like Roth conversion, ILIT Crummey, GRAT/CRAT comparison, or estate liquidity, or when the task expects a JSON output conforming to an advisory answer template. Trigger on terms like advisory, wealth management, Roth conversion, RMD, ILIT, Crummey, GRAT, CRAT, estate planning, liquidity action plan, trust comparison, or private wealth.
- ▌ Wealth Advisory 2 · prism-shadow bundlePrivate wealth advisory planning engine that produces structured JSON analyses from an advisory API environment. Use when the user asks to prepare a planning output for a client using a supplied API base URL, or when the task involves Roth conversion RMD analysis, ILIT Crummey funding, GRAT-versus-CRAT trust comparison, or estate liquidity action plans. Triggers on phrases like "Prepare the requested structured planning output for client", "advisory API", "Roth conversion", "ILIT", "GRAT", "CRAT", "Crummey", "estate liquidity", "retirement accounts", "trust comparison", or when answer templates with enums like STAGED_ROTH_CONVERSION or FUND_WITH_CRUMMEY_NOTICES appear in context.
- ▌ Wealth Advisory Planner 4 · prism-shadow bundleStructured wealth advisory planning for private wealth teams. Produces JSON outputs for Roth conversion and RMD analysis, ILIT Crummey funding implementation, GRAT vs CRAT trust comparisons, and combined estate liquidity action plans. Use when the task involves a client from the advisory environment, an answer_template.json with wealth advisory fields, API calls to the advisory API surface (clients, source documents, retirement accounts, life insurance, trust candidates, tax policies, RMD factors), or request memos referencing Roth conversions, ILIT, Crummey notices, GRAT, CRAT, estate liquidity, or source document conflict resolution.
- ▌ Crescent Finance Ops 19 · prism-shadow bundleCrescent Arts Collective Finance Ops API reporting for branch financials, ensemble compensation, and production payroll. Use when a task involves the Crescent Finance Ops API (base URL in environment_access.json or environment_access.md), references endpoints under /api/finance/, /api/compensation/, or /api/payroll/, and asks for a structured JSON result from a request memo and answer template. Triggers on phrases like branch close, regional view, compensation summary, board forecast, payroll review, or request_memo.json with answer_template.json.
- ▌ Crescent Finance Ops 20 · prism-shadow bundleComputational financial operations for Crescent Arts Collective — branch management reporting, compensation summaries and forecasts, and weekly production payroll. Use when a task requires reading from the Crescent Finance Ops API (branches, records, period-map, accounts, compensation rate-book/rosters/scenarios, or payroll rate-book/productions), computing derived metrics (EBITDA, ratios, variances, growth rates, compensation pay-type totals, payroll service categories), and producing a structured JSON answer. Triggers on requests involving: branch close packages, regional reporting, ensemble compensation, board forecasts, or theatre payroll review.
- ▌ Crescent Finance Ops 21 · prism-shadow bundlePrepare management reports for Crescent Arts Collective by querying the Crescent Finance Ops API. Use this skill when working with Crescent payroll, compensation, or finance branch/region reporting tasks. The skill covers: (1) Monthly branch close packages with income statements, variance analysis, fiscal-year comparisons, regional context, and branch rankings, (2) Ensemble compensation summaries by quarter and pay type with roster treatment counts, (3) Compensation forecasts with multi-year growth scenarios, (4) Weekly payroll review for theatre productions with service counts, category totals, per-musician breakdowns, contract conflict detection, and (5) Regional management views with cross-year comparisons and branch-level EBITDA rankings. All tasks follow a common pipeline: fetch from the Finance Ops API, apply domain-specific computation rules, and format a JSON answer per the provided answer template.
- ▌ Asteria Portfolio Risk 2 · prism-shadow bundleInstitutional portfolio risk analysis for the Asteria Investment Office. Covers energy-credit trade strategy, international equity correlation review, active allocation view refresh, fixed-income risk rebalance, and multi-asset committee decision linkage. Use when the task references Asteria portfolios, the Asteria Investment Office, or any portfolio ID starting with PF-EN-, PF-INT-, PF-FI-, or PF-MA-. Also use when the task provides an answer_template.json and a local request payload and expects JSON output computed from a shared Asteria API environment at http://task-env:9010/.
- ▌ Asteria Portfolio Risk 3 · prism-shadow bundleInstitutional portfolio risk, credit strategy, equity correlation, and asset-allocation workflows for the Asteria Investment Office shared API environment. Use when the task involves Asteria portfolios, credit desk decisions, equity correlation reviews, fixed-income rebalance rotations, CIO allocation views, or investment-committee decision files. The environment exposes current portfolio holdings, bond and issuer records, monthly index levels, allocation opportunity sets, prior views, macro signals, and policy thresholds. Trigger on prompts that reference Asteria, PF-..., BND_... or IDX_... identifiers, credit/correlation/allocation/committee/rebalance workflows, or any structured JSON output template matching Asteria schema conventions.
- ▌ Asteria Investment Office 8 · prism-shadow bundleInstitutional portfolio risk and allocation workflows for the Asteria Investment Office shared environment. Use for fixed-income credit trades, international equity correlation reviews, active allocation view refreshes, credit risk rebalances, and multi-asset committee decisions. The environment exposes REST endpoints for portfolios, bonds, issuers, indices, index levels, policies, allocation taxonomy, prior views, macro signals, and energy markets. Task prompts reference client desks (energy credit, CIO, risk, investment committee) and provide structured answer templates. Do not use for general portfolio analytics or other investment data providers.
- ▌ Credit Office 3 · prism-shadow bundleCredit committee analysis for a shared credit office REST API. Covers risk-rating regrades, lending-committee allocations, credit-union segment posture reviews, watch-list stress testing, and competing CRE decisions. Use when the task involves any branch-level or segment-level credit analysis against the credit office API — including portfolio rating migration, application scoring, concentration checks, FDIC benchmark comparisons, NCUA peer analysis, CDFI factor scoring, DSCR stress tests, or committee-ready JSON reporting.
- ▌ Medbridge Sales Ops 22 · prism-shadow bundleComplete workflow guide for the MedBridge Sales Ops shared REST API covering quote revisions with freight, indicative module quotes, and engagement reconciliations. Use when the task mentions MedBridge Sales Ops, a TASK_ENV_BASE_URL sales-operations API, or reference fields like quote_id, customer_id, product_code, freight-quotes, policies, opportunities, milestones, invoices, payments, revenue-journals, events, or vouchers. Handles three task types: (1) quote revision with freight comparison and risk assessment, (2) indicative EXW-only module quotations from RFQs, (3) opportunity milestone reconciliation with revenue recognition and event/voucher follow-up tasks.
- ▌
- ▌ Medbridge Sales Ops 24 · prism-shadow bundleComplete MedBridge Sales Ops API integration for humanitarian and medical supply quoting, pricing, freight comparison, account reconciliation, and engagement milestone tracking. Use when the task involves: (1) Building quote revision packages with EXW pricing, freight options, and policy-driven recommendations, (2) Processing indicative RFQ/quote requests with module-level line items and EXW-only scope, (3) Reconciling won opportunities against milestone invoices, payments, and revenue recognition journals, (4) Producing engagement reconciliations with accounting actions and event invitation tasks, (5) Any MedBridge Sales Ops data retrieval across customers, products, quotes, RFQs, freight-quotes, invoices, payments, revenue-journals, events, vouchers, or opportunities via the MedBridge REST API.
- ▌ Support Console Operator · prism-shadow bundleResolve telecom support tickets, contact-center cases, enterprise incidents, and mobile-data issues using a shared REST support-console API. Use when the task involves: (1) a batch of offline service tickets needing classification and routing, (2) a contact-center queue of mobile cases requiring self-service or billing actions, (3) an enterprise client export-complaint investigation with SLA and evidence handling, (4) a queue-quality review of tickets before SLA handoff, or (5) a mobile-data recovery worklist with refuel or carrier-update operations. Trigger on prompts mentioning support tickets, case queues, incident investigations, SLA reviews, or mobile-data recovery with a shared API endpoint.
- ▌ Support Console Ops 4 · prism-shadow bundleTelecom support console operations — resolve offline service tickets, contact-center mobile cases, enterprise export incidents, queue quality reviews, and mobile data recovery worklists by querying the support console REST API and applying domain-specific decision frameworks. Use when the task provides a batch JSON/CSV of tickets, cases, or work items against the support console and asks for structured resolution JSON.
- ▌
- ▌ Apexcloud Retention Ops 34 · prism-shadow bundle[object Object],file types,or tasks that trigger it.
- ▌ Apexcloud Retention Ops 35 · prism-shadow bundleComplete reference for the ApexCloud Retention Operations API. Use when building renewal risk queues, QBR metrics packets, receivables reviews, churn model validations, or high-touch retention action boards from the ApexCloud task environment. Covers all public endpoints, controlled enum vocabularies, business calculation rules (ARR sourcing, clean ticket counts, overdue balance formulas, NPS handling, renewal windows), cross-entity linking between A/R customers and CRM accounts, churn model training/scoring with logistic regression, and five reusable task archetypes. Trigger on tasks mentioning ApexCloud, retention operations, renewal risk, QBR, QBR metrics, receivables, pipeline operations review, churn model, churn validation, churn candidates, retention board, retention action board, BORD sort, or the /api/ and /exports/ endpoints listed in the catalog.
- ▌ Apexcloud Retention · prism-shadow bundleOperational analysis and reporting with the ApexCloud Retention Operations REST API. Use when a task requires: (1) renewal risk queue ranking accounts by churn risk with risk scores, actions, and reason codes, (2) QBR metrics packet with monthly revenue, support tickets, SLA, and NPS, (3) A/R receivables and pipeline operations review with overdue followups linked to CRM accounts, (4) churn model validation and outreach ranking by predicted churn probability, (5) high-touch retention operations board reconciling billing, support, NPS, receivables, usage, and expansion across accounts, or (6) any task querying multiple ApexCloud endpoints to produce structured JSON with controlled vocabularies and deterministic precision.
- ▌ Erp Finance Review 5 · prism-shadow bundleERP finance close and review operations using a shared REST API. Use when working with finance review tasks that involve cross-referencing claims, AP bills, payments, vendors, compliance records, prepaid schedules, GL balances, or close logs to produce structured release, close, or reconciliation decisions. Triggers include: (1) Reimbursement or AP claim close review, (2) Vendor onboarding or account-change release review, (3) Prepaid expense close reconciliation against GL balances, (4) Stale AP snapshot reconciliation against current system records, (5) Any task requiring multi-endpoint finance API cross-referencing to classify items into decision categories and produce JSON output matching a supplied answer template.
- ▌ Finance Close Review 2 · prism-shadow bundleFinance close and compliance review operations against a shared ERP API. Use when the task involves batch reconciliation of expense claims, AP bills, vendor onboarding, prepaid amortization, account-change payment release, or compliance screening. Trigger on prompts about AP close review, reimbursement batch settlement, vendor finance-risk review, prepaid schedule reconciliation against GL balances, stale AP snapshot reconciliation, payment release after account changes, or any finance operations task that references a shared task environment API with endpoints under /api/claims, /api/ap/, /api/compliance/, /api/prepaids/, /api/vendors, or /api/close/.
- ▌ Finance Close Review 3 · prism-shadow bundleFinance close and AP review operations against a shared ERP JSON API. Use when tasks involve reviewing expense claims against AP bills and payments, releasing vendor onboarding batches with compliance checks, reconciling prepaid invoice schedules against GL balances, reconciling stale AP snapshots against current ERP state, or reviewing account-change payment releases with compliance and risk screening. Triggered by prompts mentioning claim-AP close, reimbursement batch, vendor onboarding, prepaid close, stale AP reconciliation, or account-change payment review.
- ▌ Procureops 5 · prism-shadow bundleIndustrial procurement operations analysis using the ProcureOps REST API. Use when the task involves: (1) sourcing nomination readiness for programs or SKUs, (2) receiving-control closeout and AP invoice reconciliation, (3) AP close-desk payment-hold and vendor-balance reconciliation, (4) contract change-control impact analysis and amendment decisions, (5) AP release and receiving exception review with chargeback netting, or (6) any cross-entity procurement query spanning suppliers, items, programs, contracts, requisitions, purchase orders, receipts, invoices, payments, approvals, budget snapshots, and vendor risk events.
- ▌ Procurops Agent · prism-shadow bundleComplete procurement-operations analysis agent for the ProcureOps REST API. Queries suppliers, items, programs, contracts, purchase requisitions, purchase orders, receipts, AP invoices, AP payments, approvals, budget snapshots, and vendor risk events from a shared task-environment API, then cross-references records by foreign key to produce structured JSON answers for sourcing nomination readiness, receiving closeouts, AP close reconciliation, change-control decisions, and AP release/hold files. Use when the task provides a local memo or packet naming target program/supplier/PO/receipt/invoice IDs and expects a ProcureOps-backed JSON answer that follows an answer template.
- ▌ Procureops 6 · prism-shadow bundleProcureOps procurement reconciliation tasks: nomination readiness packets, receiving closeout reviews, AP payment-hold reconciliations, modular change-control decisions, and AP release/hold exception reviews. Use when the task references a TASK_ENV_BASE_URL ProcureOps API, a local answer_template.json, and needs to cross-reference purchase orders, receipts, invoices, contracts, suppliers, budgets, approvals, vendor risk events, and local payloads (memos, chargeback registers, release packets) to produce structured JSON decisions. Triggers on procurement-readiness, receiving-control, AP-close, change-control, and AP-release tasks.
- ▌ Asteria Dq Hub Certification · prism-shadow bundleReconcile source records, assign opaque control codes, and produce certification decisions against the Asteria Fleet Data Quality Hub. Use when the user references Asteria, a Fleet Data Quality Hub, TASK_ENV_BASE_URL, contact/partner onboarding certification, fuel-purchase normalization, freight-charge reconciliation, maintenance-log integrity, field-service roster readiness, or any audit that involves /api/catalog/collections, /api/catalog/schema, /api/contacts, /api/transactions/fuel, /api/transactions/freight, /api/maintenance/events, /api/source-snapshots, /api/reference/aliases, /api/reference/conversions, /api/reference/fx, or /api/query endpoints. Use whenever the task asks you to reconcile overlapping source records from this hub and produce a JSON certification answer conforming to a supplied answer template.
- ▌ Asteria Dq Hub 3 · prism-shadow bundleReconcile contact, fuel, maintenance, freight, or field-service collections against the Asteria Fleet Data Quality Hub read-only REST API. Use this skill whenever the user mentions the Asteria Fleet Data Quality Hub, Fleet Data Quality Hub, DQ Hub, Asteria DQ, reconciling Asteria data, partner onboarding certification, fuel audit, maintenance audit, freight accrual, field-service roster, or any task that references the /api/catalog/collections, /api/contacts, /api/transactions/fuel, /api/transactions/freight, /api/maintenance/events, or /api/query endpoints. Do not use for generic REST API tasks unrelated to Asteria Fleet data.
- ▌ Atlas Ops API · prism-shadow bundleSolve operational analytics and data-correction tasks against the Atlas Commerce Operations API. Use this skill whenever the user mentions Atlas Commerce Operations, the Atlas API, fulfillment scorecards, refund reconciliation, carrier quality corrections, warehouse productivity reviews, support health reviews, or any operational analytics task that references TASK_ENV_BASE_URL with a bearer token and SQL endpoints.
- ▌ Atlas Ops API 2 · prism-shadow bundleAnalyze the Atlas Commerce Operations database through its REST API. Use this skill whenever the user mentions Atlas, the workplace service, task-env, /api/schema, /api/data-dictionary, /api/sql, /api/sql/transaction, /api/correction-audit, fulfillment scorecards, refund reconciliation, carrier quality reviews, warehouse productivity, support health reviews, or any business-analytical task that requires querying the Atlas Commerce Operations schema. Also use it when the user asks about production orders, shipments, carrier scans, payment events, refund attempts, support cases, warehouse tasks, inventory movements, or campaign-attributed analytics.
- ▌ Atlas Ops Analyst · prism-shadow bundleAnalyze the Atlas Commerce Operations database through its authenticated REST API. Use this skill whenever the task involves Atlas data, Commerce Operations analytics, fulfillment metrics, refund reconciliation, carrier quality review, warehouse productivity, support health analysis, or any business-operations task that references a TASK_ENV_BASE_URL with /api/schema and /api/sql endpoints. This skill covers the complete workflow: reading the API schema and data dictionary, translating business definitions into SQL, building multi-step analytical queries, applying tiered classification rules, and writing results to an answer template.
- ▌ Pho Audit 4 · prism-shadow bundleExecute registered Public Health Observatory algorithmic transportability and robustness audits using a read-only evidence portal. Use this skill whenever a task references an analysis_request.json payload from the Public Health Observatory, involves a multi-module statistical audit with controlled decision gates, or mentions PHO protocols, transportability audits, or robustness audits. Do not use for generic public-health data analysis that lacks a registered protocol.
- ▌ Pho Audit Solver 3 · prism-shadow bundleSolve reproducible Public Health Observatory algorithmic audits. Use this skill whenever the task references a Public Health Observatory data portal, an analysis_request.json with audit modules, an answer_template.json contract, or asks to run registered algorithmic audit procedures on health/socioeconomic surveillance data. This covers state-level transport audits, county-level mediation or panel audits, country burden stratification, and any task that combines PHO portal data retrieval with deterministic statistical modules.
- ▌ Pho Algorithmic Audit 11 · prism-shadow bundleSolve Public Health Observatory algorithmic transportability audits. Use when the user presents an analysis_request.json and answer_template.json referencing a PHO protocol, mentions "Public Health Observatory", "algorithmic audit", "transportability", "PHO", or a task requiring six-module statistical computation against a read-only REST API at TASK_ENV_BASE_URL, or when the prompt asks to complete a registered audit using a Web portal with controlled publication gates.
- ▌ Portfolio Management · prism-shadow bundleAnalyze engineering portfolio data from a shared REST environment. Use when the user needs portfolio mix reviews, SLA aging audits, release readiness assessments, work item classification, blocker/dependency analysis, or any task that involves the portfolio management endpoints (work-items, mix-targets, sla-policy, releases, milestones, blockers, dependencies, query). Trigger on mentions of portfolio mix, SLA aging, release readiness, work item classification, engineering portfolio, quarterly review, blocker analysis, dependency chains, or tasks that reference a task environment base URL with these endpoints.
- ▌ Portfolio Analyzer · prism-shadow bundleAnalyze engineering portfolio data from a shared task-environment REST API. Use this skill whenever the user asks about portfolio mix reviews, SLA aging audits, release readiness assessments, work item classification, engineering capacity planning, or any task that references a TASK_ENV_BASE_URL with work items, mix targets, releases, milestones, blockers, dependencies, or SLA policies. This skill covers portfolio category analysis, SLA breach detection, release gating, dependency chain tracing, and duplicate/distractor record handling. Even if the user does not mention "portfolio" explicitly, use this skill for any task that queries work items grouped by scope, team, quarter, or release in an engineering-operations context.
- ▌ Portfolio Analytics · prism-shadow bundleAnalyze engineering work-item portfolios using a shared REST API. Use this skill whenever the user asks to review portfolio mix, audit SLA aging, assess release readiness, or perform any analysis over the engineering work-item environment. Trigger on phrases like "portfolio mix", "SLA aging", "release readiness", "work item audit", "closed-work review", or when the user provides a TASK_ENV_BASE_URL and asks to produce a structured JSON report from work-item endpoints.
- ▌ Harbor Crm Integration 3 · prism-shadow bundleBuild integrated HarborCRM workflows that join event, CRM, finance, trade-show, import-batch, and policy endpoints into reconciled, classified, and structured outputs. Use when the task involves: (1) post-event CRM handoff or reconciliation, (2) trade-show exhibitor prospecting with qualification and tiering, (3) import-batch cleaning, deduplication, and CRM import preparation, (4) cross-domain data joining across HarborCRM API segments, or (5) template-driven JSON output construction with controlled-enum classification and sorting rules.
- ▌ Harbor Crm Handoff 5 · prism-shadow bundleHarborCRM multi-entity data reconciliation and CRM handoff preparation. Use when preparing post-event or post-tradeshow CRM handoff records from HarborCRM API data. Handles five operational workflows: (1) post-event sponsor/lead reconciliation with controlled-status sponsor reporting, qualified non-sponsor lead handoff, badge-level exclusion, and CRM action counts, (2) tradeshow OEM/platform-based prospecting with qualified exhibitor lists, priority tiering, near-miss exclusion, and aggregate counts, (3) import-batch contact cleaning with deduplication, suppression, and CRM action classification, (4) post-event badge/opportunity/sponsor reconciliation including campaign-member actions and badge-only contact normalization, and (5) tradeshow lead ranking with demo-scored priority tiers, CRM overlap detection, and platform-coverage summaries. Use for any HarborCRM data reconciliation, cleaning, qualification, and structured JSON handoff task.
- ▌ Harborcrm Task Solver · prism-shadow bundleHarborCRM API task solver for event CRM handoff, trade show prospecting, and import batch preparation. Use when the task involves: (1) Fetching data from HarborCRM public API endpoints (events, trade shows, CRM, finance, imports, policies), (2) Cross-referencing CRM accounts, contacts, opportunities, campaign members, sponsor orders, invoices, badges, exhibitors, or import batches, (3) Producing a JSON output that conforms to a provided answer template, (4) Post-event CRM reconciliation or lead handoff, (5) Trade show exhibitor prospecting and lead qualification, (6) Import batch deduplication, suppression, and CRM import preparation. Trigger on mentions of HarborCRM, event_id, show_id, batch_id, sponsor_statuses, qualified_lead_accounts, campaign_member_actions, badge_decisions, crm_action, clean_contacts, ranked_leads, or answer_template.json with HarborCRM data.
- ▌ Clinic Decision Support 7 · prism-shadowUse when the user needs to produce a structured, protocol-driven clinical decision-support result from a synthetic clinic FHIR-like REST API. This includes respiratory assessments, pediatric head-injury triage, potassium replacement orders, care-management routing, observation-window retrieval, and any similar workflow where a case ID and a strict JSON answer template are provided. Trigger on phrases such as "clinical decision support", "protocol assessment", "clinic case", "synthetic clinic", "answer template", "structured JSON response", "FHIR", or mentions of clinic case IDs and runtime environments.
- ▌ Clinic Protocol Solver · prism-shadow bundleSolve structured clinical protocol decision-support tasks that query a synthetic clinic REST API, apply protocol logic to patient data, and return strictly-typed JSON conforming to a supplied answer template. Use this skill whenever the task mentions a clinic runtime environment, a TASK_ENV_BASE_URL, FHIR resources (Patient, Observation, Case, Medication, Allergy, etc.), clinical decision support, protocol assessments, care management routing, lab-result gating, or returning JSON that conforms to an answer_template.json file with controlled enumerations.
- ▌ Clinic Decision Support 8 · prism-shadowQuery a synthetic clinic REST API to retrieve clinical data and produce protocol-bound decision-support results as structured JSON. Use this skill whenever the task references a clinic runtime environment (TASK_ENV_BASE_URL), asks you to review patient records or clinical protocols, requires a JSON output conforming to a provided answer template, or mentions clinical decision support, medical protocol assessment, care management routing, potassium replacement, respiratory assessment, head injury triage, lab result interpretation, or FHIR-style API queries — even if the user does not name these terms explicitly.
- ▌ Investigation Review Hub 10 · prism-shadow bundleProduce structured JSON gap analyses, remediation dashboards, and production-readiness reviews by querying an Investigation Review Hub REST API and conforming to a task-provided answer-template schema. Use this skill whenever the user mentions an Investigation Review Hub, a review hub, legal-hold or production gap analysis, remediation dashboard, privilege-log review, eDiscovery readiness, or a grand jury / SEC / DOJ subpoena production review. Do not skip this skill when the task references <TASK_ENV_BASE_URL>, an answer template JSON file, or subpoena category codes.
- ▌ Investigation Review Hub 11 · prism-shadowProduce structured ediscovery investigation deliverables using the Investigation Review Hub REST API. Use this skill whenever the user mentions investigation review, gap analysis, privilege review, production readiness, remediation dashboard, retention review, custodian review, QC findings, subpoena categories, or any task that requires structured JSON output from a review-hub environment. Even when the user asks for a single metric or endpoint, consider whether the full hub workflow is needed — the task environment typically provides a `<TASK_ENV_BASE_URL>`, answer templates, and payload files that together demand end-to-end hub interaction.
- ▌ Investigation Review 2 · prism-shadowProduce structured JSON analysis reports for e-discovery matters using the Investigation Review Hub REST API. Use this skill whenever the task involves a matter ID, subpoena categories, production gaps, privilege logs, QC findings, retention events, remediation actions, custodian sources, or any structured gap, remediation, retention, or readiness review that references an answer_template.json and a <TASK_ENV_BASE_URL> placeholder. This applies to grand jury, SEC, DOJ, and any other investigation type served by the hub.
- ▌ Court Clerk Closeout 2 · prism-shadow bundleCourt docket closeout, sentencing reconciliation, and financial posting for criminal, traffic, and civil citation matters. Use when the user asks about court docket closeout, sentencing packages, financial reconciliation for court cases, post-disposition packets, traffic citation closeout with payment plans, or any task that involves cross-referencing local hearing notes, audit memos, finance worksheets, or petition summaries against a Court Operations Portal API. Trigger on mentions of circuit court, county court, docket closeout, sentencing order, fee reconciliation, court financial entry, payment plan for fines/costs, probation referral forms, license suspension orders, or placeholder handling for missing court identifiers. Even if the user does not use the exact phrase closeout, use this skill whenever they need to reconcile court case records with multiple conflicting local sources and produce structured financial or disposition JSON output.
- ▌ Court Clerk 5 · prism-shadow bundlePrepare court clerk closeout packages, sentencing packets, post-disposition financial and supervision packets, traffic violation closeouts, and disposition register entries. Use this skill whenever the user asks to reconcile court hearing notes, audit memos, finance queue extracts, petition summaries, or sentencing intake sheets with a Court Operations Portal API and produce structured JSON answers. Do not attempt court reconciliation work without consulting this skill — the domain rules and resolution hierarchy are non-obvious.
- ▌ Court Clerk Closeout 3 · prism-shadowPrepare court clerk closeout and field-packet JSON answers from local case materials and a Court Operations Portal REST API. Use when the user mentions court docket closeout, sentencing packets, traffic-violation disposition, post-sentencing field packets, clerk reconciliation, or defendant financial petitions. Do not use for generic legal document drafting or non-clerk workflows.
- ▌ Licensing Review 18 · prism-shadow bundlePerform structured licensing eligibility reviews using a shared REST+SQL licensing environment. Use this skill whenever the task involves contractor license applications, liquor license transfers, alcohol renewal queues, or any batch/single-application eligibility decision that requires cross-referencing multiple API-sourced records (bonds, insurance, violations, inspections, incidents, site evidence, license history, policies, correspondence) and producing a strictly templated JSON output. Trigger on phrases like contractor application review, liquor license staff package, alcohol renewal screening, licensing eligibility, or any prompt that supplies a TASK_ENV_BASE_URL with licensing data endpoints and an answer template.
- ▌ Licensing Review 19 · prism-shadow bundleReview regulatory licensing applications and produce structured JSON decisions for contractor eligibility, liquor license staff packages, and alcohol renewal queues. Use when the user mentions contractor applications, liquor license review, alcohol renewal screening, licensing board decisions, compliance review, or any task that requires cross-referencing licensing REST API endpoints to produce structured JSON determinations. Also use when the user provides target application IDs and a TASK_ENV_BASE_URL with licensing data endpoints.
- ▌ Licensing Review 20 · prism-shadow bundleComplete structured licensing review tasks for contractor, liquor, and alcohol renewal domains. Use this skill whenever a prompt mentions licensing review, contractor applications, liquor license transfer, alcohol renewal queue, licensing board, eligibility batch, staff package, manual review queue, renewal screen, or asks you to call licensing environment APIs ending in /api/policies, /api/contractor/, /api/liquor/, /api/alcohol/, or /api/renewal/. Trigger on any task that references a TASK_ENV_BASE_URL with licensing endpoints and an answer_template.json payload.
- ▌ Deal Workbench Review · prism-shadowHow to review M&A deal documents using the deal workbench API. Use when the task involves reviewing purchase agreements, producing issue registers, preparing closing packages, compiling committee escalation memos, conducting transition reviews, or building deviation matrices against a deal workbench. Applies to buyer-side or seller-side APA/SPA reviews, playbook comparisons, policy threshold checks, and any structured M&A deal analysis where the task provides an answer_template.json payload and references a running deal workbench at a TASK_ENV_BASE_URL.
- ▌ Ma Deal Review · prism-shadow bundleReview and analyze M&A deal terms on a deal workbench when the task involves comparing draft purchase-agreement terms against a buyer or seller playbook, identifying out-of-policy or missing terms, computing dollar amounts from headline purchase price, producing a structured JSON deliverable (issue register, closing package, committee escalation memo, deviation matrix, or transition review), or assessing closing readiness and blockers for an acquisition. Use this skill whenever the user mentions deal review, APA, SPA, issue register, closing package, committee escalation, deviation matrix, transition review, playbook comparison, or any M&A workbench task with a deal ID and a client side (buyer/seller).
- ▌ Deal Workbench 4 · prism-shadow bundlePrepare structured M&A deliverables — issue registers, economics packages, committee escalation memos, transition reviews, and deviation matrices — from a deal workbench API. Use when the user asks for M&A work, deal analysis, contract/term comparison against a playbook or policy, closing readiness assessment, indemnity/escrow/survival review, regulatory (HSR) checks, employee continuity analysis, or any structured deliverable tied to a deal workbench. Use whenever the prompt mentions a deal ID, playbook, policy thresholds, committee escalation, APA/SPA terms, or asks you to produce a JSON deliverable from deal data.
- ▌ Asteria Dq Hub 2 · prism-shadow bundleUse when the task involves reconciling, auditing, certifying, or computing derived metrics from the Asteria Fleet Data Quality Hub REST API. Triggers on mentions of Asteria, Fleet Data Quality Hub, fleet data reconciliation, partner onboarding certification, fuel audit, maintenance event audit, field-service roster, freight charge audit, or any task that supplies a case_scope.json plus an answer_template.json and references a base URL for a read-only data quality API. Also use when the user asks to audit or reconcile fleet, fuel, freight, maintenance, or contact data from an HTTP API.
- ▌ Credit Risk Committee 5 · prism-shadow bundlePrepare credit risk committee deliverables from the shared credit office API. Use this skill whenever the task involves a credit-risk committee review, branch loan portfolio analysis, risk-rating migration review, lending-committee allocation package, credit-union segment posture page, watch-list stress packet, CRE competing-credit decision, FDIC or NCUA benchmark comparison, CDFI-style risk classification, DSCR stress testing, concentration-limit checks, or any committee-ready credit memo. The skill encodes the full policy framework and API surface; always load it before computing committee outputs.