Menu
Skills in this repository
SkillsMP has collected 1,540 skills from MadewellRD/skills-lab. Open a skill to review its source and details.
MadewellRD/skills-labShowing 40 of 1,540 collected skills.
measure delivered customer value per outcome with the baseline and current value stated alongside the measurement method behind each, the attribution basis crediting the change to this product, monetization only where the customer accepts the conversion, and…
turn survey and interview evidence into decisions by stating each finding with its instrument population response count response rate and window, coding verbatims into themes counted by accounts and arr rather than by mentions, naming sampling bias where the…
analyze what is generating support demand by producing a ranked contact driver list with volume, window, and trend against a comparison period, contacts per active account so growth is not read as regression, the underlying cause separated from the reason…
orchestrate customer support work across ticket intake and entitlement checks, triage and routing, severity and sla clocks, troubleshooting and diagnosis, reproduction and bug intake, engineering escalation, macro and response quality, resolution and closure,…
take a support symptom to a cause by carrying hypotheses with the observation that would confirm or eliminate each, building an evidence inventory from logs, traces, har captures, configuration exports, and diagnostic bundles with collection times and…
run the handoff out of support into tier 3 and engineering by naming the escalation criterion actually met rather than the pressure that prompted it, assembling the package the receiving engineer needs so nothing is rediscovered, deciding on-call engagement…
run the customer-facing side of a mass event by establishing affected scope from system evidence with an explicit statement of what is not affected, recording the impact start timestamp every credit and outage letter runs from, publishing one holding position…
record first touch on an inbound support contact with the arrival timestamp on the customer's side of the channel that starts every sla clock, requester authorization and named-contact status before any account data is disclosed, entitlement and coverage…
author and govern help center and internal knowledge base articles captured from resolved contacts, scoped to the product versions and editions they are true for, with steps verified against a stated build, titles and search terms written in the customer's…
draft what the customer actually reads, with every factual claim traced to a source and every commitment carrying a date and an owner, and audit the macro, canned response, and saved reply library for staleness, duplication, contradiction after a release,…
close out what an outage left behind, covering per-account follow-up positions, reason-for-outage letters bounded by what the incident record establishes, contractual service credits and the claim window, tickets raised during the event, and commitments made…
review support interaction quality against a scorecard with every score tied to quoted ticket evidence, a sampling plan stating the population, the selection method, and what the sample size can actually support, calibration sessions with reviewer variance…
read the shape of a support queue by reporting backlog in age cohorts with untouched, pending-customer, and pending-engineering states held apart, inflow against outflow, at-risk and breached counts with credit exposure, reopen rate against its definition in…
turn a customer report into a reproduction record and a defect draft engineering can act on, with minimal steps a stranger can follow, the build edition and configuration matrix actually exercised, expected against actual behavior, frequency and intermittency…
decide how a ticket ends, with the resolution code from the scheme in force, the fix type separating a real fix from a workaround from a configuration change from expected behavior from not reproduced, customer confirmation before closure above the threshold,…
assess self-service coverage against ranked contact drivers across the help center, in-product help, community, and automated answering, analyze search failures and zero-result queries, state containment and deflection with the exact denominator and how…
set support severity from customer impact and run every sla clock against the executed agreement, computing first response, next update, restoration, and resolution targets on the contractual calendar and timezone, pausing only under the written pause rule,…
report support numbers that leave the team, with every metric carrying its written definition, its population, its exclusions, its window, and its source system, satisfaction reported with response counts and response rates, response and resolution times…
specify and control helpdesk configuration changes across ticket fields, forms, views, triggers, automations, routing and assignment rules, sla policies, macros, and integrations, with the blast radius stated including tickets already open, interaction…
route and order support tickets by naming the queue, tier, and skill each contact requires, setting priority from the ordering rule in force and keeping it distinct from contractual severity, identifying spam, duplicates, machine-generated tickets, and…
model support volume against people, covering interval-level contact forecasts, staffing requirements against a stated service target, shrinkage and occupancy with what each includes, coverage gaps by interval, language, skill, and product rather than a…
design the analytics consumption layer covering certified datasets and dashboards per persona, self-serve boundaries and the joins that produce wrong numbers, fan-out and grain-breaking query anti-patterns, dashboard hygiene with duplicates and orphans,…
design pipeline scheduling and the dag, covering data aware triggering that waits for data rather than for a clock, sensors and arrival timeouts, retry policy and non retryable failure classes, concurrency pools and queueing at peak, sla miss conditions and…
orchestrate data engineering and analytics workflows across data modeling, star schemas and slowly changing dimensions, etl and elt pipelines, cdc ingestion, streaming, batch orchestration, sql transformation layers, warehouse and lakehouse design, data…
define producer and consumer data contracts and schema evolution rules, covering field set types and nullability, the semantics a schema cannot carry such as units timezone currency null meaning and enum meaning, compatibility mode and the enforcement point…
design data classification and access control covering pii phi and pci classification of physical columns, roles groups and actual grants, row-level security predicates, column masking and tokenization, enforcement points, purpose limitation per audience,…
respond to bad data in production covering severity by consumer exposure rather than row count, containment that pauses dependents and holds exports, evidence capture before any re-run, lineage-derived blast radius including external recipients, the backfill…
plan data platform migration covering scope and what is deliberately retired rather than carried, dual-run design, parity reconciliation across row counts control totals and metric values with a stated tolerance, historical backfill depth, consumer cutover…
design conceptual logical and physical data models with a declared grain per fact, transaction periodic snapshot and accumulating snapshot fact types, conformed dimensions and the bus matrix, slowly changing dimension type per attribute with effective dating,…
design data observability monitors and alert routing covering freshness sla, row volume anomaly, schema drift detection, distribution and null rate drift, job failure, consumer lag, lineage-aware alert grouping and suppression, detection coverage, alert noise…
analyze data platform spend covering the compute storage and transfer breakdown from the billing export, top cost drivers named as specific queries pipelines and dashboards, spend attribution and the unattributable share, efficiency findings across partition…
define a data product as the decision it serves, naming consumers and external recipients, output port, accountable owner, criticality tier, regulatory or contractual use, and agreed freshness completeness and accuracy targets, plus the tables dashboards and…
design data quality tests and validation, writing out the actual assertions for freshness, volume, uniqueness at the declared grain, not null, referential integrity, accepted values, distribution drift and business rules, deriving thresholds from history or…
design data retention and erasure covering retention schedules with their regulatory contractual or operational basis, deletion mechanisms that actually remove data given table format snapshots time travel and backups, the propagation map of every derived…
design batch and change data capture ingestion, covering extraction pattern and watermark selection, snapshot plus stream stitching at a consistent log position, delete propagation, idempotency and deduplication keys, raw record preservation for replay,…
build data lineage and metadata covering column-level and table-level lineage from sql parsing, orchestrator metadata and query history, upstream and downstream impact analysis, blast radius, catalog registration and stewardship, business glossary mapping,…
define metrics and the semantic layer covering metric expressions with filters exclusions and denominators, entity dimension and measure modeling, grain validity, additive semi-additive and non-additive aggregation, distinct counts that do not roll up, time…
profile source systems before extraction, establishing record grain, candidate and actual primary keys, uniqueness violations, null rates, cardinality, value ranges, encoding and type surprises, arrival cadence and lateness, hard versus soft delete behavior,…
design streaming data pipelines covering event time versus processing time, partition keys and the ordering they buy, tumbling hopping sliding and session windows, watermarks and allowed lateness, delivery semantics as the consumer observes them, state store…
design the layered sql transformation stack from staging through intermediate to marts, covering materialization and incremental strategy with merge keys and lookback windows, deduplication and record selection, slowly changing dimension implementation with…