More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Storage Migration Readiness Review

    1

    Storage Migration Readiness Review is a bounded ToolForge Labs workflow.

    $1

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Storage Migration Readiness Review

    Storage Migration Readiness Review

    Example session with this skill installed

    Review the attached migration plan for moving our production PostgreSQL cluster from an on-prem SAN to RDS. Here are the runbook snippets and the terraform storage configs.

    • Read your context and instructions
    • Compiled the storage migration readiness

    I have reviewed the PostgreSQL migration plan and Terraform configurations. The review focuses on data integrity, cutover sequencing, and rollback feasibility based on the provided snippets.

    Storage Migration Readiness Review: On-Prem SAN to RDS

    CategoryStatusFindings
    Source/Target CompatibilityPASSRDS instance type (db.m6g.4xlarge) matches IOPS requirements of the source SAN.
    Change CaptureWARNINGRunbook mentions logical replication but lacks the max_replication_slots config for the source.
    ReconciliationBLOCKERNo byte-count or checksum verification step is defined for the final cutover sync.
    Rollback PathGAPEvidence of a tested "reverse sync" or point-in-time recovery to SAN is missing.
    MonitoringPASSCloudWatch alarms for StorageFree and WriteLatency are defined in Terraform.

    Blockers and Evidence Gaps

    Missing Reconciliation Logic: The plan lacks a script or command to verify record counts between the SAN and RDS before DNS cutover.
    2.

    Replication Slot Config: Verification of source DB parameter wal_level=logical is required but not documented in the pre-flight check.
    3.

    Rollback Validation: There is no evidence that the rollback trigger (e.g., latency > 500ms) has an automated or verified manual path back to the SAN once the write-lock is released.

    Approval Questions for Owners

    • Has the pg_checksums utility been run on the source to ensure no existing block corruption will be replicated?
    • Who is the designated owner for the final Go/No-Go decision if replication lag exceeds the 5-minute freeze window?

    Next steps

    1. Add a checksum or row-count comparison step to the cutover.md runbook.
    2. Verify source database postgresql.conf settings for replication compatibility.
    3. Define the specific rollback procedure for the 15-minute post-cutover window.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Storage Migration Readiness Review is a bounded ToolForge Labs workflow. Review storage migrations across databases, object stores, filesystems, caches, indexes, replicas, exports/imports, validation, cutover, rollback, reconciliation, and operational ownership. Works from supplied evidence or workspace files such as documents, logs, configuration, diffs, architecture notes, test summaries, and rollout materials. Produces evidence-backed findings, readiness gaps, risk framing, and practical next actions while preserving existing product/security policy. The skill separates verified facts from assumptions, avoids invented execution claims, and highlights what remains unverified or requires follow-up outside supplied evidence.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for DevOps & Cloud.

    Cannot verify production systems, external services, or facts that are not present in supplied evidence. With partial context it returns bounded diagnosis/review, explicit assumptions, and a deterministic validation plan rather than claiming successful execution.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 2 months ago

    Permissions

    Terminal / Shell
    Read Files
    Write Files

    Use a clean branch or a controlled review workspace. Supply repository files, logs, traces, configuration, or evidence needed for the task. Review all patches/findings before merge or operational action; keep production credentials and destructive production actions out of the workflow.

    Listed2 months ago
    Updated9 days ago

    What's inside

    Frequently Asked Questions

    This skill analyzes your migration documentation, configs, and test logs to identify technical gaps and risks in your cutover plans, rollback strategies, and data reconciliation processes. It ensures your team hasn't overlooked critical operational details before you flip the switch.

    It is designed for ToolForge Labs workflows and is compatible with major AI agents that support file-based context, allowing it to process your architectural notes, database diffs, and validation logs directly.

    The skill accepts a wide range of inputs including database schemas, migration configuration files, infrastructure-as-code snippets, test execution summaries, and export/import logs.

    You receive the full ToolForge Labs workflow template, including the logic for evidence-backed finding generation, risk framing, and the automated 'Verified vs. Assumption' reporting structure.

    No, the skill is designed to operate within your existing environment's security policies, acting as a passive reviewer of supplied evidence without requiring direct write-access to your production databases.

    The skill explicitly highlights unverified claims and marks items as 'Assumptions' if they aren't backed by your provided logs or docs, ensuring you know exactly what still needs manual validation.

    New in DevOps & Cloud