agentleFS
kele-devkele-dev/Claude-Orchestrator-Skill/skills/init/SKILL.md

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

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.
  • LambenthanSkill

    daily-arxiv

    每日从 arXiv 拉取新论文,过滤相关性,auto-ingest 高优先级论文,检测 SOTA 更新

    Also in 5 projects that use this

  • LambenthanSkill

    exp-eval

    实验判决门:Review LLM 独立评判实验结果 → 4 种判决路径 → 自动更新 claims confidence、ideas status、graph edges

    Also in 5 projects that use this

  • skyllwtSkill

    exp-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

  • skyllwtSkill

    exp-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

  • gaebalaiSkill

    codex-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

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
  1. Very specific:

    If <store>/lessons/learned-map.md exists and there is no --refresh, say so in one line and stop.

    line 14
  2. Distinctive:

    Test, build, lint, and typecheck commands.

    line 28
  3. Very specific:

    Run each detected test/lint/typecheck command once.

    line 32
  4. Very specific:

    Write <store>/lessons/learned-map.md in the learn format: the frontmatter description line plus at most 20 lesson lines (shorter is fine).

    line 36
  5. Very specific:

    Add one map line: Verify: bash <absolute store path>/verify.sh, using the absolute store path from the brief, never the literal <store> …

    line 38

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.md exists and there is no --refresh, say so in one line and stop. Also skip if a legacy learned-map exists (legacy.md in the orchestrator:learn folder; 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.md in the learn format: 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 print PASS <name>, or on failure FAIL <name> followed by the last 15 lines of its output; end with one line VERIFY: PASS (n/m) or VERIFY: 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.