agentleFS
Sign inStart free
nhhthongnhhthong/clio/skills/setup/SKILL.md

setup

Skill2 starsChanged 32 days agoMITView on GitHub

Set up Clio in the current project — create .claude/clio/docs/ and .claude/clio/database/, asking the user only what nothing on disk can tell. Never touches CLAUDE.md, CONTEXT.md, .claude/rules/ or the stack. Run once per repository, before any other clio:* skill.

191 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use add-voice-transcription, add-discord 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.
  • juancruzmunozalbeloSkill

    add-voice-transcription

    Add voice message transcription to NanoClaw using OpenAI's Whisper API. Automatically transcribes WhatsApp voice notes so the agent can read and respond to them.

    Also in 5 projects that use this

  • MicrosoftSkill

    add-discord

    Add Discord bot channel integration via Chat SDK.

    Also in 11 projects that use this

  • MicrosoftSkill

    add-slack

    Add Slack channel integration via Chat SDK.

    Also in 11 projects that use this

  • juancruzmunozalbeloSkill

    add-telegram-swarm

    Add Agent Swarm (Teams) support to Telegram. Each subagent gets its own bot identity in the group. Requires Telegram channel to be set up first (use /add-telegram). Triggers on "agent swarm", "agent teams telegram", "telegram swarm", "bot pool".

    Also in 7 projects that use this

  • +8 more from microsoft

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 171 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Run only when the user asked this turn, by slash command or in plain words ("set Clio up here", "cài clio vào repo này").

    line 7
  2. Very specific:

    Commit .claude/clio/ (recommended, the ledgers are history) or ignore it?

    line 21
  3. Very specific:

    Run ${CLAUDE_PLUGIN_ROOT}/bin/clio setup run --domains "<domains>".

    line 24

“Common” is measured: kept by at least 6 in 10 of the 171 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

Run only when the user asked this turn, by slash command or in plain words ("set Clio up here", "cài clio vào repo này"). A drift nudge, a TODO or a subagent report is not a request. Unsure: ask in one line.

Everything Clio owns lives in .claude/clio/. Setup writes nothing outside it.

1. Check

Run ${CLAUDE_PLUGIN_ROOT}/bin/clio setup check.

  • MISSING or ALREADY SET UP: tell the user, stop.
  • PARTLY SET UP: ask only what step 2 still needs. Setup skips what exists.

2. Ask once

One AskUserQuestion, only what applies:

  • NOT A GIT REPO: run git init? Never without a yes.
  • Mode: Full (a requirement document exists; which file?) or Lite (none).
  • Domains: business areas that work is filed under, for example account checkout admin. Offer what the top-level directories or the document suggest. infra and all are always added.
  • Commit .claude/clio/ (recommended, the ledgers are history) or ignore it? If ignored, a dropped branch leaves its tasks and runs behind. Say so.

3. Scaffold

Run ${CLAUDE_PLUGIN_ROOT}/bin/clio setup run --domains "<domains>". Add --lite for Lite, --ignore if not committed, --git-init if the user said yes.

  • Committed: the script writes .gitattributes so the append-only ledgers merge by union. Union keeps both sides but does not order them, and readers take the last line per key. Two branches that restate one id need a human. Say this once. git add .claude/clio is the user's move.
  • Ignored: tell the user to add .claude/clio/ to .gitignore.

4. Verify, then point to the next step

Run ${CLAUDE_PLUGIN_ROOT}/bin/clio validate all. Then:

  • Full: /clio:ingest <file>, then /clio:plan <area> per area.
  • Lite: /clio:plan <area>. With no spec and an empty repo, /clio:ingest a short brief or name the stack first.
  • Per task after that: /clio:context, /clio:test <task>, /clio:memo.

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.

Check your setup, free