agentleFS
le4kerle4ker/mneme-template/.agents/skills/setup/SKILL.md

setup

Skill2 starsChanged 14 days agoMITView on GitHub

Run once in a fresh vault. Do not run again after the Areas have been configured. Ask one question at a time and wait for the answer: 1. Which long-term Areas should the vault track? Offer Books, Finance, Fitness, Travel, Recipes, Work, Wellness, Music, and Learning as examples. For each, record its name, an emoji, and a one-line description. Draft the emoji and description for the user to approve. Ask whether they want to add more Areas until they are…

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

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 171 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run once in a fresh vault.

    line 9
  2. Distinctive:

    Ask one question at a time and wait for the answer:

    line 14
  3. Distinctive:

    After gathering the details, make these changes without additional prompts:

    line 27
  4. Very specific:

    Create Areas/{emoji} {name}/.gitkeep for each Area.

    line 29
  5. Distinctive:

    Delete this setup skill after creating the other files.

    line 38

“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
<!-- markdownlint-disable MD041 -->

Run once in a fresh vault. Do not run again after the Areas have been configured.

Gather details

Ask one question at a time and wait for the answer:

  1. Which long-term Areas should the vault track? Offer Books, Finance, Fitness, Travel, Recipes, Work, Wellness, Music, and Learning as examples. For each, record its name, an emoji, and a one-line description. Draft the emoji and description for the user to approve. Ask whether they want to add more Areas until they are done.
  2. Which Areas need recurring logs? For each, record the log filename and the fields to track. Date is included automatically.
  3. What should the vault be called? Use “My Vault” if they skip this answer.

Generate the vault

After gathering the details, make these changes without additional prompts:

  1. Create Areas/{emoji} {name}/.gitkeep for each Area.
  2. Replace the setup comment under ## Content Areas in AGENTS.md with a Markdown table listing each Area path and description.
  3. For each journalled Area, create .agents/skills/log-{kebab-name}/SKILL.md. Include name and a concise description in YAML front matter. In the skill instructions, ask for each field except Date (use today's date), open Areas/{emoji} {name}/{Log File Name}.md, create it with an H1 and an empty table if needed, insert each new row directly below the table header, run make format, and report the logged entry.
  4. Delete this setup skill after creating the other files.
  5. Run make format.

Report the vault name, Areas created, generated log skills, and next steps: open the vault in Obsidian, invoke $inbox to capture a first note, and invoke $sync-vault to commit and push.

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.