Agent skill

Glance Test

Run E2E browser tests on any web application using Glance MCP.

MITAuto-check passedTesting & QA

Install Glance Test

skills CLI

$ npx skills add DebugBase/glance --skill glance-test -a claude-code

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

GitHub CLI

$ gh skill install DebugBase/glance glance-test --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/DebugBase/glance.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/glance-test .claude/skills/glance-test && 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/

Paste into Claude Code

Install the "glance-test" agent skill from https://github.com/DebugBase/glance/tree/main/skills/glance-test into .claude/skills/glance-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "glance-test", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/DebugBase/glance/tree/main/skills/glance-test

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add DebugBase/glance --skill glance-test -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install DebugBase/glance glance-test --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/DebugBase/glance.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/glance-test .agents/skills/glance-test && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "glance-test" agent skill from https://github.com/DebugBase/glance/tree/main/skills/glance-test into .agents/skills/glance-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "glance-test", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add DebugBase/glance --skill glance-test -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install DebugBase/glance glance-test --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/DebugBase/glance.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/glance-test .cursor/skills/glance-test && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "glance-test" agent skill from https://github.com/DebugBase/glance/tree/main/skills/glance-test into .cursor/skills/glance-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "glance-test", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/DebugBase/glance.git --path skills/glance-test

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add DebugBase/glance --skill glance-test -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install DebugBase/glance glance-test --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/DebugBase/glance.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/glance-test .gemini/skills/glance-test && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "glance-test" agent skill from https://github.com/DebugBase/glance/tree/main/skills/glance-test into .gemini/skills/glance-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "glance-test", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install DebugBase/glance glance-test

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add DebugBase/glance --skill glance-test -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/DebugBase/glance.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/glance-test .github/skills/glance-test && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "glance-test" agent skill from https://github.com/DebugBase/glance/tree/main/skills/glance-test into .github/skills/glance-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "glance-test", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add DebugBase/glance --skill glance-test -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install DebugBase/glance glance-test --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/DebugBase/glance.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/glance-test .opencode/skills/glance-test && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "glance-test" agent skill from https://github.com/DebugBase/glance/tree/main/skills/glance-test into .opencode/skills/glance-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "glance-test", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: glance-test
GitHub stars: 156
Token cost: ~827 tokens
SKILL.md length: 241 words
Files: 1
Skills in repo: 1
Repo updated: Apr 16, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Run E2E browser tests on any web application using Glance MCP.

Works in 8 steps: Get the target → Start session and navigate → Initial assessment → …
The user says test this page
SKILL.md covers Prerequisites, Workflow, Assertion Quick Reference and Tips
Calls claude

What it does

Glance Test is an agent skill from DebugBase/glance. Run E2E browser tests on any web application using Glance MCP. Use when the user says "test this page," "check this URL," "run E2E tests," "browser test," "test the login flow," "check if the site works," "visual regression," or "screenshot this page." Also use for post-deploy verification and smoke tests.

Its SKILL.md is about 830 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, covering End-to-end testing, QA and bug reports and MCP servers. It works with Model Context Protocol and Playwright. The repository describes itself as: AI-powered browser automation MCP server for Claude Code. Navigate, click, screenshot, test — all from your terminal. The licence is MIT.

When your agent uses it

The user says test this page
Test the login flow
Check if the site works
Visual regression

Example prompts

“test this page,”
“check this URL,”
“run E2E tests,”
“/glance-test”

Requirements

Node.js

Workflow steps

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

Get the target
Start session and navigate
Initial assessment
Smart page discovery
Test each page
Test forms and auth
Generate report
End session

What it can do on your machine

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

Glance Test loads about 827 tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 241 words of instructions outside code blocks.

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

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 DebugBase/glance at commit f90a62c, republished under its MIT licence (© DebugBase). 241 words, ~827 tokens.

Download SKILL.mdSave it as .claude/skills/glance-test/SKILL.md (or your agent's skills folder).

name: glance-test
description: Run E2E browser tests on any web application using Glance MCP. Use when the user says "test this page," "check this URL," "run E2E tests," "browser test," "test the login flow," "check if the site works," "visual regression," or "screenshot this page." Also use for post-deploy verification and smoke tests.
metadata.version: 1.0.0

Glance E2E Browser Test

You run end-to-end browser tests using Glance MCP tools. You have a real Chromium browser at your disposal.

Prerequisites

Glance MCP must be configured. If mcp__browser__browser_navigate is not available, tell the user:

claude mcp add glance -- npx glance-mcp

Workflow

1. Get the target

Ask for the URL if not provided. Accept:

Full URL: https://example.com
Local: localhost:3000
Relative paths (prepend the known base URL)

2. Start session and navigate

mcp__browser__session_start — name: "e2e-{domain}"
mcp__browser__browser_navigate — url

3. Initial assessment

mcp__browser__browser_screenshot — see the page
mcp__browser__browser_snapshot — get DOM structure
mcp__browser__browser_console_messages — check for JS errors

4. Smart page discovery

From the snapshot, identify:

Navigation links (sidebar, header, footer)
Forms (login, register, contact, search)
CTAs (buttons, links)
Interactive elements (dropdowns, modals, tabs)

5. Test each page

For every discoverable page, run:

navigate → screenshot → assert key elements → check console → check network

Use test_scenario_run for multi-step flows:

json

{
  "name": "Page: /login",
  "steps": [
    {"name": "Navigate", "action": "navigate", "url": "URL"},
    {"name": "Page loaded", "action": "assert", "type": "exists", "selector": "h1"},
    {"name": "Screenshot", "action": "screenshot", "screenshotName": "page-name"},
    {"name": "No console errors", "action": "assert", "type": "consoleNoErrors"}
  ]
}

6. Test forms and auth

If login/register forms exist:

Test with invalid data (expect error message)
Test with valid data if credentials provided
Verify redirects and session persistence

7. Generate report

Output a markdown table:

| Page | Steps | Pass | Fail | Issues |
|------|-------|------|------|--------|
| /    | 5     | 5    | 0    | None   |
| /login | 8  | 7    | 1    | Console error: ... |

Include:

Total pages tested
Total steps: X pass, Y fail
Screenshots of failures
Console errors found
Network failures
Bugs discovered with severity

8. End session

mcp__browser__session_end

Assertion Quick Reference

Type	Use for
`exists`	Element present
`notExists`	Element absent
`textContains`	Partial text match
`textEquals`	Exact text
`urlContains`	URL check after navigation
`isVisible`	Visibility check
`isEnabled`	Button/input enabled
`consoleNoErrors`	Zero JS errors

Tips

browser_click accepts plain text: "Sign in", "Submit", "Next"
Always screenshot before and after form submissions
Check browser_network_requests after login to verify API calls
Use visual_baseline + visual_compare for regression testing
Set BROWSER_HEADLESS=false for the user to watch live

Files

Just SKILL.md in skills/glance-test of DebugBase/glance.

Open the folder on GitHubat commit f90a62c

Compare with similar skills

Glance Test 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.

Glance Test compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Glance Test this skillDebugBase/glance	156	—	~827	Automated safety check: Pass	MIT	5 mo ago
Playwright Testingchongdashu/vibejam-starter-pack	149	—	~2.2k	Automated safety check: Pass	None	5 mo ago
Agentic Browser Testingpetrkindlmann/qa-skills	163	—	~4.5k	Automated safety check: Pass	MIT	3 mo ago
Open BrowserJasonHonKL/Openbrowser	114	—	~1.6k	Automated safety check: Pass	MIT	5 mo ago
Windows QA EngineerCodeAlive-AI/ai-driven-development	155	—	~1.4k	Automated safety check: Pass	MIT	yesterday
Playwright Expertcin12211/orca-q	223	—	~1.3k	Automated safety check: Pass	MIT	16 days ago

Similar skills

Playwright Testing
chongdashu/vibejam-starter-pack
Plan, implement, and debug frontend tests: unit/integration/E2E/visual/a11y.
149 GitHub stars~2.2k tokensUpdated 5 mo ago
Testing & QAAuto-check passed
Agentic Browser Testing
petrkindlmann/qa-skills
Goal-driven E2E testing where a browser agent (Playwright MCP / computer-use) reads a natural-language goal and explores the app via the accessibility tree to assert outcomes — no pre-written script.
163 GitHub stars~4.5k tokensUpdated 3 mo ago
Testing & QAAuto-check passed
Open Browser
JasonHonKL/Openbrowser
A skill your agent uses whenever the task involves browsing web pages, extracting page content, clicking forms, or completing web workflows.
114 GitHub stars~1.6k tokensUpdated 5 mo ago
Testing & QAAuto-check passed
Windows QA Engineer
CodeAlive-AI/ai-driven-development
A skill your agent uses when testing Windows 11 desktop apps (WinForms/WPF/UWP) via UFO UIA/Win32 automation MCP.
155 GitHub stars~1.4k tokensUpdated yesterday
Testing & QAAuto-check passed
Playwright Expert
cin12211/orca-q
Playwright E2E testing expert for browser automation, cross-browser testing, visual regression, network interception, and CI integration.
223 GitHub stars~1.3k tokensUpdated 16 days ago
Testing & QAAuto-check passed
Playwright MCP Browser Control
Hainrixz/editor-pro-max
Drives a live browser through the Playwright MCP server to navigate, inspect, fill forms and screenshot pages, with snapshot-first habits and output-size care.
260 GitHub stars~2k tokensUpdated 6 mo ago
Testing & QAAuto-check passed

Works with

Questions about Glance Test

What does Glance Test do?

Run E2E browser tests on any web application using Glance MCP. Glance Test is an agent skill from DebugBase/glance. Run E2E browser tests on any web application using Glance MCP.

When should I use Glance Test?

Glance Test fits situations like: the user says test this page; test the login flow; check if the site works; visual regression.

How do I install Glance Test in Claude Code?

Run `npx skills add DebugBase/glance --skill glance-test -a claude-code`. Or copy the skill folder (skills/glance-test in DebugBase/glance) into .claude/skills/glance-test in your project. Claude Code loads it when a task matches its description.

How do I install Glance Test in Codex?

Run `npx skills add DebugBase/glance --skill glance-test -a codex`. Or copy the skill folder (skills/glance-test in DebugBase/glance) into .agents/skills/glance-test in your project. Codex loads it when a task matches its description.

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

What does Glance Test need to run?

Going by SKILL.md and its folder, Glance Test needs the command-line tools its instructions call (claude). Our summary lists: Node.js.

Does Glance Test 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 Glance Test 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 Glance Test use?

Glance Test 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 Glance Test use?

About 827 tokens (SKILL.md is roughly 3.3k 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 Glance Test?

Skills that share tags, products or a category with Glance Test: Playwright Testing (chongdashu/vibejam-starter-pack, 149 stars), Agentic Browser Testing (petrkindlmann/qa-skills, 163 stars), Open Browser (JasonHonKL/Openbrowser, 114 stars) and Windows QA Engineer (CodeAlive-AI/ai-driven-development, 155 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Glance Test?

DebugBase (a GitHub organization) maintains it in DebugBase/glance, which has 156 GitHub stars. The repository was last updated on April 16, 2026.

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

Install Glance Test

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Glance E2E Browser Test

Prerequisites

Workflow

1. Get the target

2. Start session and navigate

3. Initial assessment

4. Smart page discovery

5. Test each page

6. Test forms and auth

7. Generate report

8. End session

Assertion Quick Reference

Tips

Files

Compare with similar skills

Similar skills

Playwright Testing

Agentic Browser Testing

Open Browser

Windows QA Engineer

Playwright Expert

Playwright MCP Browser Control

Related

Questions about Glance Test