agentleFS
piotrmechlinskipiotrmechlinski/executive-brain/.claude/skills/brief/SKILL.md

brief

Skill0 starsChanged 24 days agoMITView on GitHub

A brief before a meeting, or on a person or a project. What is overdue, open and unverified, who the people are and the last meetings, every line with its ID and source, as a note, a Word file or a PDF. Use when the user types /brief, or asks to be briefed or prepared for a meeting.

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 8 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

  • howellsSkill

    reconcile

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

    Also in 3 projects that use this

  • HermeticOrmusSkill

    close

    End-of-session ritual. Captures session state, updates auto-memory, writes a session summary, then exits the session cleanly.

    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:

    Write it from the vault, with the project IDs and the people's names as the registers spell them: python3 tools/vault.py brief P1 "Tom …

    line 10
  2. Very specific:

    If they want a file to read or send: python3 tools/build_doc.py "Outputs/YYYY-MM-DD Brief — Subject.md", then copy the PDF or the Word file …

    line 17

“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

Brief

  1. Work out what the brief is for from what they said: a meeting (who will be there, which projects), a person, or a project. Ask only if it is unclear.
  2. Write it from the vault, with the project IDs and the people's names as the registers spell them: python3 tools/vault.py brief P1 "Tom Becker" --out "Outputs/YYYY-MM-DD Brief — Subject.md". The tool writes every line with its ID and a link to its source. Change nothing in it by hand: a correction goes into the registers, and the brief is built again.
  3. In the chat, give three to five lines for the meeting: what is decided, what is still open and who owns it, what is overdue or unverified. Each line names its IDs, as CLAUDE.md says under "Answers"; nothing comes from memory or the web.
  4. If they want a file to read or send: python3 tools/build_doc.py "Outputs/YYYY-MM-DD Brief — Subject.md", then copy the PDF or the Word file from build/ into Outputs/ under the same name.
  5. python3 tools/vault.py refresh, then python3 tools/vault.py check. Commit as Brief: Subject, then pull and push main as CLAUDE.md says under "Git". Give the links to the brief and its files on GitHub.

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.