init
Skill10 starsChanged 2 days agoMITView on GitHub
Maps a project in one cheap Haiku pass and writes the learned-map lesson with verified test/build/lint commands. Use on /orchestrator:init or at the first task in a project without a learned-map.
143 other projects use a version of this.
Adopted by
Most recently taken up by
- FAHTHIZ/oasistheir own version, first seen Nov 16, 2026
- timursafiullin/aodtheir own version, first seen Nov 15, 2026
- XORwell/archeflowtheir own version, first seen Nov 15, 2026
- warrendeanlangeveldt/code-kittheir own version, first seen Nov 15, 2026
- scolladon/crafttheir own version, first seen Nov 15, 2026
- felipefontoura/claude-sdd-kittheir own version, first seen Nov 15, 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 versions143 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 143
- microsoft/vscode★ 195ksame name
- mcollina/skills★ 2ksame name
- DAIR-AutoResearch/AutoSci★ 1.7ksame name
- PKU-DAIR/AutoSci★ 1.7ksame name
- skyllwt/AutoSci★ 1.7ksame name
- skyllwt/OmegaWiki★ 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
133 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.
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 1 is distinctive, and 4 are very specific to this project.
0
Common
Most of the 131 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
If <store>/lessons/learned-map.md exists and there is no --refresh, say so in one line and stop.
- Distinctive: line 28
Test, build, lint, and typecheck commands.
- Very specific: line 32
Run each detected test/lint/typecheck command once.
- Very specific: line 36
Write <store>/lessons/learned-map.md in the learn format: the frontmatter description line plus at most 20 lesson lines (shorter is fine).
- Very specific: line 38
Add one map line: Verify: bash <absolute store path>/verify.sh, using the absolute store path from the brief, never the literal <store> …
“Common” is measured: kept by at least 6 in 10 of the 131 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
Project init: one-pass map
Arguments: $ARGUMENTS
<store> is defined in the learn skill (per-project folder under ~/.claude/orchestrator/, same from every git worktree, writable from worktree sessions); use the session-start Orchestrator store: line, or run the Store command once, and put the absolute path in the brief. The main session never reads the manifests itself.
1. Skip
- If
<store>/lessons/learned-map.mdexists and there is no--refresh, say so in one line and stop. Also skip if a legacy learned-map exists (legacy.mdin theorchestrator:learnfolder; only if legacy files exist), unless--refresh.
2. Delegate once (orchestrator:haiku-coder, TYPE: CREATE)
The brief tells Haiku to read only top-level files that exist:
- package.json and workspace files, pyproject.toml, requirements*.txt, Cargo.toml, go.mod, composer.json, Gemfile.
- Makefile, justfile, Dockerfile, compose files, CI workflows (.github/workflows).
- CLAUDE.md (if present).
- The first 60 lines of README.
- A per-folder file count from
git ls-files(top 2 levels, counts only, not the full list).
Same delegation: also copy missing legacy topics (legacy.md in the orchestrator:learn folder; only if legacy files exist).
3. Derive (same delegation)
- Stack, key folders and their purpose, entry points.
- Test, build, lint, and typecheck commands.
- Generated or do-not-edit paths.
4. Verify commands (same delegation)
- Run each detected test/lint/typecheck command once. Run-only: no edits, no fixes. Trim the output.
- Mark each one: verified, broken (with the first error), or not run (needs services, env, or secrets, or is slow, such as e2e or deploy).
5. Write the map (same delegation)
- Write
<store>/lessons/learned-map.mdin thelearnformat: the frontmatter description line plus at most 20 lesson lines (shorter is fine). Do not repeat facts CLAUDE.md already states. - Also write
<store>/verify.sh(bash, LF line endings, portable to bash 3.2 on macOS):set -o pipefail; for each verified test/lint/typecheck command, capture its output (2>&1) and printPASS <name>, or on failureFAIL <name>followed by the last 15 lines of its output; end with one lineVERIFY: PASS (n/m)orVERIFY: FAIL (n/m)and exit non-zero on any failure. No broken or not-run commands. Run it once and confirm the last line. - Add one map line:
Verify: bash <absolute store path>/verify.sh, using the absolute store path from the brief, never the literal<store>(counts toward the 20 lines).
6. Report
- The main session reads only the Haiku report and the written map.
- Report in one short block (stack, commands with their status, the verify.sh result, anything broken) plus the token line.
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.

