Defuddle
kepano/obsidian-skills
Uses the Defuddle CLI to pull clean, readable Markdown, JSON or metadata from web pages, stripping navigation, ads and clutter to save tokens.
Phase 2 — propagate an already-merged scaffold-stark-2 update out to its sibling forks and the create-stark npm template.
$ npx skills add Scaffold-Stark/scaffold-stark-2 --skill stark-sync-phase2 -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Scaffold-Stark/scaffold-stark-2 stark-sync-phase2 --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-sync-phase2 .claude/skills/stark-sync-phase2 && 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-sync-phase2" agent skill from https://github.com/Scaffold-Stark/scaffold-stark-2/tree/main/.claude/skills/stark-sync-phase2 into .claude/skills/stark-sync-phase2/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stark-sync-phase2", 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-sync-phase2Type 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-sync-phase2 -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Scaffold-Stark/scaffold-stark-2 stark-sync-phase2 --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-sync-phase2 .agents/skills/stark-sync-phase2 && 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-sync-phase2" agent skill from https://github.com/Scaffold-Stark/scaffold-stark-2/tree/main/.claude/skills/stark-sync-phase2 into .agents/skills/stark-sync-phase2/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stark-sync-phase2", 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-sync-phase2 -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Scaffold-Stark/scaffold-stark-2 stark-sync-phase2 --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-sync-phase2 .cursor/skills/stark-sync-phase2 && 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-sync-phase2" agent skill from https://github.com/Scaffold-Stark/scaffold-stark-2/tree/main/.claude/skills/stark-sync-phase2 into .cursor/skills/stark-sync-phase2/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stark-sync-phase2", 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-sync-phase2--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-sync-phase2 -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Scaffold-Stark/scaffold-stark-2 stark-sync-phase2 --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-sync-phase2 .gemini/skills/stark-sync-phase2 && 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-sync-phase2" agent skill from https://github.com/Scaffold-Stark/scaffold-stark-2/tree/main/.claude/skills/stark-sync-phase2 into .gemini/skills/stark-sync-phase2/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stark-sync-phase2", 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-sync-phase2Installs 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-sync-phase2 -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-sync-phase2 .github/skills/stark-sync-phase2 && 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-sync-phase2" agent skill from https://github.com/Scaffold-Stark/scaffold-stark-2/tree/main/.claude/skills/stark-sync-phase2 into .github/skills/stark-sync-phase2/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stark-sync-phase2", 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-sync-phase2 -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-sync-phase2 --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-sync-phase2 .opencode/skills/stark-sync-phase2 && 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-sync-phase2" agent skill from https://github.com/Scaffold-Stark/scaffold-stark-2/tree/main/.claude/skills/stark-sync-phase2 into .opencode/skills/stark-sync-phase2/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stark-sync-phase2", 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.
stark-sync-phase2Phase 2 — propagate an already-merged scaffold-stark-2 update out to its sibling forks and the create-stark npm template.
Stark Sync Phase2 is an agent skill from 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. Verifies whether each target's sync automation actually worked, and repairs broken automation rather than hand-patching the target. Use only AFTER Phase 1 changes are merged; run stark-update-phase1 first.
Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It works with npm. The repository describes itself as: Open source forkable Starknet dev stack. Codebase of Scaffold Stark.
Read from SKILL.md and the folder at commit ae1b689. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
gitghnpmnpxFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use git, gh, 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.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Stark Sync Phase2 loads about 2.4k tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 1,051 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.
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.
Without a licence we can't republish the file, so here is its outline and opening line. It has 1,051 words (~2,380 tokens).
“Answer: did each sibling actually receive the Phase 1 changes, and if not, why?”
Just SKILL.md in .claude/skills/stark-sync-phase2 of Scaffold-Stark/scaffold-stark-2.
Open the folder on GitHubat commit ae1b689
Stark Sync Phase2 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 Sync Phase2 this skillScaffold-Stark/scaffold-stark-2 | 109 | — | ~2.4k | Automated safety check: Pass | None | |
| Defuddlekepano/obsidian-skills | 49k | 12 repos | ~208 | Automated safety check: Pass | MIT | |
| Vercel Deploybytedance/deer-flow | 83k | 10 repos | ~797 | Automated safety check: Pass | MIT | |
| MCP Server BuildershareAI-lab/learn-claude-code | 78k | 5 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Knap Markdown Templateskepano/obsidian-skills | 49k | 2 repos | ~986 | Automated safety check: Pass | MIT | |
| Install Anti-Slop Oxlint Rulesdmmulroy/anti-slop | 5.3k | 1 repos | ~2.2k | Automated safety check: Pass | MIT |
kepano/obsidian-skills
Uses the Defuddle CLI to pull clean, readable Markdown, JSON or metadata from web pages, stripping navigation, ads and clutter to save tokens.
bytedance/deer-flow
Deploys a project to Vercel with one script and no login, then returns a live preview URL and a claim link for moving the deployment into your own Vercel account.
shareAI-lab/learn-claude-code
Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.
kepano/obsidian-skills
Renders Markdown notes from Knap templates and JSON data on the command line, including notes built from Defuddle web page output.
dmmulroy/anti-slop
Installs, updates or migrates the vendored anti-slop Oxlint plugin in a repository, keeping local rule changes and the plugin's license and provenance files.
nomcopter/react-mosaic
Helps with running tasks in an Nx workspace. An agent skill from nomcopter/react-mosaic.
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…
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…
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).
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…
Works with
Phase 2 — propagate an already-merged scaffold-stark-2 update out to its sibling forks and the create-stark npm template. Stark Sync Phase2 is an agent skill from 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.
Run `npx skills add Scaffold-Stark/scaffold-stark-2 --skill stark-sync-phase2 -a claude-code`. Or copy the skill folder (.claude/skills/stark-sync-phase2 in Scaffold-Stark/scaffold-stark-2) into .claude/skills/stark-sync-phase2 in your project. Claude Code loads it when a task matches its description.
Run `npx skills add Scaffold-Stark/scaffold-stark-2 --skill stark-sync-phase2 -a codex`. Or copy the skill folder (.claude/skills/stark-sync-phase2 in Scaffold-Stark/scaffold-stark-2) into .agents/skills/stark-sync-phase2 in your project. Codex loads it when a task matches its description.
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-sync-phase2 -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-sync-phase2, .gemini/skills/stark-sync-phase2, .github/skills/stark-sync-phase2 and .opencode/skills/stark-sync-phase2 in your project.
Going by SKILL.md and its folder, Stark Sync Phase2 needs the command-line tools its instructions call (git, gh, npm and npx). Our summary lists: Node.js; Docker.
SKILL.md contains no URLs. Its commands use git, gh, npm and npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
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.
No licence was found for Stark Sync Phase2 or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
About 2.4k tokens (SKILL.md is roughly 9.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Stark Sync Phase2: Defuddle (kepano/obsidian-skills, 49k stars), Vercel Deploy (bytedance/deer-flow, 83k stars), MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars) and Knap Markdown Templates (kepano/obsidian-skills, 49k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
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.