agentleFS
Sign inStart free
jaskiel123jaskiel123/operators-brain/.claude/skills/start/SKILL.md

start

Skill0 starsChanged 5 months agoMITView on GitHub

Guided setup that configures the Operator's Brain to how you actually work.

130 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use setup-engine, team-audio 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.
  • CoralGameSkill

    setup-engine

    Configure the project's game engine and version. Pins the engine in CLAUDE.md, detects knowledge gaps, and populates engine reference docs via WebSearch when the version is beyond the LLM's training data.

    Also in 13 projects that use this

  • CoralGameSkill

    team-audio

    Orchestrate audio team: audio-director + sound-designer + technical-artist + gameplay-programmer for full audio pipeline from direction to implementation.

    Also in 13 projects that use this

  • lilangMaxSkill

    create-stories

    Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.

    Also in 11 projects that use this

  • lilangMaxSkill

    story-done

    End-of-story completion review. Reads the story file, verifies each acceptance criterion against the implementation, checks for GDD/ADR deviations, prompts code review, updates story status to Complete, and surfaces the next ready story from the sprint.

    Also in 11 projects that use this

  • +5 more from CoralGame
  • +3 more from lilangMax

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 117 edited versions we read keep these.

  • 3

    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 one question at a time.

    line 12
  2. Distinctive:

    Write the answers into:

    line 20
  3. Very specific:

    Never invent answers. If the user skips one, leave a clear TODO: marker.

    line 33
  4. Distinctive:

    Keep voice samples verbatim — they are how the AI learns to write as the user.

    line 34

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

Goal

Interview the user in 7 short questions and fill context/about-you.md, context/about-business.md, and context/clients.md so every future session starts with real context.

Process

  1. Greet briefly. Explain this takes ~5 minutes and the user can pause/resume.
  2. Ask one question at a time. Wait for each answer before the next.
    1. Your name, role, working hours, and timezone.
    2. What the business does and who pays you (business model).
    3. Top 3 active clients or projects right now.
    4. The exact tools you use daily (calendar, email, CRM, docs — name them).
    5. Your voice: paste 1-2 samples of how you write (a post, an email, a proposal).
    6. What you procrastinate on that the system could handle.
    7. What the system must never do without asking you first.
  3. Write the answers into:
    • context/about-you.md (name, role, hours, voice samples, rules).
    • context/about-business.md (model, who pays, priorities).
    • context/clients.md (one section per active client/project).
  4. Replace {{YOUR_NAME}} placeholders in CLAUDE.md and AGENTS.md with the real name.
  5. Confirm what was saved and suggest the first command: /brief.

References

  • context/about-you.md, context/about-business.md, context/clients.md — destinations.
  • CLAUDE.md — placeholder to fill.

Rules

  1. One question at a time. Do not dump all 7 at once.
  2. Never invent answers. If the user skips one, leave a clear TODO: marker.
  3. Keep voice samples verbatim — they are how the AI learns to write as the user.

Improvement

  • Last updated: 2026-06-13
  • Next: detect already-filled context and offer a "refresh" path instead of overwriting.

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