agentleFS
matteo-strategamatteo-stratega/claude-cortex/.claude/skills/setup/SKILL.md

setup

Skill8 starsChanged 5 months agoMITView on GitHub

First-time guided workspace setup. Run once after cloning to fill in your context files.

192 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use add-atomic-chat-tool, add-dashboard 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.
  • MicrosoftSkill

    add-atomic-chat-tool

    Add Atomic Chat MCP server so the container agent can call local models served by the Atomic Chat desktop app via its OpenAI-compatible API.

    Also in 8 projects that use this

  • MicrosoftSkill

    add-dashboard

    Add a monitoring dashboard to NanoClaw. Installs @nanoco/nanoclaw-dashboard and a pusher that sends periodic JSON snapshots.

    Also in 8 projects that use this

  • +10 more from microsoft

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 169 edited versions we read keep these.

  • 6

    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:

    Ask these questions ONE AT A TIME (wait for each answer):

    line 18
  2. Very specific:

    After user confirms, say: "You're set.

    line 42
  3. Distinctive:

    Ask questions one at a time — don't dump all 5 at once

    line 52
  4. Distinctive:

    Use their exact words in the context files — don't rephrase into corporate speak

    line 53
  5. Distinctive:

    If they say "I don't have clients" or "I don't create content", mark those areas as "Paused" in the Active Areas table

    line 54
  6. Distinctive:

    Keep context.md under 60 lines after filling in

    line 55
  7. Distinctive:

    Remove all placeholder text and example blocks

    line 56

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

First-Time Setup

Guide the user through setting up their workspace. Run this once after cloning.

Step 1: Welcome

Say: "Welcome to your AI workspace. I'll help you set it up in about 5 minutes. I'll ask you a few questions, then fill in your context files."

Step 2: Gather Info

Ask these questions ONE AT A TIME (wait for each answer):

  1. "What's your name and what do you do? (e.g., 'Alex Chen, solo founder building a SaaS')"
  2. "What are you working on right now? Give me your top 3 priorities this week."
  3. "What's your tech stack? (e.g., 'Next.js, Supabase, Netlify' — or 'I don't code, I use no-code tools')"
  4. "Do you have active clients or deals? If yes, list them briefly."
  5. "Do you create content? If yes, what channels and how often?"

Step 3: Fill In Context

Based on the answers, update these files:

  1. brain/context.md — Fill in "Who I Am", "This Week", "Quick Reference". Remove the <!-- EXAMPLE --> block.
  2. brain/contexts/work.md — Fill in deals/clients table if they have any. Remove example block.
  3. brain/contexts/projects.md — Fill in projects table. Remove example block.
  4. brain/contexts/content.md — Fill in schedule and voice notes if they create content. Remove example block.

Step 4: Confirm

Show the user their filled-in brain/context.md and ask: "Does this look right? Anything to add or change?"

Step 5: First Commit

After user confirms, say: "You're set. From now on, start every session with /start and end with /close. Your context will stay current automatically."

Suggest they make their first commit:

git add brain/ CLAUDE.md && git commit -m "Initial context setup"

Rules

  • Ask questions one at a time — don't dump all 5 at once
  • Use their exact words in the context files — don't rephrase into corporate speak
  • If they say "I don't have clients" or "I don't create content", mark those areas as "Paused" in the Active Areas table
  • Keep context.md under 60 lines after filling in
  • Remove all placeholder text and example blocks

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.