Run a single Node, browser, or Playwright spec instead of the full suite.

GPL-3.0Auto-check passedTesting & QA

Install Run One Spec

skills CLI
$ npx skills add LiberatedPixelCup/Universal-LPC-Spritesheet-Character-Generator --skill run-one-spec -a claude-code

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

GitHub CLI
$ gh skill install LiberatedPixelCup/Universal-LPC-Spritesheet-Character-Generator run-one-spec --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/LiberatedPixelCup/Universal-LPC-Spritesheet-Character-Generator.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/run-one-spec .claude/skills/run-one-spec && 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-one-spec
GitHub stars
1.8k
Token cost
~746 tokens
SKILL.md length
287 words
Files
1
Skills in repo
11
Repo updated
First seen
Licence
GPL-3.0

At a glance

Run a single Node, browser, or Playwright spec instead of the full suite.

  • Debugging one test
  • SKILL.md covers Node (tests/node/), Browser (Testem + Mocha) and Visual (Playwright)
  • Calls npm, node and npx; needs ARGOS_TOKEN
  • Iterating on a failing spec

What it does

Run One Spec is an agent skill from LiberatedPixelCup/Universal-LPC-Spritesheet-Character-Generator. Run a single Node, browser, or Playwright spec instead of the full suite. Use when debugging one test, iterating on a failing spec, or the user asks to run one file, one test, or a filtered suite. Do not start with npm test.

Its SKILL.md is about 750 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 Browser testing. It works with Playwright and npm. The repository describes itself as: Character Generator based on Universal-LPC-Spritesheet. The licence is GPL-3.0.

When your agent uses it

  • Debugging one test
  • Iterating on a failing spec
  • The user asks to run one file
  • A filtered suite

Example prompts

  • “/run-one-spec”

Requirements

  • Node.js
  • A credential in ARGOS_TOKEN

What it can do on your machine

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

    • npm
    • node
    • npx

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

  • Network

    No URLs in SKILL.md. Its commands use npm and npx, which can reach the network depending on how they are called.

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

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • ARGOS_TOKEN

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

Context cost

Run One Spec loads about 746 tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 287 words of instructions outside code blocks.

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

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 LiberatedPixelCup/Universal-LPC-Spritesheet-Character-Generator at commit 58ce1aa, republished under its GPL-3.0 licence (© LiberatedPixelCup). 287 words, ~746 tokens.

Download SKILL.mdSave it as .claude/skills/run-one-spec/SKILL.md (or your agent's skills folder).
name
run-one-spec
description
Run a single Node, browser, or Playwright spec instead of the full suite. Use when debugging one test, iterating on a failing spec, or the user asks to run one file, one test, or a filtered suite. Do not start with npm test.

Run one spec

Pick the suite the file belongs to. Do not start with npm test.

Isolation is below. Coverage is a separate full-suite run — see write-spec after a gated sources/ or scripts/ edit (skip if the path is in codecov.yml ignore:).

Node (tests/node/)

npm run test:node collects every *_spec.js / *_spec.ts and ignores extra args. Call node --test on the file instead:

bash
node --test tests/node/scripts/generateSources/items_spec.ts
node --test --test-name-pattern="parseItem" tests/node/scripts/generateSources/items_spec.ts

npm run test:node:coverage also runs every Node spec, not this file alone.

Browser (Testem + Mocha)

tests/tests.js imports every browser spec. There is no CLI file filter. Do not comment out imports. A spec that is not imported never runs; Codecov patch then fails with no Mocha failure.

Filter with ?grep= (best isolation). Start the server, then open the harness with a grep pattern:

bash
npm run test:server
# then open, in the launched browser:
# http://localhost:7357/tests_run.html?debug=false&grep=CategoryTree

Mocha's browser bundle reads grep, fgrep, and invert from location.search inside mocha.run(), which tests/tests.js calls. Every spec file is still imported, so the filter selects which tests execute, not which files load. The Mocha UI search box does the same thing by rewriting this query string.

If 7357 is busy, testem.cjs reads TESTEM_PORT:

bash
TESTEM_PORT=7360 npm run test:server

it.only / describe.only works locally as a fallback. Do not commit it.

testem.cjs before_tests always runs every Node spec first, including this Chrome-only command. It is still the full Mocha browser suite, not one file:

bash
node ./node_modules/testem/testem.js ci --launch Chrome

npm run test:browser:coverage is that full suite in Chrome and Firefox.

DEBUG=1 (or DEBUG=true) keeps the app's verbose debug output instead of the default ?debug=false.

Visual (Playwright)

npm run test:visual uses Playwright’s webServer (npm run dev locally). npx playwright test with this repo’s config does the same.

bash
npx playwright test tests/visual/home.spec.js
npx playwright test -g "title substring"

Wait for catalog/canvas via tests/visual/home-helpers.ts. Do not register visual specs in tests/tests.js. They are not Codecov-instrumented. Argos upload needs ARGOS_TOKEN. When a change warrants a visual run: visual-test.

© LiberatedPixelCup, 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/run-one-spec of LiberatedPixelCup/Universal-LPC-Spritesheet-Character-Generator.

Open the folder on GitHubat commit 58ce1aa

Compare with similar skills

Run One Spec 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 One Spec compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Run One Spec this skillLiberatedPixelCup/Universal-LPC-Spritesheet-Character-Generator1.8k—~746Automated safety check: PassGPL-3.0
UI Visual DebuggingNangoHQ/nango13k—~1.3kAutomated safety check: PassCustom licence
Debuggingidavidov13/agentic-playwright225—~6.2kAutomated safety check: NotesMIT
PlaywrightKiln-AI/Kiln5.2k—~1.3kAutomated safety check: PassCustom licence
UI Previewtingly-dev/tingly-box351—~2kAutomated safety check: NotesMPL-2.0
Proxy Setupasmyshlyaev177/test-proxy-recorder112—~4.3kAutomated safety check: PassMIT

Similar skills

  • UI Visual Debugging

    NangoHQ/nango

    A skill your agent uses when modifying or visually debugging Nango frontend UI, including packages/webapp, packages/connect-ui, browser interactions, screenshots, and visual regressions.

    13k GitHub stars~1.3k tokensUpdated today
    Testing & QAAuto-check passed
  • Debugging

    idavidov13/agentic-playwright

    Playwright test debugging conventions for the scaffold — reading failure messages, classifying failure modes (TimeoutError, ZodError, strict-mode violation, locator not found, network errors, schema…

    225 GitHub stars~6.2k tokensUpdated yesterday
    Testing & QAAuto-check: notes
  • Playwright

    Kiln-AI/Kiln

    Look at Kiln's UI in a real browser, and run its end-to-end tests.

    5.2k GitHub stars~1.3k tokensUpdated today
    Testing & QAAuto-check passed
  • UI Preview

    tingly-dev/tingly-box

    Capture headless-Chrome screenshots of the tingly-box frontend (running locally in mock mode) so frontend changes can be visually verified in environments without a real browser.

    351 GitHub stars~2k tokensUpdated today
    Testing & QAAuto-check: notes
  • Proxy Setup

    asmyshlyaev177/test-proxy-recorder

    Set up test-proxy-recorder for any Playwright project. An agent skill from asmyshlyaev177/test-proxy-recorder.

    112 GitHub stars~4.3k tokensUpdated today
    Testing & QAAuto-check passed
  • A skill your agent uses when running Playwright tests in this repo (luna.mbt) and either the test fails to discover specs ("did not expect test.describe()" / "two different versions of…

    173 GitHub stars~1.2k tokensUpdated 23 days ago
    Testing & QAAuto-check passed

More from LiberatedPixelCup/Universal-LPC-Spritesheet-Character-Generator

All 11 skills in this repo
  • Cls

    LiberatedPixelCup/Universal-LPC-Spritesheet-Character-Generator

    Measure lab CLS with profile:cls, debug layout shift from loading shells and first-paint jump, and keep budgets tied to a CI artifact.

    1.8k GitHub stars~822 tokensUpdated yesterday
    Auto-check passed
  • Coverage

    LiberatedPixelCup/Universal-LPC-Spritesheet-Character-Generator

    Run and read unit-test coverage for this repo and satisfy the codecov/patch and codecov/changes gates.

    1.8k GitHub stars~1.8k tokensUpdated yesterday
    Auto-check passed
  • Performance Profiling

    LiberatedPixelCup/Universal-LPC-Spritesheet-Character-Generator

    Run the headless app, catalog-load, and ZIP profilers and interpret the JSON the way a human would from window.profiler.report(), profile:load, and the ZIP console table.

    1.8k GitHub stars~1.8k tokensUpdated yesterday
    Auto-check passed
  • Typescript

    LiberatedPixelCup/Universal-LPC-Spritesheet-Character-Generator

    Write TypeScript that satisfies this repo's lint and tsconfig rules, and convert an existing .js file to .ts without breaking its call sites.

    1.8k GitHub stars~1.5k tokensUpdated yesterday
    Auto-check passed
  • Generated Metadata

    LiberatedPixelCup/Universal-LPC-Spritesheet-Character-Generator

    Diagnose missing or stale dist/-metadata.js, the Vite metadata plugin cache, and the ../name-metadata.js import alias.

    1.8k GitHub stars~597 tokensUpdated yesterday
    Auto-check passed
  • Catalog

    LiberatedPixelCup/Universal-LPC-Spritesheet-Character-Generator

    Thread CatalogReader and State through Mithril attrs, never a hidden global.

    1.8k GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed

Works with

Questions about Run One Spec

What does Run One Spec do?

Run a single Node, browser, or Playwright spec instead of the full suite. Run One Spec is an agent skill from LiberatedPixelCup/Universal-LPC-Spritesheet-Character-Generator. Run a single Node, browser, or Playwright spec instead of the full suite.

When should I use Run One Spec?

Run One Spec fits situations like: debugging one test; iterating on a failing spec; the user asks to run one file; A filtered suite.

How do I install Run One Spec in Claude Code?

Run `npx skills add LiberatedPixelCup/Universal-LPC-Spritesheet-Character-Generator --skill run-one-spec -a claude-code`. Or copy the skill folder (.agents/skills/run-one-spec in LiberatedPixelCup/Universal-LPC-Spritesheet-Character-Generator) into .claude/skills/run-one-spec in your project. Claude Code loads it when a task matches its description.

How do I install Run One Spec in Codex?

Run `npx skills add LiberatedPixelCup/Universal-LPC-Spritesheet-Character-Generator --skill run-one-spec -a codex`. Or copy the skill folder (.agents/skills/run-one-spec in LiberatedPixelCup/Universal-LPC-Spritesheet-Character-Generator) into .agents/skills/run-one-spec in your project. Codex loads it when a task matches its description.

Can I use Run One Spec 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 LiberatedPixelCup/Universal-LPC-Spritesheet-Character-Generator --skill run-one-spec -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-one-spec, .gemini/skills/run-one-spec, .github/skills/run-one-spec and .opencode/skills/run-one-spec in your project.

What does Run One Spec need to run?

Going by SKILL.md and its folder, Run One Spec needs the command-line tools its instructions call (npm, node and npx) and credentials named ARGOS_TOKEN. Our summary lists: Node.js; A credential in ARGOS_TOKEN.

Does Run One Spec access the network?

SKILL.md contains no URLs. Its commands use npm and npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Run One Spec 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 One Spec use?

Run One Spec 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 Run One Spec use?

About 746 tokens (SKILL.md is roughly 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 Run One Spec?

Skills that share tags, products or a category with Run One Spec: UI Visual Debugging (NangoHQ/nango, 13k stars), Debugging (idavidov13/agentic-playwright, 225 stars), Playwright (Kiln-AI/Kiln, 5.2k stars) and UI Preview (tingly-dev/tingly-box, 351 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Run One Spec?

LiberatedPixelCup (a GitHub organization) maintains it in LiberatedPixelCup/Universal-LPC-Spritesheet-Character-Generator, which has 1,834 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 7, 2026.

Source: LiberatedPixelCup/Universal-LPC-Spritesheet-Character-Generator on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.