New: 97,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

Plan

by MigoXLab in MigoXLab/webqa-agent

Decompose a task into steps with completion checkpoints. An agent skill from MigoXLab/webqa-agent.

Apache-2.0Auto-check passedTesting & QA

Install Plan

skills CLI
$ npx skills add MigoXLab/webqa-agent --skill plan -a claude-code

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

GitHub CLI
$ gh skill install MigoXLab/webqa-agent plan --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/MigoXLab/webqa-agent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/webqa_agent/executor/flash/skills/plan .claude/skills/plan && 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
plan
GitHub stars
232
Token cost
~1k tokens
SKILL.md length
548 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
Apache-2.0

At a glance

Decompose a task into steps with completion checkpoints. An agent skill from MigoXLab/webqa-agent.

  • Works in 3 steps: Understand the Objective → Sequence the Steps → Place Completion Checkpoints
  • Testing & QA work in your project
  • SKILL.md covers When to Use, Planning Phases, Observation Batching and Multi-Tab Workflows, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Plan is an agent skill from MigoXLab/webqa-agent. Decompose a task into steps with completion checkpoints.

Its SKILL.md is about 1k 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 Testing & QA. The repository describes itself as: Autonomous web browser agent that audits performance, functionality & UX for engineers and vibe-coding creators. 网站自主评估测试 Agent，支持 GUI/CLI 一键完成性能、功能使用与交互体验的测试评估. The licence is Apache-2.0.

When your agent uses it

  • Testing & QA work in your project

Example prompts

  • “/plan”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Understand the Objective
  2. Sequence the Steps
  3. Place Completion Checkpoints

What it can do on your machine

Read from SKILL.md and the folder at commit aa156d4. 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

    No scripts in the folder and no shell commands in SKILL.md.

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

  • Network

    No URLs in SKILL.md.

    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

Plan loads about 1k tokens when it runs. Until then it costs about 15 tokens; SKILL.md has 548 words of instructions outside code blocks.

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

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 MigoXLab/webqa-agent at commit aa156d4, republished under its Apache-2.0 licence (© MigoXLab). 548 words, ~1,043 tokens.

Download SKILL.mdSave it as .claude/skills/plan/SKILL.md (or your agent's skills folder).
name
plan
description
Decompose a task into steps with completion checkpoints.
when_to_use
For multi-step workflows or broad testing objectives.

Plan Skill

Structure your approach before acting. Decompose broad objectives into sequenced steps with completion criteria at key milestones.

When to Use

  • The task describes a multi-step workflow (login, search, checkout, etc.)
  • The objective is broad ("test fundamental functionalities")
  • You are unfamiliar with the page structure
  • The task involves state that carries across steps (form data, cart items)

Skip this skill for single-action tasks ("click the login button").

Planning Phases

Phase 1: Understand the Objective
  • What is the end goal? What does success look like?
  • Which pages/features are involved? Ignore unrelated ones.
  • What data flows through the workflow? (e.g., search query -> results -> detail page)
Phase 2: Sequence the Steps

Order steps as a continuous workflow, each following from the previous outcome.

  • Aim for 4-8 steps for substantial tasks, fewer for simple ones. Each step is one reasoning unit — typically 1-3 tool calls that achieve a single sub-goal.
  • Use semantic intent, not element selectors:
    • Good: "Click the 'Submit' button below the form"
    • Bad: "Click element #btn_47" or "Click at coordinates (400, 300)"
  • For each step, state what and why:
    • Good: "Enter a search query to test the search flow"
    • Bad: "Type 'hello world' in the search box"
  • Mark dependencies between steps: if step 4 depends on data from step 2's outcome, say so explicitly.
    • Example: "Step 4 uses the product name found in step 2's results"
Phase 3: Place Completion Checkpoints

Insert a checkpoint every 3-5 steps at key milestones.

For each checkpoint, define what to verify (the completion condition), not how to verify it:

  • Good: "Verify: search results page loaded with matching items"
  • Bad: "take_snapshot and check for a results container"

The completion condition answers: what state proves this milestone was reached? The execution cycle (system prompt Step 4) handles the how.

Merge multiple conditions into one checkpoint to reduce round-trips:

  • Good: one checkpoint verifying title + items + no error state
  • Bad: separate checkpoints for each
Show full SKILL.md (233 more words)Show less

Observation Batching

The engine runs read-only tools concurrently. Batch independent observations in a single turn for efficiency:

Turn N (one LLM response, all run in parallel):
  - take_snapshot    -> DOM structure
  - take_screenshot  -> visual state
  - list_console_messages -> JS errors
  - list_network_requests -> failed API calls

Use this pattern at completion checkpoints for a comprehensive view without extra round-trips.

Multi-Tab Workflows

You have full tab management. Use it when beneficial:

  • Preserve state: Open a link in a new tab (new_page) to inspect it without losing the current page's form state.
  • Compare pages: Keep the original open, navigate the new tab, then select_page back to compare.
  • Clean up: close_page when a tab is no longer needed.

Re-planning

The plan is a living document, not a fixed script. When execution reveals new information that invalidates the plan:

  • The original page structure differs from expectations.
  • A step's outcome opens a different path than planned.
  • A step is blocked and must be skipped.

Revise the remaining steps based on what you now know. Do not force the original plan when reality has diverged.

Completion

When the objective is fully achieved, stop executing even if you planned more steps. Remaining steps that add no new information are waste. State clearly what was accomplished and why remaining steps are unnecessary.

Do not loop after completion. Do not retry successful actions.

Error Handling

When a tool returns an error or an action produces unexpected results, load the recovery skill for structured guidance: load_skill(skill_name="recovery")

The recovery skill provides error classification, diagnosis with progress assessment, and concrete recovery strategies with escalation.

© MigoXLab, Apache-2.0. 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 webqa_agent/executor/flash/skills/plan of MigoXLab/webqa-agent.

Open the folder on GitHubat commit aa156d4

Compare with similar skills

Plan 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.

Plan compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Plan this skillMigoXLab/webqa-agent232—~1kAutomated safety check: PassApache-2.0
Web Application Testinganthropics/skills180k51 repos~966Automated safety check: PassApache-2.0
Diagnosing Bugsfossasia/eventyay-interpretation1.6k31 repos~2.1kAutomated safety check: PassApache-2.0
TDDfossasia/eventyay-interpretation1.6k28 repos~1.1kAutomated safety check: PassApache-2.0
TDD WorkflowhellangleZ/burn-in-cceverywhere-ralph11211 repos~2.4kAutomated safety check: PassNone
TDDsanity-io/sanity6.4k20 repos~1kAutomated safety check: PassMIT

Similar skills

  • Web Application Testing

    anthropics/skills

    Official

    Tests local web applications with Python Playwright scripts, checking frontend behavior, capturing screenshots and reading browser console logs.

    180k GitHub starsUsed in 51 repos~966 tokens
    Testing & QAAuto-check passed

  • Diagnosing Bugs

    fossasia/eventyay-interpretation

    Diagnosis loop for hard bugs and performance regressions. An agent skill from fossasia/eventyay-interpretation.

    1.6k GitHub starsUsed in 31 repos~2.1k tokens
    Testing & QAAuto-check passed

  • TDD

    fossasia/eventyay-interpretation

    Test-driven development. An agent skill from fossasia/eventyay-interpretation.

    1.6k GitHub starsUsed in 28 repos~1.1k tokens
    Testing & QAAuto-check passed

  • TDD Workflow

    hellangleZ/burn-in-cceverywhere-ralph

    A skill your agent uses when writing new features, fixing bugs, or refactoring code.

    112 GitHub starsUsed in 11 repos~2.4k tokens
    Testing & QAAuto-check passed

  • TDD

    sanity-io/sanity

    Official

    Test-driven development with red-green-refactor loop. An agent skill from sanity-io/sanity.

    6.4k GitHub starsUsed in 20 repos~1k tokens
    Testing & QAAuto-check passed

  • Context Driven Development

    Ibrahim-3d/orchestrator-supaconductor

    A skill your agent uses when working with Conductor's context-driven development methodology, managing project context artifacts, or understanding the relationship between product.md, tech-stack.md…

    380 GitHub starsUsed in 8 repos~2.9k tokens
    Testing & QAAuto-check passed

More from MigoXLab/webqa-agent

  • UI Audit

    MigoXLab/webqa-agent

    UI audit for hierarchy, accessibility, and UX. An agent skill from MigoXLab/webqa-agent.

    232 GitHub stars~1.3k tokensUpdated 3 mo ago
    Auto-check passed

  • Button Check

    MigoXLab/webqa-agent

    Traverse all interactive elements on the page — click clickables, fill inputs — and verify no errors.

    232 GitHub stars~2.2k tokensUpdated 3 mo ago
    Auto-check passed

  • Nuclei Scan

    MigoXLab/webqa-agent

    Run a Nuclei security scan against the target URL and report findings by severity.

    232 GitHub stars~846 tokensUpdated 3 mo ago
    Auto-check passed

  • Recovery

    MigoXLab/webqa-agent

    Structured error recovery for failed or ineffective browser actions.

    232 GitHub stars~1.1k tokensUpdated 3 mo ago
    Auto-check passed

  • Webqa

    MigoXLab/webqa-agent

    Use WebQA to test websites, web pages, URLs, login flows, search flows, forms, navigation, and core user journeys with an AI browser QA agent.

    232 GitHub stars~394 tokensUpdated 3 mo ago
    Auto-check passed

Categories

Questions about Plan

What does Plan do?

Decompose a task into steps with completion checkpoints. An agent skill from MigoXLab/webqa-agent. Plan is an agent skill from MigoXLab/webqa-agent. Decompose a task into steps with completion checkpoints.

When should I use Plan?

Plan fits situations like: testing & QA work in your project.

How do I install Plan in Claude Code?

Run `npx skills add MigoXLab/webqa-agent --skill plan -a claude-code`. Or copy the skill folder (webqa_agent/executor/flash/skills/plan in MigoXLab/webqa-agent) into .claude/skills/plan in your project. Claude Code loads it when a task matches its description.

How do I install Plan in Codex?

Run `npx skills add MigoXLab/webqa-agent --skill plan -a codex`. Or copy the skill folder (webqa_agent/executor/flash/skills/plan in MigoXLab/webqa-agent) into .agents/skills/plan in your project. Codex loads it when a task matches its description.

Can I use Plan 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 MigoXLab/webqa-agent --skill plan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/plan, .gemini/skills/plan, .github/skills/plan and .opencode/skills/plan in your project.

What does Plan need to run?

SKILL.md names no scripts, command-line tools or credentials: Plan is instructions for the agent only.

Does Plan access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Plan 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 Plan use?

Plan is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Plan use?

About 1k tokens (SKILL.md is roughly 4.2k 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 Plan?

Skills that share tags, products or a category with Plan: Web Application Testing (anthropics/skills, 180k stars), Diagnosing Bugs (fossasia/eventyay-interpretation, 1.6k stars), TDD (fossasia/eventyay-interpretation, 1.6k stars) and TDD Workflow (hellangleZ/burn-in-cceverywhere-ralph, 112 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Plan?

MigoXLab (a GitHub organization) maintains it in MigoXLab/webqa-agent, which has 232 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on July 2, 2026.

Source: MigoXLab/webqa-agent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.