メニュー
このリポジトリの skills
SkillsMP は MadewellRD/skills-lab から 1,540 件の skill を収集しています。skill を開くとソースと詳細を確認できます。
MadewellRD/skills-lab収集済み skill 1,540 件中 40 件を表示しています。
run vulnerability management across consolidated and deduplicated findings from every scanner, risk-based prioritization with each severity carrying its scale, asset criticality and exposure weighting, remediation ownership and service level assignment, patch…
原文の言語: 英語
design and review production alerting including symptom-based paging on user impact, multi-window multi-burn-rate rules tied to error budget spend, page versus ticket versus dashboard routing, deduplication grouping inhibition and dependency-aware…
原文の言語: 英語
check backup coverage against the data inventory, record mechanism schedule retention and immutability with their sources, write the restore procedure and its measured time from a dated drill, verify integrity and deletion resistance including ransomware and…
原文の言語: 英語
build the demand model and its drivers, measure headroom against the binding saturation signal rather than average cpu, find quota connection partition thread and licence ceilings, state provisioning lead time, compute failover headroom at real peak, and…
原文の言語: 英語
make production change safe through rollout strategy and staged exposure, canary analysis signals and promotion thresholds, bake time per stage, rollback triggers and whether rollback has ever actually succeeded, freeze policy and its exception path, schema…
原文の言語: 英語
design chaos experiments with an explicit steady-state hypothesis, choose the fault and its scope, contain blast radius with abort criteria written before injection, run game days that exercise responders and runbooks, and promote controls that fail the…
原文の言語: 英語
map the dependency graph along each critical user journey with hard, soft, and degraded-ok coupling, find single points of failure and shared-fate risk across zones clusters datastores identity dns and control planes, analyze failure modes with trigger…
原文の言語: 英語
set rto and rpo per tier with their sources, state the failover mode actually implemented rather than the one designed, define regional evacuation and failback, derive the dependency recovery order across identity dns data tier and control plane, run and…
原文の言語: 英語
run a live production incident with severity declaration, incident commander and operations communications and scribe roles, evidence capture before any mitigating restart, reversible mitigation preferred over diagnosis, internal and customer communication…
原文の言語: 英語
derive a workload model from production traffic, design load stress soak spike and breakpoint profiles with what each proves, state environment fidelity gaps and what they invalidate, measure the saturation point and the behavior past it, and define the…
原文の言語: 英語
design and review on-call rotations and escalation including coverage and follow-the-sun arrangements, primary and secondary tiers with acknowledgement and response expectations, shift handoff and transfer of open state, page load budget and out-of-hours…
原文の言語: 英語
write and facilitate blameless postmortems and incident reviews with a timeline anchored to timestamped evidence, contributing factors across technical detection and process dimensions, counterfactual discipline that resists the single root cause story, a…
原文の言語: 英語
run a production readiness review or support acceptance review with a gate set scored pass, waived, failed, or not assessed against named evidence, a launch or acceptance decision with conditions, waivers carrying a named owner and an expiry date, hand-back…
原文の言語: 英語
run the recurring service reliability review covering error budget attainment and burn across the period, error budget policy adjudication including whether a freeze applies and its exception path, incident page and toil trends, open postmortem actions and…
原文の言語: 英語
design timeout and retry budgets, circuit breakers, bulkheads, load shedding and admission control, backpressure, cache and stale-serve fallbacks, idempotency and replay safety, and graceful degradation modes, and record whether each control is configured,…
原文の言語: 英語
write and review operational runbooks keyed to the alert or failure mode that triggers them, with the first mitigating action stated before diagnosis, diagnostic decision trees carrying exact queries and dashboards, escalation and rollback branches, access…
原文の言語: 英語
map critical user journeys to the services on their path, assign criticality tiers using an explicit tiering rule, attribute ownership and pager rotation per service, and name every service with no owner, no tier, or a rotation that resolves to nobody. use…
原文の言語: 英語
specify service level indicators per critical user journey including the good-event and valid-event definitions, the measurement point and its bias, the implementation query or export behind each indicator, and the split between measured, partially measured,…
原文の言語: 英語
set service level objectives with windows, define and compute the error budget and its balance, account for burn rate over multiple windows, write an error budget policy with consequences that bind someone, and separate objectives agreed with the owner from…
原文の言語: 英語
orchestrate site reliability engineering work across slis, slos, error budgets, capacity planning, load and performance testing, chaos and resilience testing, dependency and failure-mode analysis, disaster recovery, backup and restore, alerting quality,…
原文の言語: 英語
account for operational toil with measured hours and how they were established, classify each recurring task as automatable partially automatable or inherent, define the elimination path per task through automation self-service or a design change that removes…
原文の言語: 英語
define accessibility and seo requirements for web surfaces including wcag, semantic html, keyboard navigation, focus, screen-reader behavior, metadata, structured data, canonicals, sitemaps, robots, crawlability, localization, and page-type search…
原文の言語: 英語
plan web backend integration across api contracts, auth, sessions, bff layers, cms connections, data models, caching, rate limits, pagination, failure modes, and ownership. use when a web surface depends on services, databases, third-party systems, identity,…
原文の言語: 英語
define cms and content operations for web properties including structured content models, editorial workflow, publishing rules, approvals, localization, migration, governance, content debt, metadata ownership, and day-two content maintenance. use for…
原文の言語: 英語
create implementation-ready frontend engineering plans for web surfaces including rendering strategy, routing, layouts, components, state, forms, data fetching, framework constraints, accessibility hooks, performance controls, and coding-agent handoffs. use…
原文の言語: 英語
design web information architecture including sitemap, route hierarchy, navigation, url taxonomy, content relationships, wayfinding, content hierarchy, and findability. use when Gemini needs to structure websites, portals, dashboards, docs sites, ecommerce…
原文の言語: 英語
create web-specific product requirements, page and route scope, user journeys, acceptance criteria, success metrics, analytics intent, source facts, risks, open questions, and downstream handoff notes for websites, web apps, landing pages, portals,…
原文の言語: 英語
define ux/ui design system guidance for web surfaces including component inventory, responsive behavior, design tokens, interaction states, accessibility-aware patterns, brand consistency, and design governance. use before frontend implementation or…
原文の言語: 英語
orchestrate complete web development workflows across product, information architecture, ux/ui design systems, frontend engineering, backend integration, cms/content operations, web security/secops, performance, accessibility, seo, testing, observability,…
原文の言語: 英語
coordinate post-launch web maintenance and growth including analytics-informed backlog, experiments, conversion optimization, content refresh, seo iteration, accessibility remediation, performance regression follow-up, dependency upgrades, refactors,…
原文の言語: 英語
design production web observability including rum, synthetic checks, availability, frontend errors, api errors, latency, core web vitals, analytics events, dashboards, alerts, ownership, incident hooks, launch monitoring, and post-launch review. use before…
原文の言語: 英語
plan and gate web performance using core web vitals, performance budgets, rendering cost, hydration, bundle size, images, fonts, scripts, cdn, caching, data fetching, latency, field and lab measurement, launch thresholds, and regression controls. use before…
原文の言語: 英語
plan web release and deployment across ci/cd, preview environments, build commands, environment promotion, hosting, cdn, edge config, cache invalidation, feature flags, launch checklist, rollback, post-release validation, and release-to-observability handoff.…
原文の言語: 英語
review and plan web security and secops controls across auth, sessions, browser storage, cookies, csp, security headers, cors, csrf, dependency risk, secrets, third-party scripts, cdn/edge hardening, abuse prevention, monitoring hooks, and incident readiness.…
原文の言語: 英語
define web testing and qa strategy across browsers, devices, responsive layouts, visual regression, forms, auth flows, integrations, accessibility checks, seo checks, performance checks, smoke tests, regression tests, release signoff, and defect triage. use…
原文の言語: 英語
design AI agent architecture including planning boundaries, execution loops, memory and state strategy, tool routing, approval gates, retries, delegation, and halt behavior.
原文の言語: 英語
design observability for AI agents and workflows including traces, prompts, model calls, tool calls, retrieval events, approvals, errors, eval probes, cost, latency, and safety signals.
原文の言語: 英語
orchestrate AI engineering workflows from capability intent through model, prompt, tool, agent, retrieval, eval, safety, inference, observability, release, and incident stages using connector-grounded evidence, workflow packets, stage advancement, and halt…
原文の言語: 英語
triage AI production incidents involving hallucination spikes, safety failures, prompt injection, tool misuse, data leakage, model regressions, cost spikes, latency degradation, eval regressions, or user harm reports.
原文の言語: 英語
assess readiness to release AI capabilities across requirements, evals, safety review, red-team status, inference ops, observability, rollback, docs, support handoff, and owner approval.
原文の言語: 英語