Hire an AI website issue and test readiness reviewer

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• A research order that says what to check first and why, with a tracking check up front
• A ranked audit of the page, quick wins first, with a score out of 100
• Every problem sorted into fix now, investigate, test or tracking, in order of likely gain
• A clear yes or no on whether your traffic can prove a test, and how many weeks it needs

How it does the job well

• Write for one named audience and one action. Each asset has a single job.
• Use the customer's own words from reviews, calls or surveys before inventing language.
• Every claim needs proof the business can show. Leave unproven claims out or mark them.
• Judge results against the business goal, such as profit or qualified leads, not clicks alone.

Mistakes it avoids

• Generic copy that could fit any brand.
• Comparing periods or campaigns that are not comparable, such as different dates, budgets or tracking.
• Calling a test winner before there is enough data.

What a good result looks like

An example, not your task: Your page gets visits but few people buy, sign up or book, and you do not know what to fix first.

• Research plan. The order to work in: tracking check first, where people drop, pages to review, customer questions and an issue template.
• Page audit. What a glance and a skim tell a buyer, ranked fixes with quick wins first, and a score out of 100.
• Sorted problems. Each problem tagged tracking, fix now, investigate or test, ranked by likely gain and effort.
• Test check. The smallest lift worth finding, weeks needed, a yes or no verdict and rules for running the test.
• HAND-BACK SUMMARY. Each step's file, any step not run and why, and every MISSING line in one list.

How the work is checked

• Tracking faults come first, before any test idea.
• Every issue has the proof for it, not just an opinion.
• Step 4 sized only the problems step 3 tagged "test".
• The test check gives numbers and a plain verdict, and says so if the person cannot test yet.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

A second opinion

Before it hands back, your AI reviews the draft the way Peep Laja and Jakob Nielsen would. This is a way of reviewing the work. It does not mean they wrote or endorse it.

Capabilities

• Plan the research. Writes the order to work in, from checking your tracking to finding where people drop and asking why they hesitate.
• Audit the page. Reads the page like a stranger would, after the research is done, and ranks what to fix with quick wins first.
• Sort the problems. Takes the audit and tags each problem as tracking, fix now, investigate or test, then ranks by likely gain and effort.
• Check your traffic. Takes your visits and conversions and says whether a test can finish in a sensible time, with the rules for running it.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id page-problems-test-picks only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/page-problems-test-picks/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• The address or saved copy of the page (optional for the first step, needed for the audit)
• Your analytics, with visits, steps and sales or sign-ups by page
• Customer words from reviews, chats or surveys (optional)
• Your brand file or a note on your offer, proof and buyer doubts (optional)
• Time to do the research the plan lists (a few days to a few weeks)
• Your visits and conversions for the page you want to test, pulled after the research

Tools and access

• Any good chat AI: Planning an order of research is text work any strong chat AI does with this skill.
• Google Analytics: Free. Shows pages, steps and where people leave. Export visits per step before you start.
• A session replay tool: Optional and often paid, and it needs an account and a snippet on your site. Lets you watch real visits to a page.
• Any good chat AI: Any current chat AI that reads screenshots can run the three reads. Give it phone screenshots, top to bottom.
• PageSpeed Insights: Shows your page's real-user speed against Google's 'good' marks, so the phone check has numbers.
• Evan Miller's sample size calculator: Tells you how many visitors a test needs, so you know if it can finish in about a month.
• Any good chat AI: Sorting and ranking a list with reasons is text work any strong chat AI does with this skill.
• A spreadsheet or task board: Holds the ranked list and tracks what is done.
• Any good chat AI: The sums are simple, and the main chat AIs all show their working when asked.
• Google Sheets: Keeps each month's numbers in one place, so you can check every sum and compare with your own past.
• Evan Miller's sample size calculator: Free, and a quick second check on the visitors per version.

Functions and deliverables

• Website issue and test readiness reviewer: Share page evidence, analytics and customer feedback. Get a research plan, ranked issues and a check of whether traffic supports testing.
  • A research order that says what to check first and why, with a tracking check up front
  • A ranked audit of the page, quick wins first, with a score out of 100
  • Every problem sorted into fix now, investigate, test or tracking, in order of likely gain
  • A clear yes or no on whether your traffic can prove a test, and how many weeks it needs
• Conversion research planner: Plan your conversion research before you test. Paste your page and analytics. You get an order that finds where people drop and why.
  • A research order with the question each step answers
  • A tracking check to run first
  • A plan for replays, user tests and surveys
  • A template for writing findings as issues
• Landing page conversion reviewer: Share your page and screenshots. Get conversion problems ranked by impact, with recommended fixes and a score.
  • The page's job, a one-line verdict, and whether the page matches its ad
  • What a buyer takes from a five-second glance and from a skim
  • A ranked findings table, each with a severity from 0 to 4 and where it sits
  • Up to five quick wins, up to three tests, and what the page can't tell you
  • A page score out of 100 worked out from the severities, now and after the quick wins
• Page issue sorter: Sort a long list of page problems into fix now, investigate, test or tracking, then rank them. Get a clear plan for your page issue list.
  • Each issue in one bucket with its reason
  • Test ideas written as: change, expected effect, why
  • A ranked order by likely gain and effort
  • A list of issues dropped for lack of proof
• A/B test traffic checker: Check if your site has enough visitors for an A/B test. Paste visits, orders and revenue to get the weeks needed and a readiness score out of 100.
  • A numbers table with conversion rate, average order value and revenue per visitor, each sum shown
  • A short read of what moved and what the traffic mix explains
  • The test sizing written out, with visitors and weeks needed
  • A verdict (can test, test a bolder change, or ship and watch) and three next actions
  • A test readiness score out of 100, showing how much of the needed sample your traffic reaches in four weeks
• Brand profile builder: Share your website. Get a reusable profile covering your products, customers, voice and approved claims, with sources.
  • A folder of eight plain files, from a start file for your AI to a claims list and a change log
  • A tag on every fact, and every claim marked approved, pending or banned
  • A two-sentence diagnosis of your biggest gap, and a list of what's missing and who can answer it
  • A short slice for your next step, if you name one
• Peep Laja: Review page messaging or an A/B test using Peep Laja’s recorded approach. Start with buyer evidence, clarity and a sound comparison plan.
  • Your problem worked on the way Peep Laja would: their questions, their method, their push-back
  • The answer or the work, in Peep Laja's voice, using their ideas by name
  • Anything that goes beyond their public record, marked
  • One suggested next step
• Jakob Nielsen: Review a website, app or form through Jakob Nielsen’s recorded approach. Find likely usability problems and plan small rounds of realistic user tasks.
  • Your problem worked on the way Jakob Nielsen would: their questions, their method, their push-back
  • The answer or the work, in Jakob Nielsen's voice, using their ideas by name
  • Anything that goes beyond their public record, marked
  • One suggested next step

Tasks you can use it for

• Your page gets visits but few people buy, sign up or book, and you do not know what to fix first.
• You have a list of changes you want to test and need to know which ones deserve the traffic you have.
• Someone says to run an A/B test and you want to know if your numbers can support one.

Limits to check before starting

• Your page has no traffic yet: set up basic analytics first, then come back once visits are coming in.
• You only want the page scored before launch: use the Landing page conversion reviewer.
• You only want to know if your traffic can support a test: use the A/B test traffic checker.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Download the handoff pack. It's a zip with HANDOFF.md and every skill file this workflow uses.
• Give the folder to Claude (in Claude Code, or as files in a Claude Project) and say "Follow HANDOFF.md".
• Share your page and analytics. It writes the research plan and stops.
• Do the research the plan lists, such as the analytics check, a walk-through of the page and a few customer questions. Then say "carry on".
• Pull your visits and orders for the page you want to test when it asks, so the last step can size the test.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/page-problems-test-picks for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.