Launch and drive this project's app to see a change working.

CC0-1.0Auto-check passedTesting & QA

Install Run

skills CLI
$ npx skills add asgeirtj/system_prompts_leaks --skill run -a claude-code

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

GitHub CLI
$ gh skill install asgeirtj/system_prompts_leaks run --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/asgeirtj/system_prompts_leaks.git skills-src && mkdir -p .claude/skills && cp -r skills-src/Anthropic/claude-code/skills/run .claude/skills/run && 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
run
GitHub stars
69k
Token cost
~898 tokens
SKILL.md length
408 words
Files
7
Skills in repo
124
Repo updated
First seen
Licence
CC0-1.0

At a glance

Launch and drive this project's app to see a change working.

  • Screenshot the app
  • SKILL.md covers First: does a project skill…, Otherwise: match the shape,… and Drive it, don't just launch it
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Confirm a change works in the real app (not just tests)

What it does

Run is an agent skill from asgeirtj/system_prompts_leaks. Launch and drive this project's app to see a change working. Use when asked to run, start, or screenshot the app, or to confirm a change works in the real app (not just tests). First looks for a project skill that already covers launching the app; otherwise falls back to built-in patterns per project type (CLI, server, TUI, Electron, browser-driven, library).

Its SKILL.md is about 900 tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files (for example `examples/cli.md`, `examples/electron.md` and `examples/library.md`).

It sits in Testing & QA. It works with Playwright. The repository describes itself as: Documented system prompts from Anthropic - Claude Fable 5.1, Opus 5.5, Claude Design, Claude Code. OpenAI - ChatGPT GPT-6-Astra, Codex. Google - Gemini 3.8 Flash, 3.1 Pro… The licence is CC0-1.0.

When your agent uses it

  • Screenshot the app
  • Confirm a change works in the real app (not just tests)

Example prompts

  • “/run”

What it can do on your machine

Read from SKILL.md and the folder at commit e31ec21. 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 (its code samples are bash).

    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

Run loads about 898 tokens when it runs. Until then it costs about 91 tokens; SKILL.md has 408 words of instructions outside code blocks.

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

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 asgeirtj/system_prompts_leaks at commit e31ec21, republished under its CC0-1.0 licence (© asgeirtj). 408 words, ~898 tokens.

Download SKILL.mdSave it as .claude/skills/run/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.
name
run
description
Launch and drive this project's app to see a change working. Use when asked to run, start, or screenshot the app, or to confirm a change works in the real app (not just tests). First looks for a project skill that already covers launching the app; otherwise falls back to built-in patterns per project type (CLI, server, TUI, Electron, browser-driven, library).

Running means launching the actual app and interacting with it - not the test suite, not an import of an internal function and a console.log. The app as a user (human or programmatic) would meet it: the CLI at its command, the server at its socket, the GUI at its window.

First: does a project skill already cover this?

A project skill that launches this app is the repo's verified path - its author already cold-started from a Linux container and committed what worked: the exact apt-get line, the env vars, the patches, the driver. Use it instead of rediscovering.

bash
d=$PWD; while :; do
  grep -Hm1 '^description:' "$d"/.claude/skills/*/SKILL.md 2>/dev/null
  [ -e "$d/.git" ] || [ "$d" = / ] && break
  d=$(dirname "$d")
done
  • One describes launching/driving this app -> read that SKILL.md and follow it verbatim. Don't paraphrase; don't skip the patches.
  • Mega-repo, several plausible, no clear match -> ask the user which unit to run.
  • Stale (fails on mechanics unrelated to your task) -> tell the user; offer to refresh it via /run-skill-generator.
  • Nothing about running -> fall back to the patterns below.

Otherwise: match the shape, use the pattern

Pick the row closest to your project. Each example walks through launch + first interaction; ignore any trailing "write the skill" section - you're using the recipe, not authoring one.

Project typeHandleExample
CLI tooldirect invocation, exit code, stdin/stdoutexamples/cli.md
Web server / APIbackground launch + curl smokeexamples/server.md
TUI / interactive terminaltmux send-keys / capture-paneexamples/tui.md
Electron / desktop GUIPlaywright _electron REPL under xvfbexamples/electron.md
Browser-drivendev server + chromium-cli scriptexamples/playwright.md
Library / SDKimport-and-call smoke script at the package boundaryexamples/library.md

If nothing fits, start from the closest match and adapt. For a web app, examples/playwright.md - drive it with chromium-cli, no custom driver needed. For a desktop app, examples/electron.md - it has the _electron REPL driver skeleton and the tmux wrapping.

Show full SKILL.md (127 more words)Show less

Drive it, don't just launch it

Launching with no interaction proves the entrypoint resolves. That's not running the app - it's typechecking with extra steps. Drive it to a point where a user would see something:

  • CLI -> type a representative command, check the exit code and output.
  • Server -> hit the route the diff touches with curl, read the body.
  • TUI -> send-keys a navigation, capture-pane the result.
  • GUI -> click the button, screenshot the window. Look at the screenshot. A blank frame is a failure to launch.

If the fallback pattern didn't work out of the box - you had to install packages, set env vars, patch config, or write a driver - recommend /run-skill-generator in your report so that work gets captured as a project skill. If it just worked, don't.

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

Files

SKILL.md and 6 other files in Anthropic/claude-code/skills/run of asgeirtj/system_prompts_leaks.

  • SKILL.md
  • examples/cli.md
  • examples/electron.md
  • examples/library.md
  • examples/playwright.md
  • examples/server.md
  • examples/tui.md

Open the folder on GitHubat commit e31ec21

Compare with similar skills

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

Run compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Run this skillasgeirtj/system_prompts_leaks69k—~898Automated safety check: PassCC0-1.0
Web Application Testinganthropics/skills180k51 repos~966Automated safety check: PassApache-2.0
Playwright CLIsanity-io/sanity6.4k18 repos~1.9kAutomated safety check: PassMIT
Write and Verify Playwright Testsappsmithorg/appsmith41k—~2.9kAutomated safety check: NotesApache-2.0
playwright-cli Browser Automationgithub/gh-aw5.4k23 repos~2.8kAutomated safety check: PassMIT
Cucumber and Playwright E2E Testslanggenius/dify158k—~682Automated safety check: PassCustom licence

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
  • Playwright CLI

    sanity-io/sanity

    Official

    Automates browser interactions for web testing, form filling, screenshots, and data extraction.

    6.4k GitHub starsUsed in 18 repos~1.9k tokens
    Testing & QAAuto-check passed
  • Writes a Playwright end-to-end test from a prompt, runs it against a live Appsmith deployment and retries with fixes up to three times until it passes.

    41k GitHub stars~2.9k tokensUpdated yesterday
    Testing & QAAuto-check: notes
  • Official

    Drives a real browser from the command line with playwright-cli to open pages, interact, mock requests, save state and work with Playwright tests.

    5.4k GitHub starsUsed in 23 repos~2.8k tokens
    Testing & QAAuto-check passed
  • Guides changes and reviews of the Cucumber and Playwright end-to-end suite under `e2e/`: feature files, step definitions, support code, tags, locators and assertions.

    158k GitHub stars~682 tokensUpdated today
    Testing & QAAuto-check passed
  • Verify Openhands

    OpenHands/OpenHands

    This skill should be used to "verify OpenHands features", "test the Canvas UI like a user", "drive Agent Canvas", "check a UI change in the real app", "create or update the feature map", "run the…

    90k GitHub stars~3.4k tokensUpdated today
    Testing & QAAuto-check passed

More from asgeirtj/system_prompts_leaks

All 124 skills in this repo
  • Fleet Manager for Agent Sessions

    asgeirtj/system_prompts_leaks

    Shows one digest of coding-agent sessions across your connected machines and lets you open, read, steer, approve, stop and close them, over Herdr, tmux or MSP.

    69k GitHub stars~2.5k tokensUpdated yesterday
    Auto-check passed
  • Muse Code Product Doctor

    asgeirtj/system_prompts_leaks

    Diagnoses a Muse Code installation's own failures from binary and session evidence, instead of treating the report as an ordinary repository bug.

    69k GitHub stars~3.5k tokensUpdated yesterday
    Auto-check passed
  • DOCX

    asgeirtj/system_prompts_leaks

    A skill your agent uses whenever the user wants to create, read, edit, or manipulate Word documents (.docx) or Word templates (.dotx).

    69k GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed
  • Agents Project Coordinator

    asgeirtj/system_prompts_leaks

    Runs a goal as a project in which the agent coordinates separate agent threads, judging when to split the work, and interviews you first when nothing can be verified.

    69k GitHub stars~2.9k tokensUpdated yesterday
    Auto-check passed
  • Muse Plugin Creator

    asgeirtj/system_prompts_leaks

    Creates and validates a new native Muse plugin package in the current workspace, limited to five capability families, and leaves installation to you.

    69k GitHub stars~1.8k tokensUpdated yesterday
    Auto-check passed
  • Deep Research

    asgeirtj/system_prompts_leaks

    A skill your agent uses when the user's prompt requires (1) researching a topic across multiple sources, comparing options or alternatives, analyzing trends or history, understanding markets or…

    69k GitHub stars~3.3k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Run

What does Run do?

Launch and drive this project's app to see a change working. Run is an agent skill from asgeirtj/system_prompts_leaks. Launch and drive this project's app to see a change working.

When should I use Run?

Run fits situations like: screenshot the app; confirm a change works in the real app (not just tests).

How do I install Run in Claude Code?

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

How do I install Run in Codex?

Run `npx skills add asgeirtj/system_prompts_leaks --skill run -a codex`. Or copy the skill folder (Anthropic/claude-code/skills/run in asgeirtj/system_prompts_leaks) into .agents/skills/run in your project. Codex loads it when a task matches its description.

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

What does Run need to run?

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

Does Run 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 Run 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 Run use?

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

How many tokens does Run use?

About 898 tokens (SKILL.md is roughly 3.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 Run?

Skills that share tags, products or a category with Run: Web Application Testing (anthropics/skills, 180k stars), Playwright CLI (sanity-io/sanity, 6.4k stars), Write and Verify Playwright Tests (appsmithorg/appsmith, 41k stars) and playwright-cli Browser Automation (github/gh-aw, 5.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Run?

asgeirtj (a GitHub user) maintains it in asgeirtj/system_prompts_leaks, which has 69,211 GitHub stars. The repository holds 124 skills in this directory. The repository was last updated on October 8, 2026.

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