mit einem Klick
GDPevo
GDPevo enthält 166 gesammelte Skills von Prism-Shadow, mit Repository-Berufsabdeckung und Skill-Detailseiten auf SkillsMP.
Skills in diesem Repository
Reconcile MedBridge Sales Ops CRM tasks (B2B medical wholesale + implementation-services) against the remote Sales Ops API and emit the account-ready JSON answer. Covers QUOTE decision packages (EXW pricing, freight options, route risk, recommended mode, payment terms) and milestone RECONCILIATION packages (invoice/payment state, outstanding balance, revenue-recognition coverage, CRM follow-up routing, event/voucher linkage). Use whenever a task references MedBridge, quotes like Q-TR-*, RFQ-TR-*, opportunities like OPP-TR-*, milestones MS1/MS2/MS3, freight-quotes, revenue-journals, or the shared Sales Ops API base URL.
SCN_003 CRM support-operations solver. Resolve ticket batches (fixed-line diagnostics + gates), mobile contact-center triage, and enterprise export-complaint response packages against the shared support-console API. Apply exact metric thresholds, gate order, root-cause->team map, mobile action decision tree, and enterprise package derivation rules.
SCN_003 CRM support-console analyst. Resolve same-day ticket batches, mobile triage queues, mobile-data recovery worklists, and enterprise export-complaint response packages by querying the shared support-console API and applying fixed diagnostic thresholds, gating order, root-cause routing, and per-family decision trees.
Resolve CRM support-console tasks (SCN_003) — ticket-batch classification, mobile-data triage, and enterprise export-complaint response packages — against a remote support-console API. Use when a task asks to classify service tickets / queue snapshots, triage mobile data cases, or build an enterprise export-failure response package and references a support console API.
Resolve SCN_003 CRM support-console tasks: ticket-batch resolution, mobile contact-center triage, and enterprise export-complaint response packages. Drive the remote console API, apply diagnostic floors + gating order, and emit the per-family JSON answer.
Solve ApexCloud Retention Operations analytics tasks against the remote Retention Operations API. Encode and reproduce the exact business rules, data-hygiene conventions, policy codes, ranking/precision rules, churn-model spec, and per-archetype output schemas. Use for any CRM retention task (renewal risk queue / save plan, QBR metrics packet, receivables + pipeline operations digest, churn model validation + outreach ranking, high-touch retention action board / watchlist).
ApexCloud Retention Operations — reusable rules and verified conventions for producing renewal-risk, QBR, receivables/pipeline, churn-model, and retention-board answers from the data API.
Solve private-wealth-advisory structured planning tasks (Roth/RMD, ILIT/Crummey, GRAT/CRAT, estate-liquidity) against a remote advisory API with conflicting source documents. Produce exact JSON conforming to each task's answer template.
Verify People Ops employee-lifecycle closeouts (leave/payroll precedence, folder readiness, formal-notice quality, audit-scope selection, recruitment reconciliation) against the remote Northwind PeopleOps Console read-only JSON API. Use whenever a task asks to validate/audit/reconcile an onboarding closeout, leave source precedence, payroll assignment readiness, policy-case folder+notice, or recruitment outcome packet.
Solve PeopleOps employee-lifecycle clearance / audit / reconciliation tasks against the read-only Northwind People Lifecycle Portal JSON API. Use when a task asks to verify onboarding closeout, leave source precedence, payroll/accrual readiness, case folder + formal-notice quality, or recruitment reconciliation, and return a normalized JSON answer.
Solve HR employee-lifecycle clearance/audit tasks against the remote Northwind PeopleOps read-only JSON API. Use when a task asks you to inspect leave assignments, payroll/accrual readiness, policy-case folder+notice defects, recruitment handoff, or audit closeout, and return a structured JSON answer.
End-to-end SOP for HarborCRM front-of-funnel tasks — event sponsor/lead handoff, trade-show prospecting, and raw contact-import hygiene — producing exact answer-template JSON from the read-only HarborCRM data API.
End-to-end SOP for HarborCRM front-of-funnel CRM-marketing tasks — event sponsor/post-event handoff reconciliation, trade-show prospecting, and raw contact-import hygiene — over the read-only HarborCRM data API.
End-to-end SOP for HarborCRM front-of-funnel CRM marketing tasks — post-event sponsor/lead handoff reconciliation, trade-show OEM/robotics prospecting with ranking & tiering, and raw contact-import hygiene — producing strict JSON that matches the per-task answer_template.
SOP for HarborCRM front-of-funnel CRM tasks — event sponsor handoff/reconciliation, trade-show prospecting qualification & ranking, and raw-contact import hygiene — driven entirely from the read-only HarborCRM data API.
SOP for HarborCRM front-of-funnel tasks — post-event sponsor/lead handoff, trade-show prospecting, and raw-contact import hygiene — using the read-only HarborCRM data API.
SOP for HarborCRM front-of-funnel tasks — event sponsor-handoff reconciliation, trade-show exhibitor prospecting, and raw contact-import hygiene — using the read-only HarborCRM data API to produce strict JSON answers.
SOP for ProcureOps ERP procurement/receiving/AP tasks — pull records from the read-only API as source of truth, apply sourcing/receiving/three-way-match/AP-release rules, and emit answer.json that exactly matches the task template.
SOP for ProcureOps ERP procurement/receiving/AP tasks — pull truth from the remote API, apply three-way-match / hold / chargeback rules, and emit JSON that exactly matches the answer template.
SOP and business rules for solving ProcureOps ERP procurement/receiving/AP tasks against the read-only API, emitting answer.json that exactly matches each task template.
SOPs and business rules for solving ProcureOps procurement/receiving/AP tasks (nomination gates, three-way match, AP hold/release, chargeback netting) against the live read-only ERP API.
SOP for ProcureOps ERP procure-to-pay tasks (sourcing nomination, receiving control, three-way match, AP hold/release, chargeback netting, contract/budget headroom) using the read-only API as source of truth.
SOP and business rules for solving ProcureOps ERP procurement/receiving/AP tasks (nomination, three-way match, AP hold/release, change control) using the live read-only API as source of truth.
Solve private-wealth advisory structured-JSON planning tasks served by the prismshadow advisory API: (a) Roth conversion / RMD tax summaries (analysis_type roth_conversion_rmd), (b) ILIT Crummey funding cycles (ilit_crummey_implementation), (c) GRAT vs CRAT comparisons (trust_comparison), and (d) integrated estate-liquidity action plans (estate_liquidity_action_plan). Use when a task asks for one structured JSON object conforming to an answer_template.json for a client CLT-xxxx, sourcing all data from the read-only HTTP advisory API. Contains the verified formulas, conflict-resolution priority, exact output schema/enums, rounding/date conventions, and pitfalls.
Produce structured JSON planning outputs for a private-wealth advisory API covering four analysis types: Roth conversion / RMD tax (roth_conversion_rmd), ILIT Crummey funding (ilit_crummey_implementation), GRAT-vs-CRAT comparison (trust_comparison), and integrated estate-liquidity action plans (estate_liquidity_action_plan). Use when a task asks for one of these analyses for a client (e.g. CLT-xxxx / test_xxx), gives a request memo plus an answer_template.json, and points to a read-only HTTP advisory API. Covers the SOP, every endpoint, conflicting-source resolution, exact enums/schema, the verified formulas, rounding, and ISO-date conventions.
Solve private-wealth advisory planning tasks that require querying a remote advisory HTTP API and returning ONE strict JSON object. Covers four analysis_types: roth_conversion_rmd (Roth conversion / RMD tax), ilit_crummey_implementation (ILIT Crummey funding), trust_comparison (GRAT vs CRAT), and estate_liquidity_action_plan (integrated estate liquidity). Use when a task names a client (CLT-####), gives an answer_template.json with one of those analysis_types, and provides an advisory API base URL. Contains the field-resolution priority, the exact derived formulas, enum values, and rounding/date conventions.
Solve private-wealth advisory planning tasks (Roth conversion / RMD tax, ILIT Crummey funding, GRAT-vs-CRAT comparison, integrated estate-liquidity action plans) by pulling client data from the remote advisory API, resolving conflicting source documents by a fixed priority, running the derived per-analysis formulas, and emitting a single JSON object that conforms to the task's answer_template.json. Use whenever a prompt says "private wealth advisory team" and references a CLT-#### client plus one of those four engagements.
Solve private-wealth advisory planning tasks (Roth conversion / RMD tax, ILIT Crummey funding, GRAT-vs-CRAT comparison, integrated estate-liquidity action plans) by querying a read-only advisory HTTP API, resolving conflicting source documents by a fixed priority, and emitting a single strict JSON object that conforms to the task's answer_template. Use this whenever the prompt says "private wealth advisory team", references a client like CLT-####, and an answer_template.json defines analysis_type one of roth_conversion_rmd, ilit_crummey_implementation, trust_comparison, or estate_liquidity_action_plan.
Solve private wealth advisory structured-output tasks (Roth conversion / RMD tax, ILIT Crummey funding, GRAT vs CRAT comparison, and integrated estate-liquidity action plans) by querying a read-only advisory HTTP API, resolving conflicting source documents by priority, applying the derived business formulas, and emitting a single JSON object that conforms to the task's answer_template.json. Use this whenever a task asks for a structured planning output for a client CLT-#### in the private-wealth domain.
SOP for Crescent Finance Ops branch reporting, CBA compensation forecasting, and theatre payroll control tasks against the remote Finance Ops API.
SOP for Crescent Finance Ops branch reporting, CBA compensation forecasting, and theatre payroll control tasks against the remote Finance Ops API.
SOP for Crescent Finance Ops branch reporting, CBA compensation forecasting, and theatre payroll control tasks against the remote Finance Ops API.
SOP for Crescent Finance Ops branch reporting, CBA compensation forecasting, and theatre payroll control tasks against the remote Finance Ops API.
SOP for Crescent Finance Ops branch reporting, CBA compensation forecasting, and theatre payroll control tasks against the remote Finance Ops API.
SOP for Crescent Finance Ops branch reporting, CBA compensation forecasting, and theatre payroll control tasks against the remote Finance Ops API.
Produce the Asteria Investment Office portfolio JSON deliverables (energy-credit trade packages, international equity correlation reviews, active allocation refreshes, fixed-income risk rebalances, and multi-asset committee decisions). Treat the shared Asteria HTTP environment as the authoritative book of record over any local payload, apply the documented policy thresholds, and emit answers that exactly match each task's answer_template (field names, enum value sets, rounding, id ordering). Use this whenever a prompt references Asteria portfolios (PF-*), bonds (BND_*), issuers (ISS_*), indices (IDX_*), opportunity sets, macro signals, or allocation policy.
Produce committee-grade JSON answers for the Asteria Investment Office across five portfolio archetypes — (a) energy-credit trade packages, (b) international equity correlation reviews, (c) active allocation-view refreshes, (d) fixed-income risk rebalances, and (e) multi-asset committee decisions. Covers the exact endpoints to pull, the deterministic computation recipes (Pearson correlation on monthly simple returns, notional-weighted modified duration and YTM, HY allocation %, carry, concentration), the policy thresholds that drive views/conviction/constraint checks, and the output-schema conventions (field names, enum sets, rounding, id ordering) that the desk's answer templates require. Use whenever a task references an Asteria portfolio (PF-*), index (IDX_*), bond (BND_*), issuer (ISS_*), policy (POL_*), or an answer_template.json.
Produce committee-grade JSON for the Asteria Investment Office across five task archetypes: (a) energy-credit trade packages, (b) international equity correlation reviews, (c) active allocation view refreshes, (d) fixed-income risk rebalances, and (e) multi-asset committee decisions. Pulls every fact from the shared Asteria HTTP environment (the book of record), runs the exact quantitative recipes (Pearson correlation, weighted duration/YTM, HY %, view mapping), applies the policy thresholds and exclusion rules, and emits output that conforms exactly to the task's answer_template (field names, enum value sets, rounding, id ordering).
Repeatable workflow for answering Asteria Investment Office (PF-*) portfolio tasks against the shared HTTP environment (<remote-env-url>). Covers five archetypes: (a) energy-credit trade-package selection, (b) international equity correlation review, (c) active allocation view refresh, (d) fixed-income risk rebalance, (e) multi-asset committee decision. Tells you which endpoints to call, the exact math, the policy thresholds, and the output schema conventions (field names, enum sets, rounding, id ordering). Use whenever the prompt names an Asteria portfolio id, an allocation/correlation/credit memo, or asks for JSON matching an answer_template.
Repeatable workflow for the Asteria Investment Office desk JSON tasks. Covers five archetypes: (a) energy-credit trade-package selection, (b) international equity correlation review, (c) active allocation view refresh, (d) fixed-income risk rebalance, (e) multi-asset committee decision. Explains which HTTP endpoints to call, the exact computation recipes (Pearson correlation from monthly simple returns, weighted modified duration, HY allocation %, weighted YTM, issuer concentration %), the policy thresholds to apply, and the precise output-schema conventions (field names, enum value sets, rounding precision, id ordering). Treats the shared environment as the book of record and reconciles stale local payloads against it.