Moav E2E
MotherofallVPNs/MoaV
Run and debug MoaV's end-to-end tests — real protocol connectivity (client-test.sh) and the moav CLI smoke test — against a LIVE server, via the self-hosted e2e workflow or a local test VPS.
Use after Phase 1 dependency updates are merged, before any Phase 2 propagation to sibling forks - runs the end-to-end devnet gate (up brings devnet/deploy/dev-server up, verify drives Chrome over…
Install Stark Smoke Test
$ npx skills add Scaffold-Stark/scaffold-stark-2 --skill stark-smoke-test -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Scaffold-Stark/scaffold-stark-2 stark-smoke-test --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Scaffold-Stark/scaffold-stark-2.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/stark-smoke-test .claude/skills/stark-smoke-test && rm -rf skills-srcUse ~/.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/
Install the "stark-smoke-test" agent skill from https://github.com/Scaffold-Stark/scaffold-stark-2/tree/main/.claude/skills/stark-smoke-test into .claude/skills/stark-smoke-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stark-smoke-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 install https://github.com/Scaffold-Stark/scaffold-stark-2/tree/main/.claude/skills/stark-smoke-testType 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.
$ npx skills add Scaffold-Stark/scaffold-stark-2 --skill stark-smoke-test -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Scaffold-Stark/scaffold-stark-2 stark-smoke-test --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Scaffold-Stark/scaffold-stark-2.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/stark-smoke-test .agents/skills/stark-smoke-test && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "stark-smoke-test" agent skill from https://github.com/Scaffold-Stark/scaffold-stark-2/tree/main/.claude/skills/stark-smoke-test into .agents/skills/stark-smoke-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stark-smoke-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.
$ npx skills add Scaffold-Stark/scaffold-stark-2 --skill stark-smoke-test -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Scaffold-Stark/scaffold-stark-2 stark-smoke-test --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Scaffold-Stark/scaffold-stark-2.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/stark-smoke-test .cursor/skills/stark-smoke-test && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "stark-smoke-test" agent skill from https://github.com/Scaffold-Stark/scaffold-stark-2/tree/main/.claude/skills/stark-smoke-test into .cursor/skills/stark-smoke-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stark-smoke-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 https://github.com/Scaffold-Stark/scaffold-stark-2.git --path .claude/skills/stark-smoke-test--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Scaffold-Stark/scaffold-stark-2 --skill stark-smoke-test -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Scaffold-Stark/scaffold-stark-2 stark-smoke-test --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Scaffold-Stark/scaffold-stark-2.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/stark-smoke-test .gemini/skills/stark-smoke-test && rm -rf skills-srcUse ~/.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/
Install the "stark-smoke-test" agent skill from https://github.com/Scaffold-Stark/scaffold-stark-2/tree/main/.claude/skills/stark-smoke-test into .gemini/skills/stark-smoke-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stark-smoke-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.
$ gh skill install Scaffold-Stark/scaffold-stark-2 stark-smoke-testInstalls 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).
$ npx skills add Scaffold-Stark/scaffold-stark-2 --skill stark-smoke-test -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Scaffold-Stark/scaffold-stark-2.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/stark-smoke-test .github/skills/stark-smoke-test && rm -rf skills-srcUse ~/.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/
Install the "stark-smoke-test" agent skill from https://github.com/Scaffold-Stark/scaffold-stark-2/tree/main/.claude/skills/stark-smoke-test into .github/skills/stark-smoke-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stark-smoke-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.
$ npx skills add Scaffold-Stark/scaffold-stark-2 --skill stark-smoke-test -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Scaffold-Stark/scaffold-stark-2 stark-smoke-test --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Scaffold-Stark/scaffold-stark-2.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/stark-smoke-test .opencode/skills/stark-smoke-test && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "stark-smoke-test" agent skill from https://github.com/Scaffold-Stark/scaffold-stark-2/tree/main/.claude/skills/stark-smoke-test into .opencode/skills/stark-smoke-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stark-smoke-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
stark-smoke-test- GitHub stars
- 109
- Token cost
- ~3k tokens
- SKILL.md length
- 1,642 words
- Files
- 3
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- None found
At a glance
Use after Phase 1 dependency updates are merged, before any Phase 2 propagation to sibling forks - runs the end-to-end devnet gate (up brings devnet/deploy/dev-server up, verify drives Chrome over…
- Works in 4 steps: Devnet gate green → Sepolia gate green → PR is merged → …
- Tasks that involve QA and bug reports
- SKILL.md covers Scope, Sepolia gate (opt-in, S1-S5), Commands and Step A — bring the stack up…, plus 4 more sections
- Runs JavaScript scripts from its folder; calls node and yarn
What it does
Stark Smoke Test is an agent skill from Scaffold-Stark/scaffold-stark-2. Use after Phase 1 dependency updates are merged, before any Phase 2 propagation to sibling forks - runs the end-to-end devnet gate (up brings devnet/deploy/dev-server up, verify drives Chrome over raw CDP to exercise the app, run does both plus teardown) and reports a green or red gate.
Its SKILL.md is about 3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files.
It sits in Testing & QA, covering QA and bug reports, Dependency management and End-to-end testing. The repository describes itself as: Open source forkable Starknet dev stack. Codebase of Scaffold Stark.
When your agent uses it
- Tasks that involve QA and bug reports
- Tasks that involve Dependency management
- Tasks that involve End-to-end testing
Example prompts
- “/stark-smoke-test”
Requirements
- Node.js
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Devnet gate green
- Sepolia gate green
- PR is merged
- Phase 2 propagation allowed
What it can do on your machine
Read from SKILL.md and the folder at commit ae1b689. 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
Ships script files (JavaScript), which the agent can run.
Shell commands in SKILL.md call:
nodeyarn
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use yarn, 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 no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Stark Smoke Test loads about 3k tokens when it runs. Until then it costs about 76 tokens; SKILL.md has 1,642 words of instructions outside code blocks.
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: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteMentions a .env fileSKILL.md:75
ent and non-empty in `packages/snfoundry/.env`. Missing → INFRA. This - NoteMentions a .env fileSKILL.md:76
gate **never writes to `.env`** and never offers to — unlike the devnet - NoteMentions a .env fileSKILL.md:149
`packages/snfoundry/.env`) that is a correct, expected result on a fresh - NoteMentions a .env fileSKILL.md:152
`.env` silently — either let them paste it, confirm the prompt, or re-run with
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
Without a licence we can't republish the file, so here is its outline and opening line. It has 1,642 words (~2,960 tokens).
“Prove the stack actually works end-to-end on devnet before propagating anything to sibling forks. A red gate blocks Phase 2.”
- name
- stark-smoke-test
Files
SKILL.md and 2 other files in .claude/skills/stark-smoke-test of Scaffold-Stark/scaffold-stark-2.
- SKILL.md
- stark-smoke-test-browser.mjs
- stark-smoke-test.mjs
Open the folder on GitHubat commit ae1b689
Compare with similar skills
Stark Smoke 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Stark Smoke Test this skillScaffold-Stark/scaffold-stark-2 | 109 | — | ~3k | Automated safety check: Notes | None | |
| Moav E2EMotherofallVPNs/MoaV | 449 | — | ~1.9k | Automated safety check: Notes | MIT | |
| Whole-App Health Sweepreticlehq/reticle | 1.2k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Try In Browserankit/stylebot | 1.6k | — | ~780 | Automated safety check: Pass | MIT | |
| Vss E2E Smokeopen-edge-platform/edge-ai-libraries | 171 | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Testing QAaiskillstore/marketplace | 433 | 3 repos | ~1.2k | Automated safety check: Pass | None |
Similar skills
Whole-App Health Sweep
reticlehq/reticle
Sweeps a running web app by clicking every reachable control, then reports dead buttons, console errors, failed requests and mismatches between API data and the screen.
Try In Browser
ankit/stylebot
Launch Stylebot in a real, headed Chrome window (via yarn dev:chrome) so the user can manually eyeball a change — in whatever checkout the current session is in, worktree or main.
Vss E2E Smoke
open-edge-platform/edge-ai-libraries
Run this skill whenever the user asks to verify my VSS install works, smoke test VSS, check whether the deployment succeeded, or run an end-to-end test of summary/search for the…
Testing QA
aiskillstore/marketplace
Comprehensive testing and QA workflow covering unit testing, integration testing, E2E testing, browser automation, and quality assurance.
QA Engineer
nagisanzenin/production-grade
[production-grade internal] Writes and runs tests when you want to verify code works — unit, integration, e2e, performance, contract testing.
More from Scaffold-Stark/scaffold-stark-2
Stark Cdp With Wallet
Scaffold-Stark/scaffold-stark-2
A skill your agent uses when a task needs a real Braavos wallet driven end-to-end (unlock, connect, approve a transaction) against a live network like Starknet Sepolia, without a human clicking the…
Stark Demo Video
Scaffold-Stark/scaffold-stark-2
A skill your agent uses when asked to record a demo proving scaffold-stark actually works end to end — a terminal take of a real Sepolia deploy gate (Take 1), and/or a browser take of a real Braavos…
Stark Update Phase1
Scaffold-Stark/scaffold-stark-2
Phase 1 — check and update dependencies for scaffold-stark-2 itself (Starknet toolchain, Cairo/OpenZeppelin, starknet.js, Next.js frontend, security advisories).
Stark Sync Phase2
Scaffold-Stark/scaffold-stark-2
Phase 2 — propagate an already-merged scaffold-stark-2 update out to its sibling forks and the create-stark npm template.
Related
Categories
Questions about Stark Smoke Test
What does Stark Smoke Test do?
Use after Phase 1 dependency updates are merged, before any Phase 2 propagation to sibling forks - runs the end-to-end devnet gate (up brings devnet/deploy/dev-server up, verify drives Chrome over…. Stark Smoke Test is an agent skill from Scaffold-Stark/scaffold-stark-2. Use after Phase 1 dependency updates are merged, before any Phase 2 propagation to sibling forks - runs the end-to-end devnet gate (up brings devnet/deploy/dev-server up, verify drives Chrome over raw CDP to exercise the app, run does both plus teardown) and reports a green or red gate.
When should I use Stark Smoke Test?
Stark Smoke Test fits situations like: tasks that involve QA and bug reports; tasks that involve Dependency management; tasks that involve End-to-end testing.
How do I install Stark Smoke Test in Claude Code?
Run `npx skills add Scaffold-Stark/scaffold-stark-2 --skill stark-smoke-test -a claude-code`. Or copy the skill folder (.claude/skills/stark-smoke-test in Scaffold-Stark/scaffold-stark-2) into .claude/skills/stark-smoke-test in your project. Claude Code loads it when a task matches its description.
How do I install Stark Smoke Test in Codex?
Run `npx skills add Scaffold-Stark/scaffold-stark-2 --skill stark-smoke-test -a codex`. Or copy the skill folder (.claude/skills/stark-smoke-test in Scaffold-Stark/scaffold-stark-2) into .agents/skills/stark-smoke-test in your project. Codex loads it when a task matches its description.
Can I use Stark Smoke 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 Scaffold-Stark/scaffold-stark-2 --skill stark-smoke-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/stark-smoke-test, .gemini/skills/stark-smoke-test, .github/skills/stark-smoke-test and .opencode/skills/stark-smoke-test in your project.
What does Stark Smoke Test need to run?
Going by SKILL.md and its folder, Stark Smoke Test needs JavaScript for the scripts in its folder and the command-line tools its instructions call (node and yarn). Our summary lists: Node.js.
Does Stark Smoke 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 Stark Smoke Test safe to install?
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Stark Smoke Test use?
No licence was found for Stark Smoke Test or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Stark Smoke Test use?
About 3k tokens (SKILL.md is roughly 12k 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 Stark Smoke Test?
Skills that share tags, products or a category with Stark Smoke Test: Moav E2E (MotherofallVPNs/MoaV, 449 stars), Whole-App Health Sweep (reticlehq/reticle, 1.2k stars), Try In Browser (ankit/stylebot, 1.6k stars) and Vss E2E Smoke (open-edge-platform/edge-ai-libraries, 171 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Stark Smoke Test?
Scaffold-Stark (a GitHub organization) maintains it in Scaffold-Stark/scaffold-stark-2, which has 109 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on August 3, 2026.
Source: Scaffold-Stark/scaffold-stark-2 on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.