Claude Skills by cloudthinker-ai

Use when performing printer troubleshooting guide — common printer issues resolution guide covering connectivity problems, print quality issues, paper jams, driver configuration, and network printer setup. Provides systematic troubleshooting steps for helpdesk agents to resolve the most frequent printer-related support tickets.

Use when performing privacy impact assessment — template for conducting Privacy Impact Assessments (PIA) on new projects or system changes involving personal data. Covers data flow mapping, purpose limitation analysis, data minimization review, consent mechanisms, third-party sharing evaluation, and risk mitigation to ensure privacy by design.

Use when performing production readiness incident review — production readiness validation focused on incident response preparedness before launching a new service or major feature. Reviews on-call coverage, runbook completeness, monitoring and alerting setup, escalation paths, rollback procedures, and communication plans to ensure the team can effectively respond to incidents.

Use when performing production readiness review — production readiness checklist covering scalability, reliability, observability, security, operational maturity, and documentation. Use before promoting a service to production or during periodic production-readiness audits.

Use when performing quarterly planning template — provides a structured framework for engineering quarterly planning, covering goal setting, capacity allocation, dependency mapping, risk assessment, and milestone definition. This template helps engineering teams align their quarterly work with organizational objectives while maintaining realistic commitments and appropriate investment in tech debt and innovation.

Use when performing queue design review — reviews the design of message queue and event streaming architectures, covering queue topology, consumer design, ordering guarantees, dead letter handling, and capacity planning. This template helps teams design reliable asynchronous processing systems and avoid common messaging pitfalls.

Use when performing rate limiting design — guides teams through designing and implementing rate limiting strategies for APIs and services. This template covers algorithm selection, limit configuration, client communication, and monitoring to protect backend systems from abuse and overload while maintaining a good developer experience.

Use when performing release readiness review — comprehensive checklist for evaluating release readiness before deploying to production. Covers code completeness, testing validation, documentation updates, monitoring readiness, rollback procedures, stakeholder sign-offs, and go/no-go decision criteria to ensure confident releases.

Use when performing reliability scorecard — produces a comprehensive reliability scorecard for a service or system, evaluating it across multiple dimensions including availability, latency, durability, and operational readiness. Use this template to establish a baseline, track improvements over time, and benchmark services against organizational standards.

Use when performing reserved instance planning — analyzes current cloud compute usage patterns to recommend optimal reserved instance or savings plan purchases. Covers utilization analysis, commitment term selection, payment option comparison, coverage gap identification, and ongoing reservation management.

Use when performing rfc template — structures a Request for Comments (RFC) document for proposing significant technical changes that require cross-team input and approval. This template guides authors through problem definition, proposed solution, alternatives analysis, and rollout planning, ensuring proposals are comprehensive enough for informed review.

Use when performing root cause analysis template — comprehensive root cause analysis framework combining 5-Whys analysis, Ishikawa (fishbone) diagrams, and fault tree analysis methods. Provides structured templates for identifying contributing factors, distinguishing root causes from symptoms, and generating actionable corrective and preventive actions.

Use when performing runbook automation assessment — evaluates existing runbooks for automation potential, assessing each procedure's complexity, frequency, and risk to determine which runbooks should be automated first. This template produces a prioritized automation backlog and identifies the tooling needed to convert manual runbooks into automated remediation workflows.

Use when performing runbook cache flush — cache flush and warm procedure covering impact assessment, flush execution, and warming strategy. Use when cache data is stale, after schema changes, or when cache corruption is suspected.

Use when performing runbook database failover — database failover procedure covering pre-checks, failover execution, validation, and DNS update. Use when performing planned database failover, responding to primary database failure, or testing failover readiness.

Use when performing runbook dependency upgrade — dependency upgrade workflow covering compatibility check, testing, deployment, and monitoring. Use for library upgrades, framework version bumps, runtime updates, or security patch application.

Use when performing runbook load balancer failover — load balancer failover procedure covering health checks, traffic shift, backend validation, and rollback. Use for planned LB maintenance, active-passive failover, or responding to LB degradation.

Use when performing runbook log rotation — log rotation and cleanup procedure covering disk usage check, rotation configuration, archival, and cleanup. Use when disk usage is high due to logs, configuring new log rotation policies, or performing periodic log maintenance.

Use when performing runbook network partition — network partition recovery procedure covering diagnosis, route fix, connectivity validation, and root cause analysis. Use when services experience network segmentation, intermittent connectivity, or cross-zone communication failures.

Use when performing runbook os patching — oS patching window procedure covering pre-patch backup, patch application, reboot sequence, and validation. Use for scheduled maintenance windows, security patch deployments, or kernel upgrades.

Use when performing runbook scaling event — application scaling procedure covering trigger assessment, scale execution, and monitoring. Use for manual scaling in response to traffic spikes, planned events, or autoscaling failures.

Use when performing runbook secret rotation — secret and credential rotation procedure covering discovery, rotation execution, deployment, and validation. Use for scheduled credential rotation, responding to leaked secrets, or compliance-driven key rotation.

Use when performing runbook storage expansion — storage expansion procedure covering capacity check, volume resize, filesystem extension, and validation. Use when disk usage approaches thresholds, before large data ingestion, or for planned storage growth.

Use when performing schema migration review — reviews database schema migrations for safety, performance impact, and backward compatibility. This template ensures migrations are evaluated for lock contention, data integrity, rollback capability, and deployment sequencing before execution in production environments.

Use when performing secrets rotation audit — audits the rotation status of all secrets, credentials, API keys, and certificates across services and environments. This template identifies stale secrets, missing rotation policies, and non-compliant credential management practices, producing a remediation plan to strengthen secrets hygiene.

Use when performing security audit checklist — run a structured security audit across IAM, network, encryption, logging, and vulnerability management. Covers identity hygiene, network segmentation, data protection, and audit trail completeness. Use for periodic security reviews or pre-compliance preparation.

Use when performing security code review — security-focused code review template covering OWASP Top 10 vulnerabilities, injection attacks, authentication flaws, authorization bypass, sensitive data exposure, and cryptographic misuse. Provides a systematic security review framework for identifying and remediating security risks before code reaches production.

Use when performing security devops assessment — assesses the integration of security practices into DevOps workflows (DevSecOps). Covers shift-left security, automated security testing in CI/CD, supply chain security, runtime protection, security culture, and vulnerability management maturity.

Use when performing security incident response — security-specific incident response playbook covering breach detection, compromised credentials response, data leak containment, evidence preservation, regulatory notification requirements, forensic investigation coordination, and communication protocols. Provides structured workflows for security incidents distinct from operational incidents.

Use when performing service deprecation plan — template for planning and executing the deprecation and decommissioning of services. Covers consumer impact analysis, migration path definition, communication timeline, traffic monitoring, graceful shutdown procedures, and resource cleanup to safely retire services without disrupting dependents.

Use when performing service mesh health check — performs a comprehensive health check of a service mesh deployment, evaluating control plane status, data plane proxy health, mTLS coverage, traffic policies, and observability configuration. Use this template for periodic mesh audits or before major mesh upgrades.

Use when performing sla breach escalation — sLA breach detection and escalation procedure covering proactive SLA monitoring, breach notification workflows, escalation matrices, and remediation tracking. Ensures SLA breaches are identified early, stakeholders are notified promptly, and corrective actions are documented to prevent recurrence.

Use when performing slack deployment notification — post structured deployment notifications to Slack channels. Formats release details into a clean Slack message with service name, version, environment, deployer, key changes, and rollback instructions. Use after completing a deployment or to announce an upcoming deployment window.

Post concise incident RCA summaries to Slack channels. Formats findings into a readable Slack message with severity, root cause, impact, and action items.

Use when performing slo definition workshop — sLO definition workflow covering SLI selection, target setting, error budget policy, alerting strategy, and stakeholder alignment. Use when establishing SLOs for a new service, revising existing targets, or implementing an SRE practice.

Use when performing soc2 compliance check — assess SOC2 Type II compliance readiness across Trust Service Criteria: security, availability, processing integrity, confidentiality, and privacy. Covers access controls, change management, monitoring, incident response, and vendor management. Use for audit preparation or continuous compliance monitoring.

Use when performing software installation request — software request, approval, licensing check, and deployment workflow covering the full lifecycle from user request through procurement, license validation, security review, installation, and verification. Ensures software installations comply with licensing agreements and security policies.

Use when performing sox it controls audit — conducts an IT general controls audit for Sarbanes-Oxley (SOX) compliance, covering access management, change management, computer operations, and program development controls for systems involved in financial reporting. Includes ITGC testing procedures and deficiency classification.

Use when performing spot instance strategy — designs a spot instance strategy for fault-tolerant and flexible workloads to achieve significant cost savings. Covers workload suitability assessment, instance diversification, interruption handling, capacity management, and hybrid strategies combining spot with on-demand and reserved instances.

Use when performing sprint retrospective — facilitates structured sprint retrospectives that help engineering teams reflect on what went well, what could be improved, and what actions to take. This template guides teams through data-driven reflection, collaborative discussion, and actionable commitment tracking across sprint cycles.

Use when performing sre maturity model — evaluates an organization's Site Reliability Engineering maturity across SLO management, incident response, toil reduction, capacity planning, and reliability culture. Produces a maturity scorecard and actionable roadmap for advancing reliability engineering practices.

Use when performing ssl certificate rotation — sSL/TLS certificate rotation workflow covering certificate discovery, renewal planning, deployment procedures, and validation. Supports ACM, Let's Encrypt, and manual CA certificates. Use for scheduled rotations, expiring certificate remediation, or certificate automation setup.

Use when performing storage migration plan — structured plan for migrating data between storage systems, volumes, or tiers. Covers capacity planning, data transfer strategy, performance benchmarking, cutover coordination, and validation to ensure data integrity and minimal disruption during storage transitions.

Use when performing system design document — provides a structured template for creating comprehensive system design documents that cover requirements, architecture decisions, component design, data models, API contracts, and operational considerations. Use this template to ensure design documents are thorough and follow organizational standards.

Use when performing team health check — provides a structured framework for assessing engineering team health across key dimensions including delivery pace, code quality, collaboration, well-being, and technical practices. This template helps engineering managers and team leads identify areas of strength and opportunities for improvement through regular pulse checks.

Use when performing tech radar update — guides the process of creating or updating a technology radar that tracks the adoption status of technologies, tools, frameworks, and practices across the organization. Covers technology assessment, ring classification, team input collection, and communication of technology guidance.

Use when performing technical debt assessment — template for systematically identifying, categorizing, and prioritizing technical debt across a codebase or system. Covers code quality metrics, architecture smells, dependency risks, test coverage gaps, and creates a prioritized remediation backlog with business impact analysis.

Use when performing third party outage response — response playbook for when a third-party vendor or external dependency experiences an outage. Covers impact assessment, customer communication, workaround activation, vendor status monitoring, internal coordination, and post-outage follow-up actions to minimize blast radius from upstream failures.

Use when performing threat model template — guides teams through a structured threat modeling exercise using the STRIDE methodology. This template helps identify threats, assess risks, and define mitigations for a system or feature, producing a comprehensive threat model document that satisfies security review requirements.

Use when performing toil reduction analysis — systematically identifies, quantifies, and prioritizes toil within engineering teams. This template guides SRE and operations teams through cataloging repetitive manual work, measuring its impact on productivity, and developing automation strategies to reclaim engineering time for higher-value projects.