init
Skill34 starsChanged 51 days agoMITView on GitHub
Prepare a repository with the directories and gitignore entries
137 other projects use a version of this.
Adopted by
Most recently taken up by
- naderelewa/Product-to-Prodtheir own version, first seen Nov 8, 2026
- ShahriarBijoy/show-me-howtheir own version, first seen Nov 8, 2026
- MMACABRE/SKILLStheir own version, first seen Nov 8, 2026
- BSSE23047/nauraiz-devtheir own version, first seen Nov 8, 2026
- edwinidrus/dragonhoardtheir own version, first seen Nov 8, 2026
- NilsHellwig/acl-paper-skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use daily-arxiv, exp-eval 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.
LambenthanSkilldaily-arxiv
每日从 arXiv 拉取新论文,过滤相关性,auto-ingest 高优先级论文,检测 SOTA 更新
Also in 5 projects that use this
LambenthanSkillexp-eval
实验判决门:Review LLM 独立评判实验结果 → 4 种判决路径 → 自动更新 claims confidence、ideas status、graph edges
Also in 5 projects that use this
skyllwtSkillexp-pilot-eval
Pilot result evaluation — read pilot results, apply success criteria, update idea page (pilot_result, failure_reason if failed), generate PILOT_VERDICT_REPORT. Called by /ideate Phase 5 after /exp-pilot-run.
Also in 4 projects that use this
skyllwtSkillexp-pilot-run
Pilot experiment execution — read Pilot Spec YAML, write pilot code, run experiment(Confirm with the user before operation and require the applicant to conduct manual inspection), return results. Called by /ideate Phase 5. Does NOT modify wiki pages or judge pass/fail.
Also in 4 projects that use this
gaebalaiSkillcodex-system
PROACTIVELY consult Codex CLI, your highly capable supporter with exceptional reasoning and task completion abilities. Codex is a trusted expert you should ALWAYS consult BEFORE making decisions on: design choices, implementation approaches, debugging strategies, refactoring plans, or any non-trivial problem. When uncertain, consult Codex. Don't hesitate - Codex provides better analysis. Explicit triggers: "think deeper", "analyze", "second opinion", "consult codex".
Also in 3 projects that use this
- +6 more from Lambenthan
- +1 more from skyllwt
Other versions137 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 137
- microsoft/vscode★ 195ksame name
- mcollina/skills★ 2ksame name
- skyllwt/OmegaWiki★ 1.7ksame name
- DAIR-AutoResearch/AutoSci★ 1.7ksame name
- PKU-DAIR/AutoSci★ 1.7ksame name
- skyllwt/AutoSci★ 1.7ksame name
- TokenRollAI/cc-plugin★ 483same name
- pipecat-ai/gradient-bang★ 420same name
- AlexPEClub/ai-coding-starter-kit★ 382same name
- dannysmith/tauri-template★ 312same name
127 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 repository38 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- hooks/CLAUDE.mdCLAUDE.md
- tasks/CLAUDE.mdCLAUDE.md
- clean-commentsSkill
- raise-prSkill
- configureSkill
- migrateSkill
- pathsSkill
- create-adrSkill
- extract-adrsSkill
- review-adrSkill
- analyse-design-gapsSkill
- inventory-designSkill
- describe-prSkill
- respond-to-prSkill
- review-prSkill
- create-noteSkill
- create-planSkill
- implement-planSkill
- review-planSkill
- stress-test-planSkill
- validate-planSkill
- conduct-spikeSkill
- research-codebaseSkill
- research-issueSkill
- research-topicSkill
- commitSkill
- visualiseSkill
- create-work-itemSkill
- extract-work-itemsSkill
- list-work-itemsSkill
- refine-work-itemSkill
- rekey-work-itemsSkill
- review-work-itemSkill
- stress-test-work-itemSkill
- sync-work-items-recoverySkill
- sync-work-itemsSkill
- update-work-itemSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 125 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 56
Only after all steps above have completed successfully, present a summary:
- Distinctive: line 89
Use the actual resolved paths in the output (not the variable names).
“Common” is measured: kept by at least 6 in 10 of the 125 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
Initialise Accelerator
You prepare a consumer repository with all directories and gitignore entries that Accelerator skills expect. This is safe to run repeatedly — it reports what was created versus what already existed.
Path Resolution
Resolve each output directory using the plugin's path configuration:
Plans directory: !accelerator config path plans --fail-safe
Codebase research directory: !accelerator config path research_codebase --fail-safe
Decisions directory: !accelerator config path decisions --fail-safe
PRs directory: !accelerator config path prs --fail-safe
Validations directory: !accelerator config path validations --fail-safe
Review plans directory: !accelerator config path review_plans --fail-safe
Review PRs directory: !accelerator config path review_prs --fail-safe
Review work items directory: !accelerator config path review_work --fail-safe
Work items directory: !accelerator config path work --fail-safe
Notes directory: !accelerator config path notes --fail-safe
Design inventories directory: !accelerator config path research_design_inventories --fail-safe
Design gaps directory: !accelerator config path research_design_gaps --fail-safe
Global directory: !accelerator config path global --fail-safe
Steps
Execute the following steps in order, tracking what was created versus what already existed so you can present a summary at the end.
Steps 1–3: Run the init script
<!-- DIR_COUNT:13 -->accelerator config initThe script creates 13 meta/ directories with .gitkeep files, creates the
.accelerator/ core scaffold (.gitignore, state/, tmp/, skills/,
lenses/, templates/), writes the inner tmp .gitignore, and appends the
.accelerator/config.local.md rule to the root .gitignore. It is idempotent
— safe to run repeatedly.
Step 4: Report results
Only after all steps above have completed successfully, present a summary:
Initialisation complete:
Directories:
✓ {plans directory} (created | already exists)
✓ {research directory} (created | already exists)
✓ {decisions directory} (created | already exists)
✓ {prs directory} (created | already exists)
✓ {validations directory} (created | already exists)
✓ {review plans directory} (created | already exists)
✓ {review prs directory} (created | already exists)
✓ {review work items directory} (created | already exists)
✓ {work items directory} (created | already exists)
✓ {notes directory} (created | already exists)
✓ {design inventories directory} (created | already exists)
✓ {design gaps directory} (created | already exists)
✓ {global directory} (created | already exists)
Accelerator scaffold:
✓ .accelerator/.gitignore (created | already exists)
✓ .accelerator/state/.gitkeep (created | already exists)
✓ .accelerator/skills/.gitkeep (created | already exists)
✓ .accelerator/lenses/.gitkeep (created | already exists)
✓ .accelerator/templates/.gitkeep (created | already exists)
✓ .accelerator/tmp/.gitignore (created | already exists)
✓ .accelerator/tmp/.gitkeep (created | already exists)
Gitignore entries:
✓ .accelerator/config.local.md (added | already present)Use the actual resolved paths in the output (not the variable names).
/accelerator:init bootstraps a fresh repository. To upgrade an existing repository after a plugin update, use /accelerator:migrate instead — it applies ordered, idempotent migrations to bring meta/, .claude/, and .accelerator/ in line with the latest schema.
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.

