agentleFS
the-abraham-brandthe-abraham-brand/my-business-brain/skills/brief/SKILL.md

brief

Skill0 starsChanged 51 days agoMITView on GitHub

My Business Brain briefings and reports. Builds a cited briefing on one topic (a supplier, customer, product line or pricing), an onboarding pack for a new team member, a timeline of what happened around a fact or date, the monthly business journal, or the one-page dashboard. Use when the user runs /my-business-brain:brief, or asks "what do we know about…", "brief me on…", "what happened with…", for an onboarding pack, a monthly summary or journal, or the brain dashboard.

81 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use capture, strategy and 9 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.
  • toneron2Skill

    capture

    Capture thoughts to inbox with automatic classification

    Also in 6 projects that use this

  • EpistatesSkill

    strategy

    Plan weekly or monthly X content strategy. Use when the user wants to plan their content calendar, set growth goals, build a content pipeline, or think strategically about their X presence.

    Also in 4 projects that use this

  • aleksander-dytkoSkill

    decision

    Make a product decision with full context from the vault and available sources

    Also in 3 projects that use this

  • dirienSkill

    decide

    Three-agent adversarial debate protocol for strategic decisions. Two advocates steelman opposing positions while a moderator identifies risks and synthesizes a binding consensus. Use when choosing between alternatives, evaluating tradeoffs, or making high-stakes decisions.

    Also in 5 projects that use this

  • JaimeGBASkill

    ingest

    Digest an external source (article, paper, transcript, URL, book chapter) and integrate its content into the knowledge base

    Also in 7 projects that use this

  • howellsSkill

    reconcile

    Audit a project against current plugin conventions and offer to update structure.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 74 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    If the audience isn't clear, ask.

    line 19
  2. Very specific:

    Before sharing, run scripts/cite_check.py <brain> <file> --audience team (or external for outsiders) and fix every failure.

    line 23

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

/my-business-brain:brief

Turn what the brain knows into something a person can read in two minutes.

  1. Load the my-business-brain skill from this plugin (via the Skill tool). If it cannot be loaded, read ../my-business-brain/SKILL.md and ../my-business-brain/references/briefings-and-journal.md directly.
  2. Work out which one the user wants, and for whom:

    • Topic briefing: scripts/briefing.py <brain> --topic "..." [--q "other phrasing"] --audience owner|team|external --write.
    • Onboarding pack: scripts/briefing.py <brain> --onboarding [--domain ...] --audience team --write.
    • Timeline: scripts/timeline.py <brain> --entry ID | --key K | --topic "..." | --around YYYY-MM-DD.
    • Monthly journal: scripts/journal.py <brain> --month YYYY-MM --write.
    • Meeting prep: scripts/meeting_prep.py <brain> --with "..." [--topic "..."] [--audience team] --write.
    • Dashboard: scripts/dashboard.py <brain>, then offer to open _system/dashboard.html.

    If the audience isn't clear, ask. Anything for staff is team, anything leaving the business is external, and only the owner sees confidential facts. For a topic briefing, add open sentiment and leads on the same topic (scripts/signals.py <brain> list --open) in a separate part headed as unconfirmed, owner audience only.

  3. Replace the placeholder lines in a briefing or journal with a short plain-language summary, written only from the facts listed, in the language of record (${user_config.language}). Keep every [[id]] citation. Never add facts that aren't listed.
  4. For several follow-up questions on one topic, hand them to the topic-expert agent with the briefing's path. It answers from the briefing only, so a team or external briefing never leaks withheld facts.
  5. Before sharing, run scripts/cite_check.py <brain> <file> --audience team (or external for outsiders) and fix every failure. Log it with --log if it is sent.

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.