agentleFS
Sign inStart free
LazyerIJLazyerIJ/self-clone/skills/clone-init/SKILL.md

clone-init

Skill2 starsChanged 27 days agoMITView on GitHub

Sets up a self-clone home — a local git folder holding the knowledge tree of how you work (tree/, tools/, sources/, exams/, RULES.md), so that /grow, /exam and /survey can start growing a clone of you as a user. Use for "/clone-init", "set up self-clone", "start a clone of me", "make a work tree of my job".

  • In this repository3 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Write the answers into <home>/clone.json (owner, git_author, work_roots, notes_dirs, never_read).

    line 22
  2. Very specific:

    after /survey, add the write tools of their connected MCP servers to deny in tools/settings.py and regenerate settings

    line 37

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

clone-init — make the clone home

The clone home is a folder of its own (default ~/self-clone-home). It is never inside a work repo, and it has no git remote. This skill's base directory holds template/ — copy from there.

1. Ask (one question block, only what cannot be guessed)

  • Where to put the home (default ~/self-clone-home). Stop if it exists and is not empty.
  • The owner's name (how the tree should call them) and their git author string (for "my commits"; suggest git config user.name).
  • Work roots — folders that hold their repos (suggest the ones that exist among ~/code, ~/src, ~/projects, ~/dev, ~/work).
  • Notes folders (Obsidian vaults etc.) and folders that must never be read (customer data, personal).

2. Copy and fill

cp -R <base>/template/ <home>/
mv <home>/gitignore <home>/.gitignore
  • Write the answers into <home>/clone.json (owner, git_author, work_roots, notes_dirs, never_read). Keep session_match as the last path segment of each work root (Claude project folder names contain it).
  • Replace checked: 2000-01-01 with today in every tree/**/_branch.md.
  • printf '@RULES.md\n' > <home>/CLAUDE.md
  • mkdir -p <home>/.claude && python3 -I <home>/tools/settings.py > <home>/.claude/settings.json — if your permission settings block the write to .claude/, print the command and ask the owner to run it.

3. First commit

cd <home> && git init -q && python3 -I tools/tree.py lint && git add -A && git commit -q -m "init: self-clone home"

4. Report

Tell the owner, in a few lines:

  • the home path, and that every later command runs from a Claude Code session opened in that folder (cd <home> && claude)
  • next steps: /survey (map of sources and access) → /grow (one node) → /loop /grow (keep growing) → /exam comes up by itself
  • tools/shape.json holds every limit (depth, children, sections); RULES.md is the constitution and can be edited
  • after /survey, add the write tools of their connected MCP servers to deny in tools/settings.py and regenerate settings

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.

Reviews can't be read right now.

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.

Check your setup, free