bootstrap
Skill1 starsChanged 4 months agoMITView on GitHub
Prepares a project for the yoke flow — stack detection, scaffolding the `.yoke/` layout, and generation of CLAUDE.md, `.yoke/yoke-context.md`, and `.yoke/flow.md`. Used when the user writes "bootstrap", "set up yoke", "prepare the project", "yoke init", "setup yoke", "first run", "connect yoke", "create CLAUDE.md".
70 other projects use a version of this.
Adopted by
Most recently taken up by
- victorbeppler/claude-bootstraptheir own version, first seen Nov 8, 2026
- zedarvates/frugal-skillstheir own version, first seen Nov 8, 2026
- joi-fairshare/agentic-workflowtheir own version, first seen Nov 8, 2026
- renzrollon/interlocktheir own version, first seen Nov 5, 2026
- ArcticFox2029/chamnantheir own version, first seen Nov 5, 2026
- enocgit/sdlc-kittheir own version, first seen Nov 1, 2026
Used with
Projects with it also use surprise-me, ppt-generation and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
stophobiaSkillsurprise-me
Create a delightful, unexpected "wow" experience for the user by dynamically discovering and creatively combining other enabled skills. Triggers when the user says "surprise me" or any request expressing a desire for an unexpected creative showcase. Also triggers when the user is bored, wants inspiration, or asks for "something interesting".
Also in 3 projects that use this
HK-hubSkillppt-generation
Use this skill when the user requests to generate, create, or make presentations (PPT/PPTX). Creates visually rich slides by generating images for each slide and composing them into a PowerPoint file.
Also in 3 projects that use this
- stophobiaSkill
github-deep-research
Conduct multi-round deep research on any GitHub Repo. Use when users request comprehensive analysis, timeline reconstruction, competitive analysis, or in-depth investigation of GitHub. Produces structured markdown reports with executive summaries, chronological timelines, metrics analysis, and Mermaid diagrams. Triggers on Github repository URL or open source projects.
Also in 3 projects that use this
- HK-hubSkill
consulting-analysis
Use this skill when the user requests to generate, create, or write professional research reports including but not limited to market analysis, consumer insights, brand analysis, financial analysis, industry research, competitive intelligence, investment due diligence, or any consulting-grade analytical report. This skill operates in two phases — (1) generating a structured analysis framework with chapter skeleton, data query requirements, and analysis logic, and (2) after data collection by other skills, producing the final consulting-grade report with structured narratives, embedded charts, and strategic insights.
Also in 3 projects that use this
MicrosoftSkillpodcast-generation
Generate AI-powered podcast-style audio narratives using Azure OpenAI's GPT Realtime Mini model via WebSocket. Use when building text-to-speech features, audio narrative generation, podcast creation from content, or integrating with Azure OpenAI Realtime API for real audio output. Covers full-stack implementation from React frontend to Python FastAPI backend with WebSocket streaming.
Also in 3 projects that use this
VercelSkillvercel-deploy
Deploy applications and websites to Vercel with a claimable preview. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment". No authentication required - returns preview URL and claimable deployment link.
Also in 4 projects that use this
- +1 more from HK-hub
Other versions70 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 70
- bytedance/deer-flow★ 85ksame name
- mozilla-mobile/firefox-ios★ 13ksame name
- openai/plugins★ 7.8ksame name
- modelscope/OpenJudge★ 1.1ksame name
- agentscope-ai/OpenJudge★ 1.1ksame name
- iovisor/ubpf★ 996same name
- stophobia/deerflow2.0-enhanced★ 821same name
- infragate/capa★ 718same name
- EvovexAI/EvoFlow★ 612same name
- vercel/vercel-plugin★ 328same name
60 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- sync-docsSkill
- yoke-createSkill
- yoke-releaseSkill
- yoke-validateSkill
- doSkill
- draftSkill
- gcaSkill
- gpSkill
- grill-docsSkill
- grillSkill
- handoffSkill
- helpSkill
- issuesSkill
- journalSkill
- mergeSkill
- prdSkill
- prSkill
- reviewSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 1 is distinctive, and 5 are very specific to this project.
0
Common
Most of the 62 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 28
Run the phase pipeline in reference/bootstrap-pipeline.md start to finish: preflight → detect (parallel agents) → synthesize the …
- Very specific: line 37
Sibling awareness (ADR-0010): When .claude/settings.local.json declares additionalDirectories, discover sibling checkouts with .yoke/ there …
- Very specific: line 44
Flow map: Ask about linked repos, each repo's finish policy, and the tracker — one AskUserQuestion each, recommended answer first, skipping …
- Very specific: line 49
Committed vs local-only: Ask once whether .yoke/ is committed (default) or local-only.
- Very specific: line 55
Every artifact lives under
.yoke/: No skill — bootstrap included — writes yoke artifacts outside .yoke/. - Distinctive: line 60
One fork, one question: Every decision is a single AskUserQuestion with the recommended answer listed first.
“Common” is measured: kept by at least 6 in 10 of the 62 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Prepare a project for the yoke flow
One-time onboarding: read the codebase, then hand it a memory. Run once when
connecting yoke to a project. Detect the stack, architecture, and conventions;
generate CLAUDE.md and .yoke/yoke-context.md; scaffold the .yoke/ layout;
declare the project's finish rules in .yoke/flow.md; and commit the result.
Act as the orchestrator. Investigation and file generation belong to agents; the
orchestrator sequences them, resolves every fork through one AskUserQuestion with
a recommended answer, writes .yoke/flow.md, and commits.
Input
$ARGUMENTS — optional project description. Empty is fine: the skill detects
stack, architecture, and conventions from the code.
Procedure
Run the phase pipeline in reference/bootstrap-pipeline.md start to finish:
preflight → detect (parallel agents) → synthesize the PROJECT_PROFILE → generate
CLAUDE.md + .yoke/yoke-context.md + .yoke/ skeleton → verify → build
.yoke/flow.md from the user's answers → confirm → commit. That reference holds
every agent dispatch, the PROJECT_PROFILE shape, the flow.md questions, and the
commit steps.
Three duties the pipeline now carries:
- Sibling awareness (ADR-0010). When
.claude/settings.local.jsondeclaresadditionalDirectories, discover sibling checkouts with.yoke/there and reuse them: a stack-matching sibling'syoke-context.md(or the repo's own on a re-run) becomes a hypothesis the detect agents verify against the code, and the sibling's flow map pre-fills the flow interview down to one confirmation. Nothing is inherited unverified; shared facts stay with their owner repo and are linked, not copied. No siblings → identical to before. - Flow map. Ask about linked repos, each repo's finish policy, and the
tracker — one AskUserQuestion each, recommended answer first, skipping whatever
the repo already answers — then write
.yoke/flow.mdper the format contract inreference/flow-md.md. It is the file every other skill reads instead of re-asking. - Committed vs local-only. Ask once whether
.yoke/is committed (default) or local-only; record the choice in flow.md's Artifacts section and, when local-only, add a.yoke/line to.gitignore. The commit respects it.
Rules
- Every artifact lives under
.yoke/. No skill — bootstrap included — writes yoke artifacts outside.yoke/; yoke-context.md and flow.md both live there, never in the repo root. - Thin orchestrator. Agents do the investigation and file generation; the
orchestrator writes only
.yoke/flow.mdand runs git. - One fork, one question. Every decision is a single AskUserQuestion with the recommended answer listed first.
- No stops. Work to the end without confirmations between phases, except the flow-map questions and the Confirm gate.
- Idempotent. On re-run, extend CLAUDE.md and regenerate
.yoke/yoke-context.md; never clobber hand-written files (.yoke/context.md,.yoke/journal.md,.yoke/flow.md). - Language. Match the ticket/input language, or the project-level definition in CLAUDE.md / AGENTS.md.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.