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.
orchestrate customer success work across post-sale handoff, onboarding and time to value, adoption and enablement, usage analysis, health scoring, success planning, stakeholder mapping, playbook design, escalation management, churn risk and save plays, value…
run the escalation record from the customer raised-at timestamp that starts every committed clock, with business impact in the customer's own words, severity assessed on customer impact rather than internal effort, named internal owner and executive sponsor…
map whitespace across products business units and geographies with what is already entitled separated from what is not, build expansion hypotheses each traced to a specific usage stakeholder or stated-need signal, qualify readiness against undelivered…
report a customer health score with its model version as-of date and band, break out every component with its input value input age weight and contribution rather than only the total, name stale inputs individually, record manual overrides with the person…
build the implementation and onboarding plan with milestones owners and dependencies on both sides, run kickoff and go-live against contractual commitments separated from working targets, own provisioning integration data migration and security review…
design the customer success play library with triggers stated as an evaluable signal and threshold, entry and exit criteria including the failure exit, segment and motion applicability, delivery surface across one to one one to many in-app and lifecycle…
reconcile the executed order form against what the deal narrative promised at closed-won handoff, covering entitlement and term facts read from the contract, the commitment register of sales-cycle promises with who made them and to whom, the buying group as…
prepare and follow up quarterly and executive business reviews built on validated value rather than product activity, with honest treatment of missed commitments and open escalations, roadmap content at the commitment level the company can stand behind, the…
build the renewal timeline backward from the contractual non-renewal notice deadline through the customer's budget and procurement cycle, set the forecast category with the evidence behind it and the reason for any change, prepare the uplift and concession…
report net revenue retention gross revenue retention and logo retention with the computed basis the cohort population and every exclusion stated, hold logo retention separate from revenue retention, measure forecast accuracy against what was actually…
build the recovery plan for an at-risk account matched to the root cause rather than the symptom, with the concession stated at its value with a named approver and authority level, executive engagement designed around a decision, checkpoints testing…
define customer segments and tiers with the criteria that place an account in each, assign the touch model across high touch low touch pooled digital and partner led, compute coverage ratios and csm capacity against what the motion actually requires, name…
map the buying and using centers on an account with economic buyer champion executive sponsor administrator power users detractors procurement and security reviewers each identified or named unidentified, with influence on the renewal decision, disposition…
define desired business outcomes in the customer's own metrics, capture baselines before the change with the method and date behind each, set targets and success criteria stated as what must be observably true, and build the mutual action plan with owners and…
read product telemetry into entitled against provisioned against active as three separate numbers with the active definition and measurement window stated, compute consumption against entitlement with underuse and overage both named, detect decline with the…
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…