prism-shadow
- 1.7k skills
- 0 followers
- 5 days ago last updated
- ▌ Atlas Commerce Ops Analysis 2 · prism-shadow bundleUse for Atlas Commerce Operations tasks that ask Codex to query the authenticated workplace API, compute cutoff-based operational metrics, apply an explicitly approved canonical correction, and write a strict JSON answer file from a provided request payload and answer template.
- ▌ Atlas Commerce Ops 9 · prism-shadow bundleSolve Atlas Commerce Operations analytical and controlled-correction tasks against authenticated workplace APIs. Use when prompts require strict answer.json outputs from the Atlas database, schema and data-dictionary discovery, read-only SQL analysis, fulfillment, refunds, warehouse, support, carrier, inventory, or approved minimal canonical corrections with correction_audit verification.
- ▌ Public Health Observatory Audits 3 · prism-shadow bundleSolve Public Health Observatory portal audit tasks that provide analysis_request.json and answer_template.json, especially exact protocol IDs PHO_STATE_TRANSPORT_AUDIT_V1, PHO_COUNTY_MEDIATION_TRANSPORT_V1, PHO_STATE_ROBUSTNESS_TRANSPORT_V1, PHO_COUNTY_PANEL_TRANSPORT_V1, and country_burden_revision_audit_v1 style requests. Use for deterministic publication/cohort resolution, grouped prediction audits, cluster bootstrap, conformal calibration, PCA/k-means stability, source perturbation, mediation, GMM, and controlled JSON decisions.
- ▌ Pho Algorithmic Audits 6 · prism-shadow bundleSolve Public Health Observatory web-portal audit tasks that provide analysis_request.json and answer_template.json, including state, county, and country public-health release resolution, cohort construction, regression, GMM, ridge or elastic-net validation, wild-cluster bootstrap, grouped conformal calibration, PCA clustering, perturbation audits, and controlled JSON decisions.
- ▌ Pho Algorithmic Audits 7 · prism-shadow bundleSolve Public Health Observatory portal audits from analysis_request.json and answer_template.json, especially exact protocol IDs PHO_STATE_TRANSPORT_AUDIT_V1, PHO_COUNTY_MEDIATION_TRANSPORT_V1, PHO_STATE_ROBUSTNESS_TRANSPORT_V1, PHO_COUNTY_PANEL_TRANSPORT_V1, and country burden revision PCA or clustering audits. Use for Web-only PHO tasks requiring release resolution, cohort construction, clustered models, nested validation, bootstrap checkpoints, conformal calibration, PCA clustering, perturbation audits, and controlled JSON decisions.
- ▌ Northstar Payer Ops 17 · prism-shadow bundleProduce strict JSON determinations, appeal dispositions, payment correction packets, peer-to-peer summaries, and UM-finance queue summaries from the Northstar payer-operations environment. Use when prompts reference Northstar Health Plan, prior authorization or UM nurse review, pharmacy appeals, manufacturer assistance, payment integrity claim repricing, peer-to-peer closure, or service margin queue analysis with provided answer templates and task_context payloads.
- ▌ Northstar Payer Ops 18 · prism-shadowSolve Northstar Health Plan payer-operations tasks by querying the provided environment and returning schema-conforming JSON for prior authorization, pharmacy appeals and assistance intake, claim repricing, peer-to-peer closure, service-margin queues, and mixed UM-finance triage. Use when prompts mention Northstar payer operations, UM nurse determination summaries, appeals coordinators, payment integrity correction packets, P2P summaries, queue analysis, answer_template.json, or the task environment SQL/API endpoints.
- ▌ Northstar Payer Ops 19 · prism-shadow bundleSolve Northstar Health Plan payer-operations tasks that require live task-environment evidence and strict JSON output for prior authorization UM reviews, pharmacy appeals and assistance intake, payment-integrity claim repricing, peer-to-peer dispositions, or therapy finance margin queues. Use when prompts mention Northstar, payer operations, TASK_ENV_BASE_URL, sql/query, authorization cases, appeals, claims, P2P, rate schedules, or service margin queues.
- ▌ Ehr Quality JSON Packets 4 · prism-shadow bundleCreate normalized JSON packets for EHR quality-governance tasks that require querying a read-only task API. Use for duplicate chart merge readiness, referral coordination, care transition handoff packets, ServiceRequest quality checks, ICD-10 and service-code validation, and referral batch audits where the prompt provides an answer_template.json and IDs such as patient, referral, duplicate candidate, provider, ServiceRequest, or batch identifiers.
- ▌ Ehr Quality Governance 6 · prism-shadow bundleReusable workflow for solving read-only EHR quality-governance JSON tasks against a task API. Use when prompts ask for normalized duplicate-chart merge readiness packets, referral coordination packets or audits, care transition packets, ServiceRequest quality checks, active-list reconciliation, ICD/service-code validation, provider contacts, evidence ID selection, risk flags, follow-up queues, action tiers, or summary counts from patient/referral/provider/duplicate records.
- ▌ Ehr Quality Packet 2 · prism-shadow bundleBuild normalized JSON for read-only EHR quality-governance tasks from a prompt, answer_template.json, and a task environment. Use for duplicate-chart merge readiness, referral coordination and audits, care transition packets, ServiceRequest validation, ICD-10/service-code/provider checks, active clinical list reconciliation, document/audit evidence selection, and schema-conforming JSON-only outputs.
- ▌ Clinic Protocol JSON 10 · prism-shadow bundleUse when solving synthetic-clinic protocol tasks that provide environment_access.md, a clinic runtime base URL, and input/payloads/answer_template.json, and require one schema-conformant JSON object for clinical decision support, observation-window retrieval, medication or lab recommendations, respiratory or head-injury assessment, potassium replacement, or care-management routing.
- ▌ Synthetic Clinic Cds · prism-shadow bundleProduce strict JSON clinical decision-support answers for synthetic clinic runtime tasks. Use when a prompt provides a target case id, an answer_template.json schema, and task environment API access for protocol-bound assessments such as respiratory infection, pediatric head injury, potassium replacement, care-management routing, or observation-window lab gates.
- ▌ Synthetic Clinic Protocol JSON 11 · prism-shadow bundleSolve synthetic clinic runtime tasks that require reviewing FHIR-like case data, protocol materials, and answer_template.json to return exact protocol-bound clinical decision-support JSON. Use for respiratory CAP assessment, pediatric head injury triage, potassium repletion, care-management routing, and observation-window protocol gate tasks against the allowed clinic API.
- ▌ Review Hub Remediation JSON · prism-shadow bundleBuild structured JSON answers for Investigation Review Hub legal review tasks involving production gaps, retention and preservation losses, source collection gaps, privilege-log defects, QC miscoding, and remediation action plans. Use when a prompt asks for a JSON-only subpoena, SEC, grand jury, production-readiness, gap-analysis, or remediation dashboard answer from Review Hub API endpoints and an answer_template.json file.
- ▌ Investigation Review Hub JSON 3 · prism-shadow bundleProduce schema-conformant structured JSON legal review outputs from an Investigation Review Hub. Use for subpoena, grand jury, SEC, DOJ, production-readiness, retention, preservation, privilege-log, QC, custodian-source, and remediation dashboard tasks that require hub-only evidence, stable record IDs, category rollups, metrics, and prioritized action plans.
- ▌ Investigation Review Hub 5 · prism-shadow bundleUse for legal investigation review tasks that require structured JSON from an Investigation Review Hub, including production gap analysis, retention and litigation-hold loss review, SEC/DOJ remediation dashboards, privilege-log/QC production-readiness reviews, and cross-system action plans based on hub endpoints plus task-local answer templates.
- ▌ Court Closeout JSON 4 · prism-shadow bundleUse this skill for court-operations tasks that require clerk-ready JSON closeout packets, disposition registers, payment plans, financial-petition reviews, probation referrals, license orders, fee reconciliation, docket actions, placeholders, and audit findings from local payloads plus a Court Operations Portal API.
- ▌ Court Closeout Reconciler 4 · prism-shadow bundlePrepare clerk-ready JSON court closeout, disposition register, payment plan, probation referral, and license/payment order packets from local payloads plus a Court Operations Portal. Use for criminal or traffic matters requiring reconciliation of case/citation status, charges, docket entries, fee schedules, payment policies, forms, financial petitions, placeholders, exclusions, and batch totals against an answer_template.json.
- ▌ Court Ops Closeout JSON · prism-shadow bundleReconcile Court Operations Portal records with local clerk, hearing, finance, petition, form, fee-schedule, and payment-policy payloads to produce strict clerk-ready JSON for criminal or traffic disposition closeouts, fee registers, payment plans, probation referrals, license-suspension orders, audit findings, exclusions, and case-file placeholders.
- ▌ Licensing JSON Review 2 · prism-shadow bundleBuild structured JSON answers for licensing-environment review tasks that use TASK_ENV_BASE_URL data. Use for contractor eligibility batches, restricted liquor-license staff packages, and alcohol renewal manual-review queues involving policies, applications, bonds, insurance, license history, violations, correspondence, inspections, settlements, privileges, incidents, site evidence, answer_template.json schemas, determinations, controls, verification gaps, or ranked queues.
- ▌ Private Wealth Advisory JSON 4 · prism-shadow bundleProduce structured private-wealth advisory JSON from task prompts, answer templates, request memos, and the advisory API. Use for Roth conversion/RMD projections, ILIT Crummey funding cycles, GRAT versus CRAT comparisons, and estate-liquidity action plans that require source resolution across client profiles, source documents, retirement accounts, life-insurance records, trust candidates, tax policy constants, and RMD factors.
- ▌ Crescent Finance Ops 8 · prism-shadow bundleProduce Crescent Finance Ops JSON reports from task payloads and the Finance Ops API. Use for Crescent Arts Collective branch close reports, regional finance views, current-year compensation summaries, compensation forecasts, and touring production weekly payroll reviews that provide request_memo.json, answer_template.json, and environment_access.json payloads.
- ▌ Crescent Finance Ops Reporting 8 · prism-shadowUse for Crescent Arts Collective Finance Ops API tasks that require a structured JSON reporting answer from finance, compensation, or payroll endpoints, including branch close packages, regional views, compensation summaries and forecasts, and weekly payroll reviews.
- ▌ Crescent Finance Ops 9 · prism-shadow bundleCompute Crescent Finance Ops reporting answers from staged task inputs and the Finance Ops API. Use when a task asks for Crescent Arts Collective branch close, regional management, compensation summary or forecast, or touring theatre weekly payroll JSON using payloads/environment_access.json, payloads/request_memo.json, and payloads/answer_template.json.
- ▌ Asteria Investment Office JSON 8 · prism-shadowSolve Asteria Investment Office JSON tasks that combine current portfolio records, holdings, bonds, issuers, index levels, policy thresholds, prior views, and macro signals. Use for strict JSON outputs such as credit trade packages, fixed-income rotations, correlation reviews, allocation view refreshes, or committee summaries.
- ▌ Asteria Investment Office 3 · prism-shadow bundleSolve Asteria Investment Office JSON tasks that require the shared environment as the current book of record for portfolios, holdings, bonds, issuers, energy signals, index correlations, active allocation views, fixed-income risk rotations, and multi-asset committee decisions. Use when prompts mention Asteria portfolios, payload answer templates, stale local worksheets, CIO/risk/committee reviews, or environment-backed investment records.
- ▌ Asteria Investment Office 4 · prism-shadow bundleSolve Asteria Investment Office JSON tasks that require using the shared environment as the current book of record for portfolio holdings, fixed-income trades, equity-index correlations, active allocation views, macro signals, policies, and committee/risk outputs. Use when prompts mention Asteria portfolios, PF-* ids, energy credit, fixed-income risk rebalance, international equity correlation, allocation view refreshes, or committee decision JSON.
- ▌ Credit Office Committee Packets · prism-shadow bundleProduce committee-ready JSON from the public credit office API for branch regrade reviews, lending allocation packages, credit-union segment posture pages, watch-list stress packets, and competing CRE decisions. Use when the prompt provides a branch_id or segment_id, a TASK_ENV_BASE_URL, benchmark or policy data, and a strict answer template.
- ▌ Credit Office Committee JSON 7 · prism-shadow bundleSolve public credit-office committee JSON tasks that use TASK_ENV_BASE_URL, answer templates, branch records, loans, applications, sector exposures, policies, FDIC benchmarks, or NCUA benchmarks. Use when asked to produce branch rating migrations, lending allocations, CRE comparisons, watch-list stress packets, or credit-union segment posture pages as JSON only.
- ▌ Credit Office Committee · prism-shadow bundlePrepare committee-ready JSON credit-office answers from the public task API. Use for branch risk-rating migration, pending loan allocation, credit-union segment posture, adverse-rated watch-list stress, and competing CRE application decisions that must follow a supplied answer_template.json.
- ▌ Peopleops Console Case Workflow · prism-shadow bundleInspect and resolve PeopleOps Console lifecycle-control cases by querying the live API for employees, leave, payroll, recruitment, documents, messages, policies, and audit logs, then return JSON that matches the provided answer template. Use when a prompt asks for authoritative record selection, source precedence, folder readiness, notice quality, payroll readiness, recruiting handoff, audit scoping, or similar PeopleOps case analysis.
- ▌ Peopleops Console Controls 2 · prism-shadow bundleSolve PeopleOps Console verification and reconciliation tasks that require collecting HR case, employee, leave, payroll, recruitment, document, message, policy, and audit evidence from the task environment, applying source-precedence and draft-exclusion rules, and returning strict JSON matching an answer template.
- ▌ Peopleops Console Controls 3 · prism-shadow bundleSolve PeopleOps Console evidence-control tasks that require logging into a task environment, reconciling HR records, and returning JSON matching an answer_template. Use for onboarding closeout, remote-work case readiness, recruitment reconciliation, leave source precedence, payroll assignment, accrual readiness, formal notice, audit-scope, and folder control reviews.
- ▌ Cedar Ridge Intake 9 · prism-shadow bundleSolve Cedar Ridge Intake Coordination Portal tasks that require strict JSON outputs for patient access verification, specialty referral readiness or chart activation, dialysis transfer packet review, and chronic-care program enrollment. Use when prompts reference the Cedar Ridge portal, TASK_ENV_BASE_URL, rosters, referral batches, transfer batches, program candidates, or answer_template.json controlled values.
- ▌ Cedar Ridge Intake Coordination 6 · prism-shadow bundleReusable workflow for Cedar Ridge Intake Coordination Portal tasks that require JSON-only healthcare intake audits from TASK_ENV_BASE_URL. Use for patient access verification, referral readiness or chart activation, dialysis transfer reviews, chronic-care program enrollment panels, and similar tasks that join portal REST or SQL data with input/payloads/answer_template.json.
- ▌ Cedar Intake Reconciliation · prism-shadow bundleSolve Cedar Ridge Intake Coordination Portal tasks that require querying patients, referrals, transfers, documents, charts, programs, coverage, PBM, pharmacies, ICD metadata, or facility capacity and returning strict JSON for access verification, referral readiness, dialysis transfer review, chronic-care enrollment, or referral-to-chart activation.
- ▌ Support Console Ops 2 · prism-shadow bundleResolve support-console tasks that classify tickets, queue cases, mobile recovery actions, or enterprise export complaints into strict JSON from a provided answer template. Use when the prompt references the shared support console API, ticket/case/export payloads, or asks for ordered decision rows, summaries, owners, routing, or response packages.
- ▌ Support Console Solver · prism-shadowInspect the live support-console API, follow IDs from payload files, and return only JSON that matches the supplied answer template. Use when a prompt references the shared support console, offline ticket batches, contact-center case queues, mobile-data recovery, queue-quality review, or enterprise export complaints and asks for evidence-based JSON instead of assumptions.
- ▌ Apexcloud Retention Ops 23 · prism-shadow bundleAnalyze ApexCloud Retention Operations API prompts that require JSON-only retention, revenue, receivables, churn, QBR, or action-board outputs. Use when a task asks you to query the task environment API, reconcile account data, rank renewal or churn risk, summarize monthly metrics, map overdue receivables to CRM accounts, or produce a structured board, packet, or validation readout from a provided template.
- ▌ Apex Retention Ops 2 · prism-shadow bundleAnalyze ApexCloud Retention Operations API tasks that ask for JSON retention queues, QBR packets, receivables reviews, pipeline summaries, high-touch action boards, or churn export rankings. Use when prompts mention ApexCloud, TASK_ENV_BASE_URL, account metrics, tickets, NPS, billing snapshots, A/R aging, opportunities, HR or event summaries, or churn CSV exports and require controlled enums, policy codes, ranking, or deterministic precision.
- ▌ Apexcloud Retention Ops 24 · prism-shadow bundleStructured JSON reporting from the ApexCloud Retention Operations API and churn exports. Use when a prompt asks for a renewal-risk queue, retention board, QBR metrics packet, receivables and pipeline review, or churn model validation and candidate ranking from the task environment, billing snapshots, AR aging, tickets, NPS, opportunities, HR summary, event performance, or churn CSV files.
- ▌ Finance Control API Review · prism-shadow bundleReconcile finance-control batches against runner-provided JSON APIs and local answer templates. Use when solving ERP, AP, compliance, vendor onboarding, prepaid close, reimbursement close, stale AP snapshot refresh, or account-change payment release tasks that require a strict JSON decision output.
- ▌ Finance API Controls 2 · prism-shadow bundleSolve finance-control tasks that combine local JSON/CSV payload scopes with a runner-provided ERP/compliance API. Use for reimbursement or AP close batches, stale AP export refresh checks, vendor onboarding or account-change payment release reviews, and prepaid schedule-to-GL reconciliations requiring strict JSON output.
- ▌ Erp Finance Control Review 3 · prism-shadowSolve ERP finance-control review tasks that require querying a runner-provided JSON API and returning strict JSON. Use for reimbursement/AP batch close, stale AP snapshot reconciliation, vendor onboarding or account-change release risk, and prepaid close reconciliation tasks involving claims, bills, payments, vendors, compliance records, prepaid invoices, GL balances, and answer templates.
- ▌ Procureops Control Packets · prism-shadowRead ProcureOps task prompts and payloads, query the live ProcureOps API, and produce strict JSON packets for sourcing nominations, receiving and AP closeouts, change-control decisions, release or hold queues, budget checks, and related procurement operations.
- ▌ Procureops Reconciliation 5 · prism-shadow bundleBuild JSON-only ProcureOps sourcing, receiving, AP close, AP release, contract-change, budget, approval, and supplier-risk reconciliation answers from task-local payloads plus the shared ProcureOps API. Use when prompts mention ProcureOps endpoints, purchase orders, receipts, invoices, payments, contracts, budgets, approvals, vendor risk, sourcing nomination readiness, receiving closeout, AP hold/release queues, or change-control decision files.
- ▌ Procureops Packet Reconciliation · prism-shadow bundleUse for ProcureOps API task packets that ask for JSON-only sourcing nomination readiness, receiving closeout, AP invoice hold/release, AP close/vendor-balance reconciliation, or change-control decision files. Guides reading local input/payloads answer_template and memo/packet files, fetching ProcureOps endpoints from TASK_ENV_BASE_URL, joining supplier/item/program/requisition/contract/purchase-order/receipt/invoice/payment/approval/budget/risk records, computing rounded USD and quantity reconciliations, and emitting template-exact JSON.
- ▌ Northwind Erp Desk 3 · prism-shadowSolve Northwind Components ERP desk tasks that turn a prompt, memo, and live task-environment API data into a strict JSON answer. Use when asked to prepare expedite queue decisions, allocation or transfer reviews, replenishment plans from BOMs, supplier incident scorecards, or procurement-control decisions from the shared Northwind ERP API and an answer template.
- ▌ Northwind Erp Operations 3 · prism-shadow bundleSolve Northwind Components ERP API operational JSON tasks, including dispatch expedite queues, mixed-warehouse allocation, kit replenishment, supplier incident scorecards, and procurement quality controls. Use when a task provides local payload templates or memos plus a Northwind ERP API base URL, and asks for strict JSON from orders, products, customers, inventory, warehouses, shipping quotes, BOMs, suppliers, purchase orders, or incidents.
- ▌ Northwind Erp JSON · prism-shadow bundleSolve Northwind Components ERP API tasks that require JSON-only operational decisions or scorecards from local prompts, payload templates, and live ERP endpoints, including order allocation or expedite waves, BOM replenishment plans, supplier incident scorecards, and procurement quality controls.
- ▌ Private Wealth Advisory Planner 3 · prism-shadowStructured private wealth advisory case solving from staged API data and request memos. Use when producing final JSON for Roth conversion and RMD summaries, ILIT Crummey funding checks, GRAT versus CRAT comparisons, or estate liquidity plans that require source conflict resolution, tax-policy lookups, account exports, and ISO date or USD normalization.
- ▌ Private Wealth Advisory JSON 3 · prism-shadow bundlePrepare structured JSON answers for private wealth advisory planning tasks that use the task-group advisory API, request_memo.md, and answer_template.json. Use for Roth conversion/RMD summaries, ILIT Crummey funding cycles, GRAT vs CRAT comparisons, and estate liquidity action plans where client facts must be reconciled across signed profiles, attorney memos, CRM notes, custodian exports, life insurance records, trust candidates, tax policy constants, and RMD factors.
- ▌ Atlas Ops · prism-shadow bundleOperational analytics and data-quality correction workflows against the Atlas Commerce Operations database. Use this skill whenever the user needs to query fulfillment, refund, carrier, warehouse, support, or financial records from the Atlas workplace, run SQL analysis, apply controlled canonical corrections, compute business metrics from raw event data, or produce operational scorecards from the Atlas schema. Trigger on mentions of Atlas, commerce operations, operational analytics, fulfillment scorecards, refund reconciliation, carrier quality review, warehouse productivity, support health, shipping data, payment/settlement data, or any request that references an authenticated workplace SQL/transaction service.
- ▌ Atlas Commerce Ops 7 · prism-shadow bundleAnalyze or correct operational data through the Atlas Commerce Operations API. Use this skill whenever a task references an authenticated Atlas workplace, Atlas Commerce Operations, a task environment base URL, or an API with /api/schema, /api/sql, /api/sql/transaction, or /api/correction-audit endpoints. The skill covers the API contract, source-record deduplication, effective event selection, integer boolean and monetary conventions, controlled data corrections, and strict answer-template output.
- ▌ Pho Algorithmic Audit 9 · prism-shadow bundleComplete registered algorithmic audits against the Public Health Observatory (PHO) data portal. Use when the user presents an analysis_request.json and answer_template.json against a PHO portal, needs to resolve publication records into analytic cohorts, run a sequence of registered statistical audit modules, and return one JSON object conforming to an answer template. Trigger on PHO, Public Health Observatory, algorithmic audit, analysis_request, answer_template, protocol_id, or any mention of a read-only health-data portal with registered audit protocols.
- ▌ Pho Audit Solver · prism-shadow bundleSolve Public Health Observatory algorithmic audit tasks. Use this skill whenever the user mentions a Public Health Observatory audit, a PHO protocol, an analysis_request.json with audit modules, or needs to complete a registered algorithmic audit against the Observatory web portal. Also use this skill when the user references state/county/country health data analysis with robust statistical methods (delete-cluster jackknife, nested ridge/elastic-net CV, wild cluster bootstrap, grouped conformal, PCA trajectory clustering, source perturbation) tied to answer_template.json output contracts. The skill should be consulted even when the user only hints at "observatory data," "algorithmic audit," "publication board," or "transportability" analysis.
- ▌ Pho Audit · prism-shadow bundleExecute registered Public Health Observatory algorithmic audits using only the PHO REST API. Use this skill whenever the user needs to resolve PHO publication releases, construct study cohorts from health and socioeconomic data, or run any registered multi-module audit (transportability, mediation, burden stratification, robustness, or county dynamics) that requires clustering, ridge or elastic net, wild bootstrap, conformal prediction, PCA trajectory clustering, source perturbation, or Shapley attribution. The skill covers all PHO algorithmic audit families including state-level, county-level, and country-level protocols.
- ▌ Work Intelligence · prism-shadow bundleAnalyze engineering work items through a shared task-environment API. Use this skill whenever the user needs to produce work-intelligence reports including portfolio mix reviews, SLA aging audits, release readiness assessments, or blocker/dependency analysis from a work-tracking system. The skill provides endpoint discovery, data-quality rules, classification conventions, and output schemas. Trigger on requests involving portfolio mix, SLA aging, release readiness, work item classification, engineering metrics, or blocker analysis.
- ▌ Eng Portfolio Review · prism-shadow bundleQuery and analyze engineering work-item portfolios from a shared REST API. Use this skill whenever the task involves portfolio mix comparison against targets, SLA aging audits with overdue/breach-rate calculations, or release-readiness assessments with milestone tracking, blocker analysis, and dependency-chain resolution. Also use it when the user mentions work-item classification, SLA compliance, release gating, or any analysis that references the work-item REST API endpoints and asks for structured JSON output from them.
- ▌ Engineering Portfolio · prism-shadow bundlePerform engineering portfolio management tasks using a shared task-environment API. Use this skill whenever the user asks you to prepare a portfolio mix review, SLA aging audit, or release readiness assessment that involves querying work items, mix targets, SLA policies, releases, milestones, blockers, or dependencies. Also use this when the user mentions closed-work portfolio analysis, overdue SLA work, ship decisions, milestone completion, blocker cause counts, or dependency chains. This skill covers portfolio mix classification, SLA breach rate calculation, and release readiness scoring across engineering teams, quarters, and product areas.
- ▌ Harborcrm Structured JSON · prism-shadowAnalyze HarborCRM event, trade-show, sponsor, import-batch, and CRM reconciliation tasks that require producing one JSON object from API data and a provided answer template. Use when a prompt references HarborCRM endpoints such as `/api/events`, `/api/tradeshows`, `/api/import_batches`, `/api/crm`, `/api/finance`, or `/api/policies` and asks for JSON-only output with filtering, classification, ranking, deduplication, normalization, counts, or follow-up summaries.
- ▌ Harborcrm Reconcile · prism-shadow bundleProduce schema-conforming JSON for HarborCRM CRM, event, trade-show, and import-batch tasks. Use when asked to audit post-event CRM handoffs, reconcile sponsor badges, invoices, campaign members, prepare CRM import batches, deduplicate or suppress contacts, or build qualified exhibitor and prospecting summaries from HarborCRM API data.
- ▌ Harborcrm Reconciliation 6 · prism-shadow bundleReconcile HarborCRM API records into exact JSON outputs that match a supplied answer template. Use when a task asks for event handoffs, sponsor finance summaries, badge or campaign-member reconciliation, trade-show prospecting, import-batch cleanup, or other structured CRM analysis using HarborCRM endpoints, policies, accounts, contacts, opportunities, invoices, exhibitors, badges, or campaign members.
- ▌ Medbridge Sales Ops 12 · prism-shadow bundleSolve MedBridge Sales Ops API tasks that require account-ready JSON for quote pricing, freight comparisons, RFQs, opportunity milestone reconciliation, revenue recognition, invoice follow-up, events, and vouchers. Use when prompts mention MedBridge Sales Ops, quote/RFQ/opportunity IDs, product catalog tiers, freight quotes, policies, or returning JSON matching an answer_template.json.
- ▌ Medbridge Sales Ops 13 · prism-shadow bundleUse for MedBridge Sales Ops API tasks that ask for account-ready JSON quote packages, RFQ/module quotes, freight comparisons, customer policy flags, opportunity milestone reconciliation, invoice/payment/revenue recognition status, or linked event/voucher follow-up actions.
- ▌ Medbridge Sales Ops 14 · prism-shadowPrepare JSON-only MedBridge Sales Ops API decision packages. Use for tasks that ask Codex to verify customers, RFQs, quotes, product catalog tiers, freight quotes, policies, opportunities, invoices, payments, revenue journals, events, or vouchers from a provided task environment base URL and return an account-ready quote, transport, finance, reconciliation, or follow-up JSON matching a supplied answer template.
- ▌ Support Console Ops · prism-shadow bundleResolve support-console JSON tasks for offline service tickets, contact-center case queues, mobile-data recovery, queue-quality reviews, and enterprise export complaint packages. Use when the prompt references ticket batches, queue snapshots, case queues, mobile-data worklists, or export complaint evidence and requires a JSON answer matching a template.
- ▌ Investigation Review Hub 4 · prism-shadowProvides a disciplined workflow for querying an Investigation Review Hub REST API to build structured e-discovery review deliverables (gap analyses, privilege audits, production-readiness assessments, retention reviews, cross-system remediation dashboards). Use this skill whenever the user mentions subpoena response, litigation-hold review, privilege-log analysis, production readiness, retention gap assessment, QC remediation, or any investigation/e-discovery review task that references a shared hub API with endpoints like /api/matters, /api/documents/search, /api/privilege-log, /api/qc-findings, /api/retention-events, /api/custodian-sources, and /api/query.
- ▌ Investigation Hub · prism-shadow bundleProduces structured JSON analysis for legal investigation matters by querying an Investigation Review Hub API. Use this skill whenever the task mentions matter IDs like MTR-*, subpoena categories, production gaps, privilege logs, retention events, QC findings, custodian sources, remediation actions, grand jury or SEC investigations, or asks for any kind of gap analysis, readiness review, or remediation dashboard from a review hub. Even if the task only mentions a "hub" or "review endpoint" without full terminology, consult this skill.
- ▌ Court Clerk Closeout · prism-shadow bundlePrepare court clerk closeout and financial reconciliation packets by cross-referencing local case materials against a Court Operations Portal REST API. Use this skill whenever the task involves court case docket closeout, sentencing disposition reconciliation, fee schedule audits, payment plan computation, traffic citation financial entry, probation referral packet assembly, license suspension orders, or any clerk-of-court batch register preparation. Trigger even when the user describes the work as "sentencing closeout," "disposition register," "post-sentencing packet," "traffic violation hearings," "financial petition review," or "clerk audit."
- ▌ Court Clerk · prism-shadowCourt clerk closeout, reconciliation, and post-sentencing packet preparation. Use this skill whenever the user is preparing a criminal or traffic case closeout, reconciling audit conflicts against court records, preparing post-sentencing field packets with probation referral and license suspension orders, reconciling payment petitions against court policy, producing a structured register-ready JSON answer from local case materials and a court operations portal, or performing any court-clerk workflow that involves cross-referencing hearing notes, finance extracts, and intake sheets against an authoritative case-management API. Do NOT use for general legal analysis, drafting legal briefs, or interpreting statutes outside the clerk closeout context.
- ▌ Court Clerk 2 · prism-shadowUse this skill whenever the user asks you to prepare court closeout packages, criminal disposition registers, traffic citation payment plans, post-sentencing field packets, probation referral forms, license suspension and installment payment orders, financial petition packets, or any court-clerk reconciliation task that involves multi-source data (hearing notes, clerk memos, intake sheets, worksheets, petition summaries, form excerpts) together with a Court Operations Portal REST API. Also use this skill when the user mentions court financial reconciliation, audit findings against a CMS, fee schedule verification, docket entry preparation, or clerk-ready JSON output for a circuit or district court. Trigger even when the user does not explicitly say "court clerk" -- any task that asks you to cross-reference local case materials against a portal, resolve audit conflicts, compute payment plan schedules, prepare probation or license forms, or produce structured court register JSON should use this skill.
- ▌ Licensing Review 10 · prism-shadow bundleGuide for producing structured licensing-review decisions from a regulatory data environment. Use when the task asks for contractor application batch decisions, restricted liquor-license staff packages, or alcohol renewal manual-review queues. Also use when the prompt mentions licensing boards, contractor eligibility, liquor transfer reviews, renewal screening, or any kind of structured regulatory determination that pulls data from a licensing API.
- ▌ Licensing Review 11 · prism-shadow bundleMulti-domain licensing review for contractor eligibility, liquor license transfer packages, and alcohol renewal queues. Use when the user asks about licensing applications, license renewals, contractor eligibility review, liquor license review, alcohol renewal queues, or staff licensing packages. Also use when the user mentions licensing boards, restricted licenses, contractor batch review, or renewal manual-review queues. This skill covers the State Contractors Licensing Board, Alcohol Control Board, and Alcohol Renewal Unit workflows.
- ▌ Licensing Review 12 · prism-shadow bundleState licensing review workflows for contractor eligibility batches, restricted liquor license staff packages, and alcohol renewal manual-review queues. Use this skill whenever the user mentions contractor licensing, liquor license review, alcohol renewal screening, licensing board decisions, license application review, compliance staff packages, or any task that involves fetching licensing data from a REST API and producing a structured JSON decision output. Even when the user does not explicitly name the domain, if they describe a batch of applications, a license review package, or a ranked compliance queue tied to licensing endpoints, use this skill.
- ▌ Deal Workbench · prism-shadow bundleUse when analyzing M&A deals through a running deal workbench REST API. Triggers on any prompt mentioning a deal workbench at <TASK_ENV_BASE_URL>, deal IDs like PRJ_XXXXXX, seller or buyer APA/SPA review, committee escalation packages, transition reviews, deviation matrices, or workbench API routes like /api/deals, /api/playbooks, /api/policies, /api/query. Always use this skill when the task involves comparing draft deal terms against playbook or policy rules, producing structured JSON deal-analysis outputs, or gathering workbench data for M&A counsel deliverables.
- ▌ Deal Workbench 2 · prism-shadow bundleUse the M&A deal workbench REST API to review acquisition agreements, produce structured legal deliverables (issue registers, closing-package analyses, committee escalation memos, transition reviews, deviation matrices), and cross-reference draft terms against party playbooks or policy thresholds. Use this skill whenever the user needs to analyze a deal on the workbench, prepare seller-side or buyer-side M&A deliverables, compare agreement terms against a playbook, calculate economic exposure from term deviations, build structured deal-data JSON outputs, or work with the `<TASK_ENV_BASE_URL>` deal platform. Trigger even when the user does not explicitly name the workbench but describes M&A deal review, APA/SPA term analysis, or structured legal outputs tied to a deal ID and a playbook or policy.
- ▌ Manda Deal Review · prism-shadow bundleAnalyze M&A deal documents against playbooks, policies, and committee thresholds to produce structured issue registers, closing-readiness packages, deviation matrices, escalation memos, and transition reviews. Use this skill whenever the user is reviewing a purchase agreement (APA or SPA), preparing a deal-issues matrix, building a closing checklist, creating an M&A committee escalation memo, running a seller-side or buyer-side deal review, or comparing draft terms against playbook positions. This skill must be used even when the user describes the task in their own words without naming the skill. Trigger phrases include "review the buyer paper," "prepare a closing package," "escalation for the M&A committee," "seller issue register," "buyer deviation matrix," "carveout transition review," or any request that mentions a deal workbench, playbook rules, committee policy, or M&A term comparison.
- ▌ Asteria Fleet Dq Hub · prism-shadowUse this skill when the user needs to reconcile, audit, certify, or normalize data through the Asteria Fleet Data Quality Hub REST API. This skill covers fleet data domains (fuel, freight, maintenance, field-service roster, partner onboarding) where the task involves reading a collection catalog, resolving overlapping source snapshots, classifying records, producing canonical entity results, assigning opaque control codes, and making certification decisions. Use it whenever the user mentions Asteria, fleet data quality, data reconciliation, source-snapshot resolution, or any of the Asteria data domains even if they do not explicitly name the hub.
- ▌ Asteria Fleet Dq Hub 2 · prism-shadow bundleReconcile and certify fleet data-quality audits using the Asteria Fleet Data Quality Hub. Use this skill whenever the user mentions Asteria, Fleet Data Quality Hub, data reconciliation, fleet audits, cargo/fuel/freight/maintenance/contact/roster certification, partner onboarding, carrier accrual, fuel ledger, field-service roster, or any task that references an Asteria API with collections, snapshots, and an answer template. Even if the task is phrased generically, use this skill when the user points at a read-only API with catalog, schema, source-snapshots, and query endpoints.
- ▌ Asteria Dq Hub · prism-shadow bundleQuery and audit the Asteria Fleet Data Quality Hub API to reconcile multi-source fleet records, compute quality metrics, assign opaque control codes, and produce certification decisions. Use whenever the user mentions Asteria, fleet data quality, partner onboarding certification, fuel ledger audits, maintenance-log integrity, field-service roster readiness, freight-charge accrual reconciliation, or any task that references a Fleet Data Quality Hub, TASK_ENV_BASE_URL, or environment_access.md with Asteria API endpoints.
- ▌ Atlas Commerce Ops 6 · prism-shadow bundleSolve analytical tasks against the Atlas Commerce Operations database API. Use this skill whenever the user asks you to produce a business report, scorecard, reconciliation, operational health review, or data-quality correction using an Atlas Commerce Operations workplace service. Typical signals include references to a workplace API base URL, bearer token authorization, SQL endpoints, answer templates, or business domains like fulfillment, refund reconciliation, carrier quality, warehouse productivity, or support case health. Trigger even when the user describes the task in domain language without naming the API explicitly.
- ▌ Peopleops Console 2 · prism-shadow bundleNavigate and solve HR operations verification tasks using the PeopleOps Console REST API. Use when the user needs to verify employee onboarding closeout, review policy case folder and notice readiness, reconcile recruitment outcomes, validate leave source precedence, or inspect payroll assignment and accrual readiness — any task involving PeopleOps employee records, leave assignments, payroll, cases, recruitment, documents, messages, or audit evidence.
- ▌ Peopleops Console 3 · prism-shadowUse when the task involves the PeopleOps Console, Northwind People Lifecycle Portal, HRMS verification, employee lifecycle reconciliation, onboarding closeout, leave source precedence, payroll assignment auditing, recruitment reconciliation, policy case review, or any HR operations workflow that requires pulling evidence from REST API endpoints and applying business policies to reach a structured decision. This skill is essential whenever you see TASK_ENV_BASE_URL, ops.lead@peopleops.local, PeopleOps#2026, or JSON answer templates with enum-driven business labels. Do not try to solve these tasks by reasoning alone; the API is the single source of truth.
- ▌ Peopleops Console 4 · prism-shadow bundleSolve PeopleOps Console business-verification tasks. Use this skill whenever the user mentions PeopleOps, HR operations, employee onboarding, leave verification, payroll verification, lifecycle closeout, case folder review, formal notice inspection, recruitment reconciliation, candidate reconciliation, audit-based verification, or a `<TASK_ENV_BASE_URL>` with ops.lead@peopleops.local credentials. Also use it when a task references Northwind People entities, PeopleOps answer templates, or normalized business labels. Follow this skill even if the user does not explicitly name the PeopleOps Console.
- ▌ Cedar Ridge Intake 6 · prism-shadow bundleUse this skill whenever the user needs to work with the Cedar Ridge Intake Coordination Portal — a healthcare-intake REST API and read-only SQL endpoint covering patient registration verification, referral audits, dialysis transfer review, chronic-care enrollment panels, and pulmonary referral-to-chart activation. Trigger on references to Cedar Ridge, intake coordination, patient rosters, referral batches (ORTHO, PULM, etc.), dialysis transfers, chronic-care programs (DMHTN), or any task that mentions the Cedar Ridge portal, intake coordination, clinical intake auditing, or reconciling healthcare referral/transfer/program data against a live API.
- ▌ Cedar Ridge Intake 7 · prism-shadow bundleComplete Cedar Ridge Intake Coordination Portal intake workflows – new-patient access verification, referral batch audit, dialysis transfer review, chronic-care program enrollment, and referral-to-chart activation. Use whenever the user mentions Cedar Ridge, intake coordination, patient access verification, referral audit, transfer review, program enrollment, or chart activation in a healthcare portal context, or when a task references the (TASK_ENV_BASE_URL) placeholder or cedar ridge intake coordination portal.
- ▌ Cedar Ridge Intake 8 · prism-shadow bundleUse this skill whenever the user mentions Cedar Ridge, intake coordination, patient access verification, referral auditing or readiness, dialysis transfer review, chronic-care enrollment panels, chart activation, or any task that involves processing batches of patients through a healthcare intake portal. The skill covers the Cedar Ridge Intake Coordination Portal API, classification rules for patient registration, referral readiness, transfer packet review, program enrollment eligibility, and chart activation workflows. Trigger this even if the user only mentions a batch ID, roster ID, program code, or portal URL without explicitly naming Cedar Ridge.
- ▌ Northstar Ops · prism-shadow bundleSolve Northstar Health Plan payer-operations tasks that require querying a shared REST+SQL environment and returning structured JSON conforming to a supplied answer template. Use this skill whenever the prompt mentions Northstar Health Plan, payer operations, UM review, prior authorization, pharmacy appeals, payment integrity, claim repricing, peer-to-peer, margin queue analysis, or any task instructing you to use a shared payer-operations environment with a SQL endpoint and bearer token.
- ▌ Northstar Payer Operations 2 · prism-shadowUse when the task involves Northstar Health Plan payer operations — prior authorization, utilization management review, pharmacy appeals, payment integrity claim repricing, peer-to-peer clinical review, or UM-finance margin analysis. Always use this skill when the user references Northstar, a payer-operations environment, an authorization case, an appeal, a claim repricing, a P2P review, or a therapy margin queue, even when the domain terminology is partial or the task is framed as a JSON-structured determination, correction packet, or queue summary.
- ▌ Northstar Payer Ops 16 · prism-shadow bundleComplete structured authorization, appeals, claim-repricing, peer-to-peer, and margin-analysis tasks for Northstar Health Plan payer operations. Use when the task references the Northstar payer-operations environment, involves prior authorization cases, pharmacy appeals, payment integrity corrections, P2P summaries, or UM margin-queue analysis, requires the bearer token pa-review-token-014, uses SQL /sql/query or REST business endpoints, and asks for a structured JSON determination matching an answer template.
- ▌ Ehr Quality Governance 3 · prism-shadowBuild normalized EHR quality-governance JSON packets by querying a shared read-only FHIR-style REST API. Use this skill whenever the task involves duplicate-chart merge readiness, referral coordination, care-transition packets, quality-governance case review, or batch referral audits against an EHR environment. Trigger on mentions of EHR, FHIR, duplicate candidates, referral packets, care transitions, quality governance, clinical data reconciliation, ICD-10 validation, provider lookup, or answer_template.json with clinical/administrative keys.
- ▌ Ehr Quality Governance 4 · prism-shadow bundlePrepare normalized JSON quality-governance packets for EHR clinical review workflows. This skill covers EHR duplicate-chart merge readiness, referral coordination packets, care transition summaries, service-request quality validation, and referral audit batch processing. Use this skill whenever the user mentions EHR, electronic health records, duplicate patient merge, referral audit, clinical quality governance, care transitions, SBAR coverage, ICD-10 validation, HIM merge packets, orthopedic/cardiology/pulmonary referral coordination, or any structured clinical data reconciliation against a REST EHR API. Use it even when the user only hints at "duplicate chart review," "referral batch," "care transition packet," "merge readiness," or "quality-governance."
- ▌ Ehr Quality Governance 5 · prism-shadowUse this skill whenever the user asks you to prepare EHR quality-governance packets, merge-readiness assessments, referral coordination packets, care-transition summaries, duplicate-chart reviews, or referral batch audits against a FHIR-like read-only REST API. These tasks always involve fetching patient clinical data, reconciling active lists, validating ICD-10 codes, identifying identity signals, and building a single normalized JSON output that conforms strictly to a supplied answer template. Trigger this skill for any prompt that mentions duplicate-chart merge, referral coordination, care transition, quality governance, referral audit, or that references patients together with conditions, medications, allergies, encounters, documents, service-requests, duplicates, referrals, ICD-10, providers, or disclosures against a shared EHR API. Even if the user does not use the exact phrase "quality governance," trigger this skill when they describe a clinical-data reconciliation or packet-preparation workflow that
- ▌ Clinic Decision Support · prism-shadow bundleUse for synthetic-clinic decision-support tasks that require querying a FHIR-like REST API at TASK_ENV_BASE_URL and producing a structured JSON response conforming to a supplied answer_template.json. Always use this skill when the prompt mentions a synthetic clinic case ID (CASE-*), a clinic runtime environment, protocol-bound clinical assessments, order-entry decision support, care-management routing, or lab-observation window retrieval tasks. This skill is essential whenever the task combines a clinic API with a JSON answer template containing enum-constrained fields.
- ▌ Clinic Protocol Assessor · prism-shadow bundleUse when preparing structured clinical decision-support responses for synthetic clinic cases. Triggers on prompts mentioning clinic protocol assessments, clinical decision-support tasks, structured clinical responses, answer templates with enumerated fields, synthetic clinic cases, or tasks that require querying a clinic REST API runtime and returning a conformant JSON object. Use this whenever the prompt references a case ID, an answer template, a task environment base URL, or clinical protocol terminology — even if the user does not explicitly ask for a protocol assessment.
- ▌ Clinic Decision Support 2 · prism-shadowProtocol-bound clinical decision-support task. Use when solving a task that asks for a structured JSON response based on synthetic-clinic runtime data accessed via REST endpoints, including case/patient reviews, protocol assessments, lab-based decisions, care-management routing, or observation-window retrieval. Trigger whenever the prompt mentions a clinic runtime environment, an answer template, a case identifier, or structured clinical decision support with enumerated output fields.
- ▌ Investigation Review Hub 3 · prism-shadow bundleQuery an Investigation Review Hub REST API to produce structured JSON review dashboards for e-discovery, legal-hold gap analysis, privilege review, production readiness, and cross-system remediation. Use this skill whenever the task mentions an Investigation Review Hub, a matter-based subpoena or regulatory review, legal-hold gap analysis, production readiness review, privilege-log QC, retention-event tracking, or remediation dashboards tied to REST endpoints at a provided base URL. Trigger even when the user describes ediscovery workstreams, grand jury or SEC subpoena reviews, or asks for a structured JSON deliverable from review-hub endpoints.
- ▌ Northwind Erp Desk 2 · prism-shadowSolve Northwind Components desk-operation tasks that arrive with a memo (JSON or markdown), a JSON answer template, and a shared REST ERP API at a runner-supplied base URL. Use this skill whenever the user mentions dispatching orders, replenishment planning, supplier scorecards or quality reviews, allocation transfers, procurement holds, or any Northwind desk decision that needs live ERP record lookups and structured JSON output. Also trigger when the task includes a file named answer_template.json alongside an order-memo or request payload, or when the prompt references an ERP API base URL with endpoints like /orders, /inventory, /products, /suppliers, /incidents, or /boms.