メニュー
このリポジトリの skills
SkillsMP は MadewellRD/skills-lab から 1,540 件の skill を収集しています。skill を開くとソースと詳細を確認できます。
MadewellRD/skills-lab収集済み skill 1,540 件中 40 件を表示しています。
design hybrid connectivity and dns, covering dedicated circuits and encrypted tunnels with genuinely diverse redundant paths, bgp route exchange and failover behavior including degraded-bandwidth backup, on-premises address overlap resolution, dns zone…
原文の言語: 英語
design infrastructure as code repository and stack layout including state boundaries and blast radius, module interfaces and semantic versioning, remote state backend location with locking and encryption and read access, provider and dependency version…
原文の言語: 英語
design the cloud organization hierarchy and account structure, covering organizational units folders and management groups, account subscription and project separation by environment and sensitivity, account vending and the day-one baseline,…
原文の言語: 英語
design managed database platforms, covering engine and service selection against the access pattern, instance sizing and storage configuration, high-availability topology across failure domains, read replica placement and replication lag, backup and…
原文の言語: 英語
design the infrastructure provisioning pipeline including plan generation and the plan review gate, policy-as-code evaluation against the machine-readable plan, the approval matrix keyed to blast radius, a least-privileged federated apply identity per…
原文の言語: 英語
design cloud resilience and multi-region architecture, covering the failure domain model across zones regions and provider control planes, failover mode selection and what each mode costs to run, replication topology and lag budget per data store, dependency…
原文の言語: 英語
design cloud tag taxonomy and the mandatory tag set tied to the decisions each tag supports, select enforcement points across module defaults and pipeline policy and provider tag policy, measure tag coverage by resource count and by spend, reconcile what code…
原文の言語: 英語
size the adoption gap per product and persona as the distance between entitled capability and used capability, split the cause across capability configuration enablement product and workflow gaps, and build the intervention plan matched to that cause with…
原文の言語: 英語
qualify reference call case study logo quote and speaking candidates with willingness evidence quoted and dated rather than inferred from a score, secure customer and internal approvals scoped to a specific use with where it may appear and for how long, track…
原文の言語: 英語
build and maintain the account churn risk register with the evidence and date behind each risk, the churn reason category, the arr exposed with its basis, root cause separated from the symptom that surfaced it, the earliest signal available in the record, and…
原文の言語: 英語
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,…
原文の言語: 英語