Agent skill

Slay Browser

by debuglebowski in debuglebowski/slayzone

Control the task browser panel via the slay CLI. An agent skill from debuglebowski/slayzone.

GPL-3.0Auto-check passed

Install Slay Browser

skills CLI
$ npx skills add debuglebowski/slayzone --skill slay-browser -a claude-code

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

GitHub CLI
$ gh skill install debuglebowski/slayzone slay-browser --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/debuglebowski/slayzone.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/slay-browser .claude/skills/slay-browser && 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
slay-browser
GitHub stars
191
Token cost
~963 tokens
SKILL.md length
552 words
Files
1
Skills in repo
16
Repo updated
First seen
Licence
GPL-3.0

At a glance

Control the task browser panel via the slay CLI. An agent skill from debuglebowski/slayzone.

  • Works in 4 steps: navigate to the URL → content to inspect the page and find… → click or type to interact → …
  • SKILL.md covers Global flags, Commands, Targeting notes and Workflow tips
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Slay Browser is an agent skill from debuglebowski/slayzone. Control the task browser panel via the slay CLI

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

The licence is GPL-3.0.

Example prompts

  • “/slay-browser”

Workflow steps

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

  1. navigate to the URL
  2. content to inspect the page and find selectors
  3. click or type to interact
  4. screenshot to capture the result

What it can do on your machine

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

Slay Browser loads about 963 tokens when it runs. Until then it costs about 15 tokens; SKILL.md has 552 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
~963

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 debuglebowski/slayzone at commit e912716, republished under its GPL-3.0 licence (© debuglebowski). 552 words, ~963 tokens.

Download SKILL.mdSave it as .claude/skills/slay-browser/SKILL.md (or your agent's skills folder).
name
slay-browser
description
Control the task browser panel via the slay CLI
trigger
auto

Browser commands control the browser panel embedded in each task's detail view. All commands require $SLAYZONE_TASK_ID to be set (automatic in task terminals).

Global flags

  • --panel <state> — visible or hidden. navigate defaults to visible (auto-opens the panel); all other commands default to hidden (operate without showing the panel).
  • --tab <idOrIdx> — target a specific tab. Accepts a 0-based index (e.g. --tab 1) or an opaque tab id (e.g. --tab default). Pure-digit values are treated as indices and resolved via slay tasks browser tabs. Without --tab, commands target the currently active tab.

Commands

  • slay tasks browser tabs [--json] — list browser tabs for the current task.

    • Output columns: active | idx | id | title | url. The active tab is marked with *.
    • Tabs that haven't been loaded yet are marked (not loaded) — they exist in the task's saved state but their WebContentsView hasn't mounted (typically because the panel is closed).
  • slay tasks browser new [url] [--panel <state>] [--background] [--json] — create a new browser tab.

    • Defaults to --panel visible (auto-opens the panel) and switches to the new tab.
    • --background adds the tab without switching focus away from the active tab.
    • Without url, the tab opens about:blank.
    • Prints <idx>: <tabId> <url> (or full JSON with --json). Use the returned id with --tab for follow-up commands.
  • slay tasks browser navigate <url> [--panel <state>] [--tab <idOrIdx>] — navigate the targeted tab to a URL.

    • The only command that auto-shows the browser panel.
    • With --tab, the panel auto-opens and switches to that tab before loading the URL.
  • slay tasks browser url [--panel <state>] [--tab <idOrIdx>] — print the targeted tab's current URL.

  • slay tasks browser screenshot [-o <path>] [--panel <state>] [--tab <idOrIdx>] — capture a screenshot of the targeted tab.

    • Returns the file path of the saved image.
    • -o copies the screenshot to a specific path; without it, prints the temp file path.
  • slay tasks browser content [--json] [--panel <state>] [--tab <idOrIdx>] — get the targeted tab's text content and interactive elements as JSON.

    • Text content truncated to 10k characters.
    • Interactive elements include links, buttons, and inputs.
  • slay tasks browser click <selector> [--panel <state>] [--tab <idOrIdx>] — click an element on the targeted tab by CSS selector.

    • Returns the tag name and text of the clicked element.
  • slay tasks browser type <selector> <text> [--panel <state>] [--tab <idOrIdx>] — type text into an input on the targeted tab by CSS selector.

  • slay tasks browser eval <code> [--panel <state>] [--tab <idOrIdx>] — execute JavaScript in the targeted tab's context and print the result.

    • Strings are printed as-is.
    • Other values are pretty-printed as JSON.
Show full SKILL.md (139 more words)Show less

Targeting notes

  • Default target = the currently active tab. Existing scripts without --tab keep working.
  • When a --tab value cannot be resolved, the server returns 404 with the available tabs listed for discovery. The CLI also prints the available tabs when an index lookup fails.
  • A --tab reference by index can shift if the user reorders or closes tabs. For long-lived scripts that need a stable reference, use the opaque tab id (printed by slay tasks browser tabs).

Workflow tips

A typical browser verification flow:

  1. navigate to the URL
  2. content to inspect the page and find selectors
  3. click or type to interact
  4. screenshot to capture the result

For multi-tab flows, use slay tasks browser new <url> to spawn additional tabs, then pass the printed tab id (or the index from tabs) via --tab to subsequent commands.

© debuglebowski, GPL-3.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 .agents/skills/slay-browser of debuglebowski/slayzone.

Open the folder on GitHubat commit e912716

Compare with similar skills

Slay Browser 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.

Slay Browser compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Slay Browser this skilldebuglebowski/slayzone191—~963Automated safety check: PassGPL-3.0
CLI Anything Slay The Spire IiHKUDS/CLI-Anything52k—~1.4kAutomated safety check: PassApache-2.0
Panel Databrycewang-stanford/Auto-Empirical-Research-Skills4.5k—~2.6kAutomated safety check: PassCustom licence
Expert Panelericosiu/ai-marketing-skills3.6k2 repos~2.1kAutomated safety check: PassMIT
Investor Panel Stock Reviewwbh604/UZI-Skill7.1k—~757Automated safety check: PassMIT
Illustration Framed PanelMengTo/Skills6.6k—~5.5kAutomated safety check: PassMIT

Similar skills

  • Command-line interface for Slay the Spire 2 - Control the real game through a local bridge mod HTTP API.

    52k GitHub stars~1.4k tokensUpdated 16 days ago
    Backend & APIsAuto-check passed
  • Panel Data

    brycewang-stanford/Auto-Empirical-Research-Skills

    Econometrics skill for panel data models. An agent skill from brycewang-stanford/Auto-Empirical-Research-Skills.

    4.5k GitHub stars~2.6k tokensUpdated 2 days ago
    Research & ScienceAuto-check passed
  • Expert Panel

    ericosiu/ai-marketing-skills

    Score, evaluate, and iteratively improve any content or strategy using an auto-assembled panel of domain experts.

    3.6k GitHub starsUsed in 2 repos~2.1k tokens
    Frontend & DesignAuto-check passed
  • Scores a stock through a panel of well-known investor personas, each applying their own method and returning a structured signal, then tallies the votes.

    7.1k GitHub stars~757 tokensUpdated 1 mo ago
    Business, Finance & HRAuto-check passed
  • Draws original design-and-coding scenes as SVG cards (480x360) in a framed-panel cartoon style.

    6.6k GitHub stars~5.5k tokensUpdated yesterday
    Frontend & DesignAuto-check passed
  • Panel

    akseolabs-seo/AK-Threads-booster

    Launch or prepare the optional local visual panel for AK-Threads-Booster.

    275 GitHub stars~873 tokensUpdated 3 mo ago
    Writing & ContentAuto-check: notes

More from debuglebowski/slayzone

All 16 skills in this repo
  • Comparison Page

    debuglebowski/slayzone

    Create or update objective website comparison pages and head-to-head pages from the comparison canon.

    191 GitHub stars~1.2k tokensUpdated 1 mo ago
    Auto-check passed
  • Slay Artifacts

    debuglebowski/slayzone

    Manage task artifacts (files, folders) via the slay CLI. An agent skill from debuglebowski/slayzone.

    191 GitHub stars~1.6k tokensUpdated 1 mo ago
    Auto-check passed
  • Slay Automations

    debuglebowski/slayzone

    Create and manage automations via the slay CLI. An agent skill from debuglebowski/slayzone.

    191 GitHub stars~627 tokensUpdated 1 mo ago
    Auto-check passed
  • Slay Orchestrate

    debuglebowski/slayzone

    Supervise a set of slay tasks through planning, execution, and verification

    191 GitHub stars~1.3k tokensUpdated 1 mo ago
    Auto-check passed
  • Slay Context

    debuglebowski/slayzone

    Ensure root instruction files include SlayZone environment context

    191 GitHub stars~448 tokensUpdated 1 mo ago
    Auto-check passed
  • Slay Pty

    debuglebowski/slayzone

    Interact with PTY terminal sessions via the slay CLI. An agent skill from debuglebowski/slayzone.

    191 GitHub stars~916 tokensUpdated 1 mo ago
    Auto-check passed

Questions about Slay Browser

What does Slay Browser do?

Control the task browser panel via the slay CLI. An agent skill from debuglebowski/slayzone. Slay Browser is an agent skill from debuglebowski/slayzone.

How do I install Slay Browser in Claude Code?

Run `npx skills add debuglebowski/slayzone --skill slay-browser -a claude-code`. Or copy the skill folder (.agents/skills/slay-browser in debuglebowski/slayzone) into .claude/skills/slay-browser in your project. Claude Code loads it when a task matches its description.

How do I install Slay Browser in Codex?

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

Can I use Slay Browser 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 debuglebowski/slayzone --skill slay-browser -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/slay-browser, .gemini/skills/slay-browser, .github/skills/slay-browser and .opencode/skills/slay-browser in your project.

What does Slay Browser need to run?

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

Does Slay Browser 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 Slay Browser 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 Slay Browser use?

Slay Browser is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Slay Browser use?

About 963 tokens (SKILL.md is roughly 3.9k 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 Slay Browser?

Skills that share tags, products or a category with Slay Browser: CLI Anything Slay The Spire Ii (HKUDS/CLI-Anything, 52k stars), Panel Data (brycewang-stanford/Auto-Empirical-Research-Skills, 4.5k stars), Expert Panel (ericosiu/ai-marketing-skills, 3.6k stars) and Investor Panel Stock Review (wbh604/UZI-Skill, 7.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Slay Browser?

debuglebowski (a GitHub user) maintains it in debuglebowski/slayzone, which has 191 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on September 3, 2026.

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