agentsclimarketplace

Ship & operate

32,362 rows, by stacks then stars

1,245 of these skill files have been read, by 1,077 distinct authors, and what they tell an agent counted. What Ship & operate authors agree on, and what they forbid

  • Decommissioning desk

    MadewellRD/skills-lab/dist/vendor/anthropic/sdlc-command-desk/decommissioning-desk Skill

    2★ repo

    create connector-grounded decommissioning, api sunset, migration cutover, data retention, archive, rollback, and stakeholder communication artifacts for software delivery. use when Claude needs to retire a feature, service, api, dependency, integration, repository, job, flag, environment, data store, or product surface safely using github evidence, usage context, docs, release history, observability signals, compliance constraints, and downstream handoff notes for implementation-handoff-desk, deployment-desk, release-operations-desk, incident-response-desk, docs-traceability-desk, or verification-desk workflows.

  • Deployment desk

    MadewellRD/skills-lab/dist/vendor/anthropic/sdlc-command-desk/deployment-desk Skill

    2★ repo

    create connector-grounded deployment, rollout, feature-flag, change-management, go/no-go, post-deploy verification, and deployment handoff artifacts for software delivery. use when Claude needs to plan a deploy, assess rollout readiness, define staged rollout gates, map deployment risks, coordinate release-to-deploy handoff, prepare rollback or monitoring checkpoints, or produce downstream notes for release-operations-desk, observability-readiness-desk, incident-response-desk, ci-failure-desk, verification-desk, or implementation-handoff-desk workflows.

  • Incident response desk

    MadewellRD/skills-lab/dist/vendor/anthropic/sdlc-command-desk/incident-response-desk Skill

    2★ repo

    create connector-grounded incident response, bug triage, severity classification, root cause analysis, hotfix handoff, follow-up issue, post-incident review, and production-support artifacts from incidents, alerts, logs, metrics, traces, recent deploys, github issues, pull requests, ci evidence, runbooks, and stakeholder updates. use when Claude needs to triage a production failure, summarize an incident, draft an rca, plan a hotfix, map remediation work, or prepare downstream handoff notes for implementation-handoff-desk, ci-failure-desk, deployment-desk, observability-readiness-desk, release-operations-desk, verification-desk, or docs-traceability-desk workflows.

  • Observability readiness desk

    MadewellRD/skills-lab/dist/vendor/anthropic/sdlc-command-desk/observability-readiness-desk Skill

    2★ repo

    create connector-grounded observability readiness artifacts for software delivery. use when Claude needs to design or review logging, metrics, traces, dashboards, alerts, slos, operational runbooks, deployment monitoring checkpoints, telemetry gaps, or production-readiness evidence from repositories, architecture docs, deployment plans, incidents, ci results, and monitoring context.

  • Release operations desk

    MadewellRD/skills-lab/dist/vendor/anthropic/sdlc-command-desk/release-operations-desk Skill

    2★ repo

    create connector-grounded release readiness, release notes, version and tag plans, rollback plans, deployment handoff notes, and post-release verification artifacts from merged pull requests, changelogs, ci evidence, deployment configuration, issue milestones, and release history. use when Claude needs to prepare a release runbook, assess release blockers, package change summaries, define rollback or go/no-go gates, or hand off verified release work to implementation-handoff-desk, deployment-desk, verification-desk, ci-failure-desk, docs-traceability-desk, or incident-response-desk workflows.

  • Retrospective desk

    MadewellRD/skills-lab/dist/vendor/anthropic/sdlc-command-desk/retrospective-desk Skill

    2★ repo

    create connector-grounded retrospectives and continuous-improvement artifacts for software delivery. use when Claude needs to synthesize sprint, release, incident, pull request, ci, deployment, product, or team evidence into a retrospective report, lessons-learned memo, process-improvement plan, cycle-metrics summary, action-item tracker, or downstream handoff notes for product, architecture, issue planning, implementation-handoff-desk, release, ci, incident, or documentation workflows.

  • Sdlc command desk

    MadewellRD/skills-lab/dist/vendor/anthropic/sdlc-command-desk/sdlc-command-desk Skill

    2★ repo

    orchestrate complete software development lifecycle workflows across the SDLC Command Desk suite. use when the user wants an end-to-end workflow, sprint, implementation path, release path, or lifecycle coordination from idea through requirements, discovery, architecture, issue planning, implementation handoff, review, testing, verification, security, ci/cd, release, deployment, observability, incident response, maintenance, retrospective, or decommissioning. run stages continuously when possible instead of only producing a routing recommendation.

  • Cloud security posture desk

    MadewellRD/skills-lab/dist/vendor/anthropic/security-command-desk/cloud-security-posture-desk Skill

    2★ repo

    assess cloud security posture across account and subscription baselines, misconfiguration findings with blast radius, guardrail and organization policy gaps, infrastructure-as-code drift between code and deployed state, cloud entitlement and standing-privilege review, benchmark conformance, and an exposure-ordered remediation sequence. use for public storage exposure, permissive trust policies, cspm and ciem backlogs, landing zone review, terraform drift, and cloud benchmark assessment.

  • Security incident response desk

    MadewellRD/skills-lab/dist/vendor/anthropic/security-command-desk/security-incident-response-desk Skill

    2★ repo

    run security incident response across triage and severity classification against the org rubric, scoping and timeline reconstruction from evidence, volatile evidence preservation and forensic chain of custody, coordinated containment eradication and recovery, impact and data exposure assessment feeding the notification decision, and the post-incident review with owned follow-up actions. use for suspected compromise, active alerts, ransomware and business email compromise, credential abuse, and incident retrospectives.

  • Alerting quality desk

    MadewellRD/skills-lab/dist/vendor/anthropic/sre-reliability-command-desk/alerting-quality-desk Skill

    2★ repo

    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 suppression, alert noise and page load review, flapping and self-resolving pages, alerts with no runbook, and detection gaps where a customer reported the outage before any signal fired.

  • Oncall escalation desk

    MadewellRD/skills-lab/dist/vendor/anthropic/sre-reliability-command-desk/oncall-escalation-desk Skill

    2★ repo

    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 burden, responder onboarding and shadowing, override and holiday gaps, and the hours or services where a page would reach nobody.

  • Postmortem desk

    MadewellRD/skills-lab/dist/vendor/anthropic/sre-reliability-command-desk/postmortem-desk Skill

    2★ repo

    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 what-went-well record, action items classified as prevent detect mitigate or process with named owners and due dates, error budget consumed, and recurrence trend across prior incidents.

  • Production readiness review desk

    MadewellRD/skills-lab/dist/vendor/anthropic/sre-reliability-command-desk/production-readiness-review-desk Skill

    2★ repo

    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 criteria, and the reliability debt the service enters production carrying.

  • Slo error budget desk

    MadewellRD/skills-lab/dist/vendor/anthropic/sre-reliability-command-desk/slo-error-budget-desk Skill

    2★ repo

    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 proposed and aspirational ones. use for slo target setting, error budget accounting, burn rate analysis, budget policy design, and freeze adjudication.

  • Sre reliability command desk

    MadewellRD/skills-lab/dist/vendor/anthropic/sre-reliability-command-desk/sre-reliability-command-desk Skill

    2★ repo

    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, runbooks, on-call and escalation, production readiness review, change safety, incident command, postmortems, and toil reduction. use when the user wants to set reliability targets, run or review a production incident, plan capacity, harden a service against failure, prove recovery, tune paging and reduce alert noise, cut operational load, or gate a launch on readiness.

  • Web development command desk

    MadewellRD/skills-lab/dist/vendor/anthropic/web-development-command-desk/web-development-command-desk Skill

    2★ repo

    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, release, deployment, maintenance, and growth. use when the user wants to plan, build, validate, launch, operate, improve, migrate, or decommission a website, web app, landing page, portal, dashboard, docs site, ecommerce surface, or admin ui.

  • Web observability desk

    MadewellRD/skills-lab/dist/vendor/anthropic/web-development-command-desk/web-observability-desk Skill

    2★ repo

    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 release, during launch readiness, after incidents, or when improving operating visibility.

  • Web release deployment desk

    MadewellRD/skills-lab/dist/vendor/anthropic/web-development-command-desk/web-release-deployment-desk Skill

    2★ repo

    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. use when preparing or executing web launches, rollouts, migrations, hotfixes, or rollbacks.

  • Agent observability desk

    MadewellRD/skills-lab/dist/vendor/google/ai-engineering-command-desk/agent-observability-desk Skill

    2★ repo

    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.

  • Ai incident response desk

    MadewellRD/skills-lab/dist/vendor/google/ai-engineering-command-desk/ai-incident-response-desk Skill

    2★ repo

    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.

  • Ai release readiness desk

    MadewellRD/skills-lab/dist/vendor/google/ai-engineering-command-desk/ai-release-readiness-desk Skill

    2★ repo

    assess readiness to release AI capabilities across requirements, evals, safety review, red-team status, inference ops, observability, rollback, docs, support handoff, and owner approval.

  • Inference ops desk

    MadewellRD/skills-lab/dist/vendor/google/ai-engineering-command-desk/inference-ops-desk Skill

    2★ repo

    plan production inference operations including deployment topology, rate limits, quotas, retries, caching, streaming, fallbacks, batching, timeouts, secrets, logging, and SLOs.

  • Android command desk

    MadewellRD/skills-lab/dist/vendor/google/android-command-desk/android-command-desk Skill

    2★ repo

    orchestrate complete Android app and game development workflows across discovery, product, architecture, implementation, testing, release, Play Store operations, live ops, and maintenance. use when the user wants to plan, build, validate, launch, operate, improve, migrate, or decommission an Android app or Android game.

  • Android observability liveops desk

    MadewellRD/skills-lab/dist/vendor/google/android-command-desk/android-observability-liveops-desk Skill

    2★ repo

    define Android observability and live ops for crash reporting, logs, metrics, analytics events, alerts, feature flags, remote config, game economy/events, rollout monitoring, and incident response.

  • Android release store ops desk

    MadewellRD/skills-lab/dist/vendor/google/android-command-desk/android-release-store-ops-desk Skill

    2★ repo

    plan Android builds, signing, versioning, CI/CD, AAB/APK packaging, internal testing, Play tracks, release notes, staged rollout, rollback, Play Asset Delivery, and store listing readiness.

  • Cloud infrastructure command desk

    MadewellRD/skills-lab/dist/vendor/google/cloud-infrastructure-command-desk/cloud-infrastructure-command-desk Skill

    2★ repo

    orchestrate cloud infrastructure work across landing zones, account and subscription structure, cloud iam and federation, vpc and cidr network topology, hybrid connectivity and dns, compute and managed kubernetes platforms, object storage and managed databases, multi-region resilience and disaster recovery, infrastructure as code and state backends, provisioning pipelines and plan approval, key management and secret rotation, cloud security posture and cis benchmarks, tagging and resource inventory, cost allocation rightsizing and savings commitments, drift detection, migration waves, and decommissioning. use when the user wants to design, provision, harden, reconcile, rightsize, migrate, or retire cloud infrastructure in one or more providers.

  • Infrastructure as code desk

    MadewellRD/skills-lab/dist/vendor/google/cloud-infrastructure-command-desk/infrastructure-as-code-desk Skill

    2★ repo

    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 pinning with lock files, composition patterns across environments, validation and policy unit test gates, secrets-out-of-state discipline, state import and refactor safety, and measured codification coverage of the live estate.

  • Escalation management desk

    MadewellRD/skills-lab/dist/vendor/google/customer-success-command-desk/escalation-management-desk Skill

    2★ repo

    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 at the severity the impact warrants, an action plan with an owner and date on every item, updates delivered on the committed cadence whether or not there is progress, relationship repair alongside the technical fix, and closure only on customer confirmation. use for red accounts, critical situations, executive escalations, service disruptions, and missed commitment recovery.

  • Customer support command desk

    MadewellRD/skills-lab/dist/vendor/google/customer-support-command-desk/customer-support-command-desk Skill

    2★ repo

    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, customer-facing incident communication and status page updates, post-incident follow-up and outage letters, knowledge base authoring, self-service deflection, queue and backlog health, workforce coverage and staffing, helpdesk tooling and automation, qa review and calibration, contact driver analysis, and support metrics reporting. use when a ticket needs triage or a severity, an sla is about to breach, a customer reports something nobody can reproduce, a bug needs filing to engineering, an escalation needs raising, a backlog is aging, csat or first response time is being explained, a macro or help center article needs writing, deflection is being measured, an outage needs customer comms and an outage letter, or staffing is being planned against forecast volume.

  • Engineering escalation desk

    MadewellRD/skills-lab/dist/vendor/google/customer-support-command-desk/engineering-escalation-desk Skill

    2★ repo

    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 against the standing wake criteria, reporting tracker state and fix version as the tracker says it with the date read, holding the internal and customer update cadence, and recording de-escalation back to support. use for tier escalation, on-call paging, defect status loops, and engineering handoffs.

  • Support tooling automation desk

    MadewellRD/skills-lab/dist/vendor/google/customer-support-command-desk/support-tooling-automation-desk Skill

    2★ repo

    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 analysis against everything firing on the same event, sandbox validation against a real ticket sample, a suppression path with how fast it takes effect, and a rollback position. use for zendesk, servicenow, jira service management, freshdesk, salesforce service cloud, and similar platform change work.

  • Data incident response desk

    MadewellRD/skills-lab/dist/vendor/google/data-command-desk/data-incident-response-desk Skill

    2★ repo

    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 restatement or withdrawal decision with its reconciliation, consumer notification and the restatement record, and the postmortem with the detection gap that let it run. use when a wrong number reached consumers, a load duplicated or dropped rows, or a schema break silently corrupted a mart.

  • Data observability desk

    MadewellRD/skills-lab/dist/vendor/google/data-command-desk/data-observability-desk Skill

    2★ repo

    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 review, time to detection, and monitor ownership. use when consumers find bad data before any monitor fires, when alerts are noisy, flapping, or unowned, or when an asset needs detection coverage before it is trusted.

  • Continuous control monitoring desk

    MadewellRD/skills-lab/dist/vendor/google/grc-command-desk/continuous-control-monitoring-desk Skill

    2★ repo

    design and assess continuous control monitoring across the monitoring coverage map, automated check definitions with signal source and evaluation frequency, configuration drift and check failure routed to a named owner, control health metrics computed from actual results, monitoring evidence produced as a byproduct, and checks blocked on a missing signal source. use for control automation, monitoring coverage gaps, alert ownership, control health dashboards, and converting manual controls into continuously evidenced ones.

  • Ios command desk

    MadewellRD/skills-lab/dist/vendor/google/ios-command-desk/ios-command-desk Skill

    2★ repo

    orchestrate complete iOS app and game development workflows across discovery, product, architecture, implementation, testing, release, App Store operations, live ops, and maintenance. use when the user wants to plan, build, validate, launch, operate, improve, migrate, or decommission an iOS app or iOS game.

  • Ios observability liveops desk

    MadewellRD/skills-lab/dist/vendor/google/ios-command-desk/ios-observability-liveops-desk Skill

    2★ repo

    define iOS observability and live ops for crash reporting, logs, metrics, analytics events, alerts, feature flags, remote config, game economy/events, rollout monitoring, and incident response.

  • Ios release app store ops desk

    MadewellRD/skills-lab/dist/vendor/google/ios-command-desk/ios-release-app-store-ops-desk Skill

    2★ repo

    plan iOS builds, signing, versioning, CI/CD, archive/export packaging, internal testing, TestFlight groups and App Store release states, release notes, staged rollout, rollback, on-demand resources and asset delivery, and store listing readiness.

  • Approval escalation desk

    MadewellRD/skills-lab/dist/vendor/google/legal-contracts-command-desk/approval-escalation-desk Skill

    2★ repo

    run the contract approval gate by building the deviation register, classifying each departure as within fallback or outside the playbook, assembling one approval package that presents combined exposure rather than clause by clause, naming the authority level and the delegation of authority provision that sets it, routing to the named approver, escalating where a threshold is exceeded or an approver is unavailable, and recording the decision with its conditions. use when asked who has to approve a deviation, what the delegation of authority requires, how to package non-standard terms for sign-off, how to escalate a stuck approval, whether an approval is still valid after the terms moved, or to produce the decision record for a deal.

  • Cicd platform desk

    MadewellRD/skills-lab/dist/vendor/google/platform-engineering-command-desk/cicd-platform-desk Skill

    2★ repo

    design the ci/cd platform layer, covering reusable workflow and pipeline definitions, runner fleet sizing isolation and autoscaling, build and dependency cache strategy, artifact and container registry layout with retention and promotion by digest, dependency proxies and pull-through caches, supply-chain controls including provenance attestation signing and software bill of materials with their verification gates, build and queue performance targets, and the boundary between platform-owned and tenant-owned pipeline stages. use for shared pipeline design, runner fleet work, build cache and registry strategy, slsa and supply-chain hardening, ci queue performance, and pipeline ownership boundaries.

  • Developer experience research desk

    MadewellRD/skills-lab/dist/vendor/google/platform-engineering-command-desk/developer-experience-research-desk Skill

    2★ repo

    research developer experience and delivery performance across the developer journey, covering friction mapping, cognitive load assessment, feedback-loop latency, and baselines for lead time, deployment frequency, change failure rate, time to restore, time to first deploy, provisioning wait, build and review wait, and onboarding time, with an explicit measured-versus-unmeasured split. use when teams complain about slow delivery, onboarding drag, tooling sprawl, ticket-driven infrastructure, low platform adoption, or when a devex baseline is needed before platform investment.

  • Platform change rollout desk

    MadewellRD/skills-lab/dist/vendor/google/platform-engineering-command-desk/platform-change-rollout-desk Skill

    2★ repo

    ship platform changes to tenants safely using ring definitions and promotion criteria, breaking versus additive classification against the published compatibility guarantee, control-plane and cluster upgrade sequencing, rollback and pause criteria, tenant-facing change notice, and the freeze and exception path for tenants who cannot absorb a change on schedule.

  • Platform observability desk

    MadewellRD/skills-lab/dist/vendor/google/platform-engineering-command-desk/platform-observability-desk Skill

    2★ repo

    design the default instrumentation baseline and telemetry pipeline for an internal developer platform including auto-instrumentation, collector routing, metrics logs traces and profiles, resource attributes and naming conventions, cardinality and retention limits with their cost consequence, tenant-scoped dashboards and access, and the coverage gaps where the platform cannot see its own consumers.

  • Platform slo reliability desk

    MadewellRD/skills-lab/dist/vendor/google/platform-engineering-command-desk/platform-slo-reliability-desk Skill

    2★ repo

    define platform slis and slos for the control plane, provisioning path, pipelines, registries, and developer portal including error budget policy and its consequences, dependency and single-point-of-failure analysis, degradation modes when a platform component fails, and the honest split between measured and aspirational objectives.

  • Launch readiness desk

    MadewellRD/skills-lab/dist/vendor/google/product-command-desk/launch-readiness-desk Skill

    2★ repo

    assess product launch readiness across scope, release state, GTM, docs, support, success, metrics, rollback, risks, approvals, and post-launch monitoring.

  • Ci failure desk

    MadewellRD/skills-lab/dist/vendor/google/sdlc-command-desk/ci-failure-desk Skill

    2★ repo

    create connector-grounded ci/cd failure triage and pipeline-health artifacts for software delivery. use when Gemini needs to diagnose github actions or build failures, classify flaky tests, inspect logs and workflow runs, decide rerun versus fix, identify failing checks, map ci failures to code changes or infrastructure, or prepare downstream handoff notes for review-quality-desk, verification-desk, release-operations-desk, incident-response-desk, issue-planning-desk, or implementation-handoff-desk workflows.

  • Decommissioning desk

    MadewellRD/skills-lab/dist/vendor/google/sdlc-command-desk/decommissioning-desk Skill

    2★ repo

    create connector-grounded decommissioning, api sunset, migration cutover, data retention, archive, rollback, and stakeholder communication artifacts for software delivery. use when Gemini needs to retire a feature, service, api, dependency, integration, repository, job, flag, environment, data store, or product surface safely using github evidence, usage context, docs, release history, observability signals, compliance constraints, and downstream handoff notes for implementation-handoff-desk, deployment-desk, release-operations-desk, incident-response-desk, docs-traceability-desk, or verification-desk workflows.

  • Deployment desk

    MadewellRD/skills-lab/dist/vendor/google/sdlc-command-desk/deployment-desk Skill

    2★ repo

    create connector-grounded deployment, rollout, feature-flag, change-management, go/no-go, post-deploy verification, and deployment handoff artifacts for software delivery. use when Gemini needs to plan a deploy, assess rollout readiness, define staged rollout gates, map deployment risks, coordinate release-to-deploy handoff, prepare rollback or monitoring checkpoints, or produce downstream notes for release-operations-desk, observability-readiness-desk, incident-response-desk, ci-failure-desk, verification-desk, or implementation-handoff-desk workflows.

  • Incident response desk

    MadewellRD/skills-lab/dist/vendor/google/sdlc-command-desk/incident-response-desk Skill

    2★ repo

    create connector-grounded incident response, bug triage, severity classification, root cause analysis, hotfix handoff, follow-up issue, post-incident review, and production-support artifacts from incidents, alerts, logs, metrics, traces, recent deploys, github issues, pull requests, ci evidence, runbooks, and stakeholder updates. use when Gemini needs to triage a production failure, summarize an incident, draft an rca, plan a hotfix, map remediation work, or prepare downstream handoff notes for implementation-handoff-desk, ci-failure-desk, deployment-desk, observability-readiness-desk, release-operations-desk, verification-desk, or docs-traceability-desk workflows.

  • Observability readiness desk

    MadewellRD/skills-lab/dist/vendor/google/sdlc-command-desk/observability-readiness-desk Skill

    2★ repo

    create connector-grounded observability readiness artifacts for software delivery. use when Gemini needs to design or review logging, metrics, traces, dashboards, alerts, slos, operational runbooks, deployment monitoring checkpoints, telemetry gaps, or production-readiness evidence from repositories, architecture docs, deployment plans, incidents, ci results, and monitoring context.

  • Release operations desk

    MadewellRD/skills-lab/dist/vendor/google/sdlc-command-desk/release-operations-desk Skill

    2★ repo

    create connector-grounded release readiness, release notes, version and tag plans, rollback plans, deployment handoff notes, and post-release verification artifacts from merged pull requests, changelogs, ci evidence, deployment configuration, issue milestones, and release history. use when Gemini needs to prepare a release runbook, assess release blockers, package change summaries, define rollback or go/no-go gates, or hand off verified release work to implementation-handoff-desk, deployment-desk, verification-desk, ci-failure-desk, docs-traceability-desk, or incident-response-desk workflows.

  • Retrospective desk

    MadewellRD/skills-lab/dist/vendor/google/sdlc-command-desk/retrospective-desk Skill

    2★ repo

    create connector-grounded retrospectives and continuous-improvement artifacts for software delivery. use when Gemini needs to synthesize sprint, release, incident, pull request, ci, deployment, product, or team evidence into a retrospective report, lessons-learned memo, process-improvement plan, cycle-metrics summary, action-item tracker, or downstream handoff notes for product, architecture, issue planning, implementation-handoff-desk, release, ci, incident, or documentation workflows.

  • Sdlc command desk

    MadewellRD/skills-lab/dist/vendor/google/sdlc-command-desk/sdlc-command-desk Skill

    2★ repo

    orchestrate complete software development lifecycle workflows across the SDLC Command Desk suite. use when the user wants an end-to-end workflow, sprint, implementation path, release path, or lifecycle coordination from idea through requirements, discovery, architecture, issue planning, implementation handoff, review, testing, verification, security, ci/cd, release, deployment, observability, incident response, maintenance, retrospective, or decommissioning. run stages continuously when possible instead of only producing a routing recommendation.

  • Cloud security posture desk

    MadewellRD/skills-lab/dist/vendor/google/security-command-desk/cloud-security-posture-desk Skill

    2★ repo

    assess cloud security posture across account and subscription baselines, misconfiguration findings with blast radius, guardrail and organization policy gaps, infrastructure-as-code drift between code and deployed state, cloud entitlement and standing-privilege review, benchmark conformance, and an exposure-ordered remediation sequence. use for public storage exposure, permissive trust policies, cspm and ciem backlogs, landing zone review, terraform drift, and cloud benchmark assessment.

  • Security incident response desk

    MadewellRD/skills-lab/dist/vendor/google/security-command-desk/security-incident-response-desk Skill

    2★ repo

    run security incident response across triage and severity classification against the org rubric, scoping and timeline reconstruction from evidence, volatile evidence preservation and forensic chain of custody, coordinated containment eradication and recovery, impact and data exposure assessment feeding the notification decision, and the post-incident review with owned follow-up actions. use for suspected compromise, active alerts, ransomware and business email compromise, credential abuse, and incident retrospectives.

  • Alerting quality desk

    MadewellRD/skills-lab/dist/vendor/google/sre-reliability-command-desk/alerting-quality-desk Skill

    2★ repo

    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 suppression, alert noise and page load review, flapping and self-resolving pages, alerts with no runbook, and detection gaps where a customer reported the outage before any signal fired.

  • Oncall escalation desk

    MadewellRD/skills-lab/dist/vendor/google/sre-reliability-command-desk/oncall-escalation-desk Skill

    2★ repo

    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 burden, responder onboarding and shadowing, override and holiday gaps, and the hours or services where a page would reach nobody.

  • Postmortem desk

    MadewellRD/skills-lab/dist/vendor/google/sre-reliability-command-desk/postmortem-desk Skill

    2★ repo

    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 what-went-well record, action items classified as prevent detect mitigate or process with named owners and due dates, error budget consumed, and recurrence trend across prior incidents.

  • Production readiness review desk

    MadewellRD/skills-lab/dist/vendor/google/sre-reliability-command-desk/production-readiness-review-desk Skill

    2★ repo

    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 criteria, and the reliability debt the service enters production carrying.

  • Slo error budget desk

    MadewellRD/skills-lab/dist/vendor/google/sre-reliability-command-desk/slo-error-budget-desk Skill

    2★ repo

    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 proposed and aspirational ones. use for slo target setting, error budget accounting, burn rate analysis, budget policy design, and freeze adjudication.

  • Sre reliability command desk

    MadewellRD/skills-lab/dist/vendor/google/sre-reliability-command-desk/sre-reliability-command-desk Skill

    2★ repo

    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, runbooks, on-call and escalation, production readiness review, change safety, incident command, postmortems, and toil reduction. use when the user wants to set reliability targets, run or review a production incident, plan capacity, harden a service against failure, prove recovery, tune paging and reduce alert noise, cut operational load, or gate a launch on readiness.