Runtime Debug
vercel/next.js
Debug and verification workflow for runtime-bundle and module-resolution regressions.
Phase 1 — check and update dependencies for scaffold-stark-2 itself (Starknet toolchain, Cairo/OpenZeppelin, starknet.js, Next.js frontend, security advisories).
Install Stark Update Phase1
$ npx skills add Scaffold-Stark/scaffold-stark-2 --skill stark-update-phase1 -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Scaffold-Stark/scaffold-stark-2 stark-update-phase1 --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-update-phase1 .claude/skills/stark-update-phase1 && 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-update-phase1" agent skill from https://github.com/Scaffold-Stark/scaffold-stark-2/tree/main/.claude/skills/stark-update-phase1 into .claude/skills/stark-update-phase1/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stark-update-phase1", 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-update-phase1Type 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-update-phase1 -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Scaffold-Stark/scaffold-stark-2 stark-update-phase1 --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-update-phase1 .agents/skills/stark-update-phase1 && 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-update-phase1" agent skill from https://github.com/Scaffold-Stark/scaffold-stark-2/tree/main/.claude/skills/stark-update-phase1 into .agents/skills/stark-update-phase1/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stark-update-phase1", 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-update-phase1 -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Scaffold-Stark/scaffold-stark-2 stark-update-phase1 --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-update-phase1 .cursor/skills/stark-update-phase1 && 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-update-phase1" agent skill from https://github.com/Scaffold-Stark/scaffold-stark-2/tree/main/.claude/skills/stark-update-phase1 into .cursor/skills/stark-update-phase1/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stark-update-phase1", 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-update-phase1--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-update-phase1 -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Scaffold-Stark/scaffold-stark-2 stark-update-phase1 --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-update-phase1 .gemini/skills/stark-update-phase1 && 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-update-phase1" agent skill from https://github.com/Scaffold-Stark/scaffold-stark-2/tree/main/.claude/skills/stark-update-phase1 into .gemini/skills/stark-update-phase1/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stark-update-phase1", 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-update-phase1Installs 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-update-phase1 -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-update-phase1 .github/skills/stark-update-phase1 && 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-update-phase1" agent skill from https://github.com/Scaffold-Stark/scaffold-stark-2/tree/main/.claude/skills/stark-update-phase1 into .github/skills/stark-update-phase1/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stark-update-phase1", 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-update-phase1 -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-update-phase1 --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-update-phase1 .opencode/skills/stark-update-phase1 && 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-update-phase1" agent skill from https://github.com/Scaffold-Stark/scaffold-stark-2/tree/main/.claude/skills/stark-update-phase1 into .opencode/skills/stark-update-phase1/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stark-update-phase1", 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-update-phase1- GitHub stars
- 109
- Token cost
- ~3.2k tokens
- SKILL.md length
- 1,484 words
- Files
- 1
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- None found
At a glance
Phase 1 — check and update dependencies for scaffold-stark-2 itself (Starknet toolchain, Cairo/OpenZeppelin, starknet.js, Next.js frontend, security advisories).
- Asked does anything need updating?
- SKILL.md covers Prime directives, Step 1 — Starknet toolchain, Step 2 — Cairo / OpenZeppelin and Step 3 — starknet.js and…, plus 6 more sections
- Calls gh, npm and yarn
- Before planning a release
What it does
Stark Update Phase1 is an agent skill from 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). Use when asked "does anything need updating?", before planning a release, or when returning to the project after time away. Phase 1 covers THIS repo only; sibling forks are Phase 2 and must not be touched here.
Its SKILL.md is about 3.2k 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 Development. It works with Next.js and OpenZeppelin. The repository describes itself as: Open source forkable Starknet dev stack. Codebase of Scaffold Stark.
When your agent uses it
- Asked does anything need updating?
- Before planning a release
- Returning to the project after time away
Example prompts
- “does anything need updating?”
- “/stark-update-phase1”
Requirements
- Docker
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
Shell commands in SKILL.md call:
ghnpmyarnjq
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, npm and 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 Update Phase1 loads about 3.2k tokens when it runs. Until then it costs about 98 tokens; SKILL.md has 1,484 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 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
Without a licence we can't republish the file, so here is its outline and opening line. It has 1,484 words (~3,178 tokens).
“Answer one question: which dependencies in this repo need updating, and which should deliberately stay put?”
- name
- stark-update-phase1
Files
Just SKILL.md in .claude/skills/stark-update-phase1 of Scaffold-Stark/scaffold-stark-2.
Open the folder on GitHubat commit ae1b689
Compare with similar skills
Stark Update Phase1 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 Update Phase1 this skillScaffold-Stark/scaffold-stark-2 | 109 | — | ~3.2k | Automated safety check: Pass | None | |
| Runtime Debugvercel/next.js | 143k | 1 repos | ~618 | Automated safety check: Pass | MIT | |
| React Best Practicesshapeshift/web | 206 | 1 repos | ~2k | Automated safety check: Pass | MIT | |
| Docs AuthoringTracecatHQ/tracecat | 3.8k | — | ~3.1k | Automated safety check: Notes | AGPL-3.0 | |
| Clean Vmaxeldelafosse/loop | 281 | — | ~906 | Automated safety check: Pass | MIT | |
| React Performanceaffaan-m/ECC | 276k | 1 repos | ~4.5k | Automated safety check: Pass | MIT |
Similar skills
- Official
React Best Practices
shapeshift/web
Comprehensive React and Next.js performance optimization guide with 40+ rules for eliminating waterfalls, optimizing bundles, and improving rendering.
Docs Authoring
TracecatHQ/tracecat
A skill your agent uses when adding or updating documentation pages in an existing docs site.
Clean Vm
axeldelafosse/loop
Safely clean the local loop VM by reporting and removing stale loop runs, inactive Next.js or Storybook servers, optional browser windows, and unused loop-created worktrees without disturbing active…
React Performance
affaan-m/ECC
React and Next.js performance optimization patterns adapted from Vercel Engineering's React Best Practices (https://github.com/vercel-labs/agent-skills).
Tanstack Query Expert
davila7/claude-code-templates
Expert in TanStack Query (React Query) — asynchronous state management.
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 Smoke Test
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…
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
Works with
Categories
Questions about Stark Update Phase1
What does Stark Update Phase1 do?
Phase 1 — check and update dependencies for scaffold-stark-2 itself (Starknet toolchain, Cairo/OpenZeppelin, starknet.js, Next.js frontend, security advisories). Stark Update Phase1 is an agent skill from Scaffold-Stark/scaffold-stark-2.js frontend, security advisories).
When should I use Stark Update Phase1?
Stark Update Phase1 fits situations like: asked does anything need updating?; before planning a release; returning to the project after time away.
How do I install Stark Update Phase1 in Claude Code?
Run `npx skills add Scaffold-Stark/scaffold-stark-2 --skill stark-update-phase1 -a claude-code`. Or copy the skill folder (.claude/skills/stark-update-phase1 in Scaffold-Stark/scaffold-stark-2) into .claude/skills/stark-update-phase1 in your project. Claude Code loads it when a task matches its description.
How do I install Stark Update Phase1 in Codex?
Run `npx skills add Scaffold-Stark/scaffold-stark-2 --skill stark-update-phase1 -a codex`. Or copy the skill folder (.claude/skills/stark-update-phase1 in Scaffold-Stark/scaffold-stark-2) into .agents/skills/stark-update-phase1 in your project. Codex loads it when a task matches its description.
Can I use Stark Update Phase1 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-update-phase1 -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-update-phase1, .gemini/skills/stark-update-phase1, .github/skills/stark-update-phase1 and .opencode/skills/stark-update-phase1 in your project.
What does Stark Update Phase1 need to run?
Going by SKILL.md and its folder, Stark Update Phase1 needs the command-line tools its instructions call (gh, npm, yarn and jq). Our summary lists: Docker.
Does Stark Update Phase1 access the network?
SKILL.md contains no URLs. Its commands use gh and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Stark Update Phase1 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 Stark Update Phase1 use?
No licence was found for Stark Update Phase1 or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Stark Update Phase1 use?
About 3.2k tokens (SKILL.md is roughly 13k 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 Update Phase1?
Skills that share tags, products or a category with Stark Update Phase1: Runtime Debug (vercel/next.js, 143k stars), React Best Practices (shapeshift/web, 206 stars), Docs Authoring (TracecatHQ/tracecat, 3.8k stars) and Clean Vm (axeldelafosse/loop, 281 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Stark Update Phase1?
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.