Results for “trigger”

Maps the end-to-end customer experience from awareness to advocacy — touchpoints, emotions, friction points, and improvement opportunities per stage. Use when identifying drop-off points, improving onboarding, or understanding the full user lifecycle. Triggers on: customer journey, user journey, journey map, touchpoints, onboarding experience, funnel analysis, churn points, aha moment, drop-off, user lifecycle.

Guides DPIA for biometric processing systems including facial recognition, fingerprint, voice, iris, and gait analysis. Covers Art. 9 special category requirements, Art. 35(3)(b) mandatory DPIA triggers for large-scale biometric processing, and EDPB Guidelines 3/2019 on video surveillance. Keywords: biometric, facial recognition, fingerprint, DPIA, Art. 9, special category, EDPB Guidelines 3/2019.

Programmatically author RoadRunner scenarios from MATLAB using roadrunnerAPI. Use when adding actors, creating routes, building scenario logic (phases, conditions, actions), placing vehicles/pedestrians, defining cut-in/crossing/ follow scenarios, or any programmatic scenario creation in RoadRunner. Triggers on: roadrunnerAPI, scenario authoring, add actor, create route, phase logic, cut-in scenario, pedestrian crossing, scenario from MATLAB.

Recommends using weight‑neutral antipsychotic alternatives when possible and employing shared decision‑making that provides quantitative estimates of expected weight effect to guide drug choice. Triggered when a clinician asks, “How do I involve this patient in choosing an antipsychotic with minimal weight gain?” or “What resources show weight‑change projections for risperidone vs aripiprazole?”.

Drafts ASTM E1527-21 environmental site assessment reports under 40 CFR Part 312. Classifies RECs, CRECs, and HRECs to establish all appropriate inquiries for CERCLA liability protection. Trigger when the user requests a Phase I ESA, environmental site assessment, recognized environmental conditions analysis, ASTM E1527 compliance, or environmental due diligence for property transactions or lending.

Manage your Lidarr music library from the terminal. Search and browse artists and albums, add new artists, check calendars, view queue and download history, inspect quality and metadata profiles, and trigger searches. Use when the user mentions Lidarr, music management, adding an artist, searching for music, checking the music library, upcoming album releases, or download queue.

Detect and evaluate arbitrage opportunities across sportsbooks and prediction markets. Calculate guaranteed-profit scenarios, middle bets, and cross-platform price discrepancies. Use when comparing odds across books, calculating arb percentages, evaluating middle opportunities, or building odds-comparison workflows. Also trigger for 'arb bet', 'sure bet', 'arbitrage', 'odds comparison', 'middle bet', 'risk-free bet', or 'line shopping'.

Speed up local parfor, parfeval, or spmd by switching to a thread-based parallel pool. Trigger when a user describes slow or disappointing local parallel performance, even if they don't mention threads. Symptoms: parfor on a laptop/workstation is slower than expected or "only slightly faster than for"; parfor scales poorly with the number of workers; ticBytes/tocBytes, the Parallel Pool dashboard, mpiprofile, or system tools show large per-worker data transfer; large broadcast variables or sliced inputs make iterations slow; opening a process pool dominates a short workload; user mentions serialisation or data transfer overhead. Also trigger on any question about whether code or a function works on a thread pool. For non-pool MATLAB performance work (vectorisation, preallocation, profiling), defer to matlab-optimize-performance.

Use when the user wants more human-like AI responses — less robotic, less listy, more authentic. Triggers: 'behuman', 'be real', 'like a human', 'more human', 'less AI', 'talk like a person', 'mirror mode', 'stop being so AI', or when conversations are emotionally charged (grief, job loss, relationship advice, fear). NOT for technical questions, code generation, or factual lookups.

Interprets the saline infusion test (SIT) to assess the probability of primary aldosteronism when a patient has a positive aldosterone-to-renin ratio (ARR) and requires confirmatory testing. Triggers include evaluating post‑infusion plasma aldosterone concentration (PAC) after a positive ARR, hypertension work‑up, or when deciding whether to proceed to adrenal venous sampling (AVS).

Recommends weight‑losing and weight‑neutral medications as first‑ and second‑line agents for managing overweight/obese patients with type 2 diabetes. Triggers include when a clinician asks, 'Which diabetes medications will not worsen weight in this obese patient?' or 'Should I avoid sulfonylureas in this patient with T2DM and obesity due to weight gain risk?'

Use to find the causes behind a complaint population and track whether remediation actually stopped them recurring. Trigger for "root cause analysis on our complaints", "why do we keep getting the same complaints", "complaint themes and remediation", recurring complaint categories, complaint reduction programmes, or a remediation that was signed off and did not work.

Use to compare BPO sites, vendors or partner teams fairly, adjusting for the work mix each is given before concluding anything about performance. Trigger for "compare our BPO sites", "which vendor is performing best", "site A scores lower than site B", outsourcer QBR packs, partner MI reporting, or setting contractual quality targets with a vendor.

Use to find personal data support collects and stores that nothing actually uses, and to stop collecting it. Trigger for "do we collect too much data", "which fields do we actually use", data minimisation review, "why do we ask customers for this", reducing breach exposure, or a form that grew a field every quarter.

Use to staff and schedule QA reviewers for sustainable throughput without grading quality collapsing — fatigue, drift, and false precision from treating reviewers like production agents. Trigger for "how many QA reviewers do we need", reviewer capacity planning, grader fatigue, throughput per reviewer, calibration after long shifts, or scores drifting over the course of a day.

Use for writing, reviewing, debugging, testing, or validating Python mpmath arbitrary-precision numerical code. Trigger on mpf, mpc, mp.dps, workdps, interval arithmetic, high-precision quadrature, root finding, special functions, matrices, inverse transforms, or precision/convergence failures. Do not use for ordinary NumPy vectorization, SymPy symbolic manipulation, decimal currency arithmetic, or machine-float code with no precision requirement.

Detect and validate GPU availability for MATLAB GPU computing. Use when the user can't use their GPU, or is setting up or selecting a GPU. Triggers on: gpuDevice, GPU setup, check GPU, GPU not found, GPU not working, can't use GPU, GPU not available, unable to find a supported GPU device, compatible GPU, canUseGPU, validateGPU.

Use to design or fix a customer support survey — CSAT, NPS, or CES — and to diagnose response bias. Trigger for "design a CSAT survey", "our CSAT doesn't match reality", "should we use NPS", survey response rate, non-response bias, survey timing or scale choice, comparing satisfaction across teams or channels, or interpreting a satisfaction trend.

Use to quantify what support quality failures cost — rework, credits, escalation handling, complaints and churn — with the causal limits stated. Trigger for "what do our quality failures cost", "cost of rework in support", "business case for improving quality", "how much is bad support costing us", or a quality investment that needs a number attached.

Use to define handoff standards for support transfers and to measure whether context survives the handoff — cold vs warm, required fields, and re-ask rate after transfer. Trigger for "transfer protocol", "warm handoff", "customers repeat themselves after transfer", "ping-pong between teams", "what should agents include when transferring", handoff quality, or re-ask rate after escalation.

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

This skill guides clinicians in sharing decision‑making when selecting an antiepileptic drug (AED) by providing quantitative estimates of each drug’s expected weight effect. It is triggered when a clinician asks how to discuss weight‑change risks when choosing an AED or what information to provide on weight effects of specific agents such as valproate versus lamotrigine.

Use to design support queues and the skill taxonomy routing rules depend on — not as an org chart mirror, but as staffable combinations of skill, priority and channel. Trigger for "how should we structure our queues", "too many queues", "queue design", "routing taxonomy", "catch-all queue growing", overflow rules, or redesigning queue structure before changing routing rules.

Use to extract competitor mentions, switching language and feature-gap evidence from support conversations as an input to win/loss and product strategy. Trigger for "what competitors do customers mention", "why do customers switch away", "find feature gaps customers ask about", competitive intelligence from support, or win/loss analysis that only samples deals sales remembers.

Use to fulfil a subject access request from support data — finding everything about the person, and deciding what must be redacted before disclosure. Trigger for "handle this SAR", "subject access request", "customer wants all their data", DSAR fulfilment from support systems, "a customer asked for their call recordings", or an employee requesting their own QA records.

Use to monitor support conversations for conduct risk — pressure, mis-selling, unfair outcomes, obstruction and misleading statements — as distinct from whether the answer matched policy. Trigger for "monitor for mis-selling", "conduct risk in our support conversations", "are agents pressuring customers", "customers being obstructed from cancelling", conduct surveillance, or a conduct finding raised by second line.

Use to clean up sprawling helpdesk tags, categories and custom fields so reporting built on them means something. Trigger for "our tags are a mess", "consolidate our ticket categories", "why don't our tag reports add up", duplicate or near-duplicate tags, tags nobody uses, agents tagging inconsistently, or before building reporting on top of tags.

Configures autonomous heartbeat and cron-based proactive routines (e.g., morning briefing setup, unanswered-message scan cadence). Invoke when user is SETTING UP or MODIFYING a proactive routine, not when the routine itself fires. Cron crons execute their own logic — they do NOT load this skill. Triggers: "set up proactive check", "configure heartbeat", "add morning briefing", "tune cron cadence".

Multi-phase dialectical stress-test for HIGH-STAKES decisions only (architecture choices, irreversible product calls, strategic bets). Heavy-cost skill — do NOT use for routine questions, brainstorming, or simple tradeoffs. User must explicitly invoke or describe a decision they call "high-stakes", "irreversible", or "needs stress-testing". Triggers: "stress test this decision", "dialectic on", "challenge this thesis", "should I really".

Multi-perspective dialectical reasoning with cross-evaluative synthesis. Spawns parallel evaluative lenses (STRUCTURAL, EVIDENTIAL, SCOPE, ADVERSARIAL, PRAGMATIC) that critique thesis AND critique each other's critiques, producing N-squared evaluation matrix before recursive aggregation. Triggers on /critique, /dialectic, /crosseval, requests for thorough analysis, stress-testing arguments, or finding weaknesses. Implements Hegelian refinement enhanced with interleaved multi-domain evaluation and convergent synthesis.

Use this skill when the user asks about Americans with Disabilities Act (ADA) accommodation for CDL drivers — interaction between ADA + FMCSA medical certification, when DOT-disqualifying conditions trigger ADA analysis, reasonable accommodation case examples, employer obligations, and how to handle a driver with a condition that may affect CDL status. Cite Title I ADA + 49 CFR 391.41.

Use to find the activation blockers visible in support contacts from new customers, before they show up in retention numbers months later. Trigger for "why aren't new customers activating", "what do new customers contact us about", onboarding drop-off, time-to-value analysis, first-90-days support experience, or a retention problem that traces back to activation.

Enforces strict outside-in red-green-refactor TDD with one-failure-per-turn discipline, predicting failures before every run, hardcoding minimum changes, and using triangulation and property-based testing. Triggers on explicit TDD requests and tasks phrased as 'implement', 'add', 'write a function', 'build a feature'.

Tend the Allium garden. Use when the user wants to write, edit, update, add to, improve, clarify, refine, restructure, fix or migrate Allium specs. Covers adding entities, rules, triggers, surfaces and contracts, fixing syntax or validation errors, renaming or refactoring within specs, migrating specs to a new language version, and translating requirements into well-formed specifications. Pushes back on vague requirements.

Use Angular CLI and development tools effectively in Angular v20+ projects. Use for project setup, code generation, building, testing, and configuration. Triggers on creating new projects, generating components/services/modules, configuring builds, running tests, or optimizing production builds. Don't use for Nx workspace commands, custom Webpack configurations, or non-Angular CLI build systems like Vite standalone or esbuild direct usage.

Socratic coach for breaking down problems to fundamental truths. Use when users want to think through a problem deeply, challenge assumptions, or find innovative solutions. Triggers on requests like "help me think through this", "let's break this down", "what are my blind spots", "I'm stuck on a problem", "challenge my assumptions", or explicit requests for first-principles thinking.