Website Migration QA Pack

    1

    Analyzes website migration evidence to generate coverage matrices, redirect audits, and client acceptance reports.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Website Migration QA Pack

    Example session with this skill installed

    Review this migration CSV containing 50 old/new URL pairs and the attached crawl log. Identify redirect errors and create a coverage matrix for the 2024-10-12 staging build.

    • Read your context and instructions
    • Compiled the website migration qa

    I have reviewed the migration CSV and the crawl log for the 2024-10-12 staging build. I identified 42 verified URL pairs, 5 redirect defects, and 3 unverified paths.

    Migration QA Report: Staging Revision 2024-10-12

    Coverage Matrix

    IDOld URL PathTarget URL PathStatusNotes
    001/about-us/aboutVerifiedContent parity confirmed
    002/products/v1/productsDefectTerminal 404 observed
    003/blog/post-1/news/post-1ApprovedIntentional path change
    004/contact/contact-usUnverifiedMissing from crawl log

    Redirect Findings

    Source URLExpected TargetObserved Hop PathTerminal StatusResult
    /services/our-services301 -> 301 -> /our-services200Verified
    /old-api/api/v2302 -> /login200Defect: Auth redirect
    /shop/store301 -> /store/home404Defect: Broken target

    Required for Reconsideration

    • Fix Redirect 002: Resolve 404 on product landing page.
    • Fix Redirect 005: Ensure /old-api routes to the API endpoint, not the login gate.
    • Evidence Needed: Provide crawl data for /contact to verify the /contact-us target.

    Recommendation:

    Hold for fix. The migration has critical routing defects impacting the product catalog and API access.

    Next steps

    1. Update the .htaccess or redirect map for the flagged 404 paths.
    2. Provide a fresh crawl log once the redirect fixes are deployed to staging.
    3. Confirm if the 302 redirect on /old-api is an intentional security middleware requirement.

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

    About this skill

    Website migrations often fail due to broken redirects, layout regressions, and missing SEO metadata that go unnoticed until after deployment. This skill provides a structured QA framework to audit migration evidence, compare old and new environments, and generate client-ready acceptance reports without the manual overhead of building tracking sheets from scratch.

    What it does

    • Coverage Mapping: Generates a matrix matching old URLs to new targets to identify gaps in the migration scope.
    • Redirect Auditing: Reviews hop statuses and terminal URLs against intended policies to catch routing errors.
    • Defect Classification: Categorizes findings into defects, approved differences, or unverified items based on supplied requirements.
    • Retest Planning: Builds a prioritized queue for developers to fix blockers and for QA to verify those specific revisions.
    • Client Acceptance: Produces a plain-language sheet for stakeholders detailing what was tested and what remains blocked.

    How it works

    1. Supply Evidence: Provide the URL mapping, screenshots, crawl logs, or test results from both the source and target environments.
    2. Review & Compare: The skill analyzes the data to verify parity, identify intended changes, and flag unintended regressions.
    3. Generate Matrix: It builds a stable inventory of URL pairs, including redirect hop paths and status codes.
    4. Triage: It classifies every check to separate "approved design changes" from "functional bugs."

    Frameworks & tools

    This skill works with any text-based evidence, including CSV URL maps, crawl reports from Screaming Frog or Ahrefs, markdown test logs, and structured requirements documents.

    Why this beats prompting it yourself

    Generic prompts often struggle to distinguish between an intentional design change and a layout defect. This skill enforces strict revision binding and evidence-based logic, ensuring you don't accidentally close a bug based on outdated screenshots or incomplete crawl data.

    Use cases

    • SEO Audits: Verifying 301 redirect chains and canonical tags during a domain or platform move.
    • UAT Reporting: Creating a "Ready for Review" summary for a client that excludes optional noise.
    • Regression Testing: Comparing staging builds against production to catch CSS or component breakage.

    Known limitations

    This skill does not crawl URLs or browse live sites directly. It requires manual input of logs, screenshots, or report data as evidence. It does not perform actual form submissions or deployments.

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

    Cannot crawl live URLs or browse websites. Requires logs or reports as input evidence. Does not handle real form submissions or automated browser 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 8 days ago

    Permissions

    Read Files
    Listed8 days ago

    What's inside

    Frequently Asked Questions

    The skill requires text-based migration data, such as URL mapping lists (CSV), crawl logs from tools like Screaming Frog, markdown test logs, or requirements documents to perform its analysis.

    Unlike generic prompts, this skill uses a structured QA framework that enforces revision binding, ensuring the agent doesn't confuse intentional design updates with actual functional defects.

    This skill is designed for use within any LLM interface or AI agent platform that supports long-form text analysis and document processing.

    No, the skill does not have live browsing capabilities; it functions as an analytical layer that processes the evidence and logs you supply from your own testing tools.

    You receive the full logic framework for generating coverage matrices, redirect audits, defect classifications, and client-ready acceptance reports, formatted for immediate use.

    The skill is ideal for SEO audits to verify 301 redirect chains, User Acceptance Testing (UAT) to generate stakeholder reports, and regression testing to catch layout shifts.

    New in Business & Operations