New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Request Indexing UX Replay

by harlan-zw in harlan-zw/requestindexing.com

Replay Request Indexing onboarding as a new user on the web dashboard and through a coding agent, capture every page and state, check the onboarding mail, and fix material defects.

MITAuto-check passedDevelopment

Install Request Indexing UX Replay

skills CLI
$ npx skills add harlan-zw/requestindexing.com --skill request-indexing-ux-replay -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install harlan-zw/requestindexing.com request-indexing-ux-replay --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/harlan-zw/requestindexing.com.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/request-indexing-ux-replay .claude/skills/request-indexing-ux-replay && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
request-indexing-ux-replay
GitHub stars
396
Token cost
~1.9k tokens
SKILL.md length
1,197 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
MIT

At a glance

Replay Request Indexing onboarding as a new user on the web dashboard and through a coding agent, capture every page and state, check the onboarding mail, and fix material defects.

  • Works in 7 steps: Read AGENTS.md, VISION.md, GLOSSARY.md,… → Read… → Record the production commit from gh run… → …
  • Launch rehearsals
  • SKILL.md covers Start each replay, The test identity, Persona A: web dashboard and Persona B: agent, plus 5 more sections
  • Calls gh and pnpm; reaches requestindexing.com and gscdump.com

What it does

Request Indexing UX Replay is an agent skill from harlan-zw/requestindexing.com. Replay Request Indexing onboarding as a new user on the web dashboard and through a coding agent, capture every page and state, check the onboarding mail, and fix material defects. Use for launch rehearsals, first-user tests, or repeat onboarding checks.

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. The repository describes itself as: Find your missing on pages Google and request them to be indexed using the Web Search Indexing API. The licence is MIT.

When your agent uses it

  • Launch rehearsals
  • First-user tests
  • Repeat onboarding checks

Example prompts

  • “/request-indexing-ux-replay”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Read AGENTS.md, VISION.md, GLOSSARY.md, and COPY.md. Read DESIGN.md before a UI fix.
  2. Read layers/pro-gsc/shared/developer-setup.ts. It holds the agent setup prompt and the Developers page steps.
  3. Record the production commit from gh run list --workflow "Deploy to Cloudflare" --branch main --limit 1.
  4. Record the gscdump CLI version from pnpm dlx @gscdump/cli@latest --version.
  5. Confirm 4 facts with the user: the test Google identity, the browser profile signed in to it, the inbox that gets its mail, and whether…
  6. Make a dated note ~/notes/requestindexing-ux-replay-YYYY-MM-DD.md. Put screenshots beside it. Put scratch output in ~/scratch/ri-replay/.
  7. Never record secrets, OAuth codes, raw API keys, or private query data.

What it can do on your machine

Read from SKILL.md and the folder at commit 81644c0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh
    • pnpm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • requestindexing.com
    • gscdump.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Request Indexing UX Replay loads about 1.9k tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 1,197 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~70
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from harlan-zw/requestindexing.com at commit 81644c0, republished under its MIT licence (© harlan-zw). 1,197 words, ~1,907 tokens.

Download SKILL.mdSave it as .claude/skills/request-indexing-ux-replay/SKILL.md (or your agent's skills folder).
name
request-indexing-ux-replay
description
Replay Request Indexing onboarding as a new user on the web dashboard and through a coding agent, capture every page and state, check the onboarding mail, and fix material defects. Use for launch rehearsals, first-user tests, or repeat onboarding checks.

Request Indexing UX replay

Ported from gscdump's gscdump-ux-replay and nuxtseo.com's agent-dogfood. This app hosts no CLI, MCP server, or agent skill. The agent path is gscdump's CLI, skill, and MCP server, signed in with a key this app issues. VISION.md and docs/arch/README.md say why.

Run the product as a new user. Record what they see before you read the code. A command that exits zero does not pass the test. A useful result passes it.

Start each replay

  1. Read AGENTS.md, VISION.md, GLOSSARY.md, and COPY.md. Read DESIGN.md before a UI fix.
  2. Read layers/pro-gsc/shared/developer-setup.ts. It holds the agent setup prompt and the Developers page steps.
  3. Record the production commit from gh run list --workflow "Deploy to Cloudflare" --branch main --limit 1.
  4. Record the gscdump CLI version from pnpm dlx @gscdump/cli@latest --version.
  5. Confirm 4 facts with the user: the test Google identity, the browser profile signed in to it, the inbox that gets its mail, and whether another replay uses that identity now.
  6. Make a dated note ~/notes/requestindexing-ux-replay-YYYY-MM-DD.md. Put screenshots beside it. Put scratch output in ~/scratch/ri-replay/.
  7. Never record secrets, OAuth codes, raw API keys, or private query data.

The test identity

One Google account is one gscdump user. gscdump.com signs in a partner-created user as the same user, so both products share it. A deletion on either side changes the other.

  • Run one replay per identity at a time. If a gscdump replay uses the identity, wait until it ends.
  • Between attempts, delete the account on the Account page. The deletion is part of the path under test.
  • After a deletion, confirm that sign-in starts a new signup and onboarding. If old Sites or keys come back, record a finding.

Persona A: web dashboard

Goal: a new person signs up, completes onboarding, connects a Site, and learns whether a page is indexed and why.

  1. Start signed out at https://requestindexing.com/. Capture the landing page at desktop width and at 390px.
  2. Sign up with Google. Record each redirect and each consent screen.
  3. Complete onboarding. Capture each step. Record any step that asks for a choice the person cannot make yet.
  4. Connect a Site. Use the least sensitive Site the identity owns. Capture the Search Console property list. If the identity owns no property, capture the empty state. Check that it says why and what to do next.
  5. Watch the first sync from queued to complete. Sample the early, middle, and final states. Compare the visible progress with gscdump lifecycle data when you can read it.
  6. Open Overview, Indexing, Sitemaps, and one URL. Reload each page once to catch first-render errors. Check the sidebar.
  7. Answer the job. Pick one URL that is not indexed. Capture whether the product says why and what to do.
  8. If the Site allows it, Submit one eligible URL. Record what the UI claims. A Submission is a notification Google accepted. It never proves that the page is indexed.
  9. Delete the account. Capture the confirmation and the signed-out result.

Persona B: agent

Goal: the same person gets an indexing answer inside a coding agent, with no docs.

  1. Sign in, open Developers, and click Copy agent setup prompt. Capture the page before and after.
  2. Check that every command in the copied prompt exists in the current CLI. Use --help, never memory.
  3. Give the prompt to a sub-agent with an isolated HOME under ~/scratch/ri-replay/agent-home. The sub-agent follows the prompt only. It does not read this repository or the gscdump source.
  4. Record each command, its exit code, and its duration. The run passes only when it ends with an indexing summary for a connected Site. If the identity has no Site, the run passes when the agent says so clearly and names the next step.
  5. Check the MCP path once. Add https://gscdump.com/mcp with the key in the x-api-key header, list the tools, and call one read tool.
  6. Check the Claude.ai connector path once. It signs in at gscdump.com with the same Google account. Confirm that it shows the same Sites. If it shows a waitlist or no Sites, record a finding.
  7. Revoke the key on Developers. Confirm that the CLI and MCP now fail with a clear error.
Show full SKILL.md (490 more words)Show less

Mail

Check the inbox of the identity after signup, after the first sync, and at each onboarding email step.

  • Record the sender, subject, time after signup, and every link target.
  • Open each link signed out and signed in.
  • Each onboarding email has an unsubscribe link. Click it, capture the result page, and confirm that the next step does not send.
  • If a test needs an email sooner than its schedule, ask before you change a schedule in production.

Capture evidence

For each transition, log the time, persona, action, expected result, actual result, URL or command, and evidence file. Capture loading states, loaded states, empty states, and errors. Capture desktop width and 390px when layout matters.

Use dev-browser with a unique page name for each persona. Close every page at the end. Never run dev-browser stop. If $DISPLAY is empty, pass --headless. Google refuses sign-in in a new automated profile. For steps that need Google, connect to the user's own Chrome with dev-browser --connect. If you cannot connect, ask the user for the one browser action and continue the other checks.

Orchestrate, review, fix

  • The orchestrator keeps the note and the findings table. Each sub-agent walks one persona and returns screenshots and a transition log.
  • A reviewer reads each screenshot before the next attempt. It asks whether the issue changes a choice, hides progress, blocks a result, or costs real time. Skip polish with no concrete effect.
  • For a material defect, record the smallest failing path. Fix the cause in a task-owned wt worktree. Add a behaviour test when the fix changes logic. Open a PR and follow AGENTS.md.
  • A UI change to a signed-in route needs a deploy preview. No authenticated page renders locally without credentials.
  • A defect in the gscdump CLI, skill, MCP server, or engine gets a PR in the gscdump repository. Never add a workaround here.
  • Keep operations failures apart from product UX. Do not turn the replay into a backlog sweep.
  • After a fix deploys, run the failing step again on production. Keep the screenshots from before and after.

Bring in the user's run

If the user walks the path too, add their observations as they arrive. After the fixes are live, give the user the note link and this prompt:

Start at requestindexing.com in your normal browser. Tell me where you paused, guessed, waited, or saw a result you did not trust. Send rough notes or screenshots.

Add a Your walkthrough section to the same note. Keep the user's words beside the agent observation. For each difference, record whether it reproduces, its cause, and the fix or the reason to skip. Never claim that the user's pass happened.

Report

The note holds a short result, a Mermaid path diagram, a timed workflow table, screenshots with relative links, and a findings table with evidence and disposition.

Give the user a three-line summary and https://notes.localhost/notes/<note-name>. State end-to-end confidence from observed behaviour. Name each path that stays untested.

© harlan-zw, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/request-indexing-ux-replay of harlan-zw/requestindexing.com.

Open the folder on GitHubat commit 81644c0

Compare with similar skills

Request Indexing UX Replay next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Request Indexing UX Replay compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Request Indexing UX Replay this skillharlan-zw/requestindexing.com396—~1.9kAutomated safety check: PassMIT
Vercel Composition Patternssupabase/supabase111k58 repos~726Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
Typescript Advanced Typesrolling-scopes/rsschool-app10k25 repos~4.2kAutomated safety check: PassMPL-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k4 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • Vercel Composition Patterns

    supabase/supabase

    Official

    React composition patterns that scale. An agent skill from supabase/supabase.

    111k GitHub starsUsed in 58 repos~726 tokens
    DevelopmentAuto-check passed

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Typescript Advanced Types

    rolling-scopes/rsschool-app

    Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.

    10k GitHub starsUsed in 25 repos~4.2k tokens
    DevelopmentAuto-check passed

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 4 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed

More from harlan-zw/requestindexing.com

  • Nuxt Auth Utils Skilld

    harlan-zw/requestindexing.com

    ALWAYS use when writing code importing "nuxt-auth-utils". An agent skill from harlan-zw/requestindexing.com.

    396 GitHub stars~1.8k tokensUpdated today
    Auto-check passed

  • Nuxt Og Image Skilld

    harlan-zw/requestindexing.com

    ALWAYS use when writing code importing "nuxt-og-image". An agent skill from harlan-zw/requestindexing.com.

    396 GitHub stars~2.4k tokensUpdated today
    Auto-check passed

  • Nuxt Skilld

    harlan-zw/requestindexing.com

    ALWAYS use when writing code importing "nuxt". An agent skill from harlan-zw/requestindexing.com.

    396 GitHub stars~2.4k tokensUpdated today
    Auto-check passed

  • Nuxt UI Skilld

    harlan-zw/requestindexing.com

    ALWAYS use when writing code importing "@nuxt/ui". An agent skill from harlan-zw/requestindexing.com.

    396 GitHub stars~2.4k tokensUpdated today
    Auto-check passed

Categories

Questions about Request Indexing UX Replay

What does Request Indexing UX Replay do?

Replay Request Indexing onboarding as a new user on the web dashboard and through a coding agent, capture every page and state, check the onboarding mail, and fix material defects. com. Replay Request Indexing onboarding as a new user on the web dashboard and through a coding agent, capture every page and state, check the onboarding mail, and fix material defects.

When should I use Request Indexing UX Replay?

Request Indexing UX Replay fits situations like: launch rehearsals; first-user tests; repeat onboarding checks.

How do I install Request Indexing UX Replay in Claude Code?

Run `npx skills add harlan-zw/requestindexing.com --skill request-indexing-ux-replay -a claude-code`. Or copy the skill folder (.claude/skills/request-indexing-ux-replay in harlan-zw/requestindexing.com) into .claude/skills/request-indexing-ux-replay in your project. Claude Code loads it when a task matches its description.

How do I install Request Indexing UX Replay in Codex?

Run `npx skills add harlan-zw/requestindexing.com --skill request-indexing-ux-replay -a codex`. Or copy the skill folder (.claude/skills/request-indexing-ux-replay in harlan-zw/requestindexing.com) into .agents/skills/request-indexing-ux-replay in your project. Codex loads it when a task matches its description.

Can I use Request Indexing UX Replay in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add harlan-zw/requestindexing.com --skill request-indexing-ux-replay -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/request-indexing-ux-replay, .gemini/skills/request-indexing-ux-replay, .github/skills/request-indexing-ux-replay and .opencode/skills/request-indexing-ux-replay in your project.

What does Request Indexing UX Replay need to run?

Going by SKILL.md and its folder, Request Indexing UX Replay needs the command-line tools its instructions call (gh and pnpm).

Does Request Indexing UX Replay access the network?

SKILL.md names 2 domains. In commands or code: requestindexing.com and gscdump.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Request Indexing UX Replay safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Request Indexing UX Replay use?

Request Indexing UX Replay is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Request Indexing UX Replay use?

About 1.9k tokens (SKILL.md is roughly 7.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Request Indexing UX Replay?

Skills that share tags, products or a category with Request Indexing UX Replay: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 297k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Request Indexing UX Replay?

harlan-zw (a GitHub user) maintains it in harlan-zw/requestindexing.com, which has 396 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 11, 2026.

Source: harlan-zw/requestindexing.com on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.