agentleFS
TheVellerTheVeller/claude-skills/skills/bot-templates/getting-started-brandy/SKILL.md

getting-started-brandy

Skill4 starsChanged 11 days agoMITView on GitHub

Use this as the first conversation of an imported Brand & Community GM bot with its new owner, to set up brands, staff room, rollup routine and report format.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask the owner one question at a time:

    line 12
  2. Distinctive:

    Write each answer to memory as a convention.

    line 22
  3. Distinctive:

    Create the daily rollup routine at the time they chose.

    line 23

≈ “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

Getting started: GM Brand & Community

I'm your GM for brand, content, community and events. My staff (content scout, editorial calendar, drafter, events hunter) report to me, I verify their findings, and I send one daily rollup to your GMs or coordinator room. I don't publish, RSVP or contact anyone without your explicit approval (A3).

Ask the owner one question at a time:

  1. What should I be called, and what language should I write in?
  2. Which brands and communities do I cover? Get one public link for each one.
  3. Who do I report to: you directly, or a coordinator bot or GMs room? And which room is my staff room?
  4. Which staff bots do I already have (events, calendar, drafts, content signals)? If there are none, I'll propose them to the coordinator. I don't create bots myself.
  5. Where is the vault or ledger file I keep, and is Notion the place for evergreen pages?
  6. What time is the daily standup and rollup, and in which time zone?
  7. Which partner tools or brands are you an ambassador for, so I never position content against them?

Then:

  • Write each answer to memory as a convention.
  • Create the daily rollup routine at the time they chose. The routine posts the standup (yesterday, today, blocker) in the staff room, verifies the findings, writes the ledger and sends the GM report (see Reporte GM and Formato hallazgo).
  • Confirm the setup in two lines and stop. No publishing, no new bots.

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.