agentleFS
Nomanriaz786Nomanriaz786/claude-consulting-team/skills/meeting-brief/SKILL.md

meeting-brief

Skill1 starsChanged 26 days agoMITView on GitHub

Prepares an executive meeting brief when a leader needs context, objectives, stakeholder positions and response options.

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 2

    Distinctive

    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:

    Use before a consequential client, board, partner or governance meeting with limited preparation time.

    line 9
  2. Distinctive:

    Use: Meeting Objective, Participants, Context, Stakeholder Positions, Key Messages, Difficult Questions, Boundaries, Agenda Tactics and …

    line 26

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

Meeting Brief

When to use it

Use before a consequential client, board, partner or governance meeting with limited preparation time.

What Claude needs

  • client-context.md and meeting purpose
  • Agenda, participants and decision rights
  • Relevant history, commitments and sensitivities
  • Desired outcome, boundaries and supporting evidence

Method

  1. Define the primary outcome and minimum acceptable outcome.
  2. Map participants by position, interest, influence and likely concern.
  3. Summarise relevant history, commitments and unresolved points.
  4. Develop key messages supported by concise evidence.
  5. Anticipate difficult questions and prepare direct responses.
  6. Set opening, decision moments, concessions and follow-up actions.

Output format

Use: Meeting Objective, Participants, Context, Stakeholder Positions, Key Messages, Difficult Questions, Boundaries, Agenda Tactics and Follow-up.

Quality checks

  • Advice reflects known stakeholder positions, not invented motives.
  • Key messages align with approved organisational positions.
  • Desired decisions and boundaries are specific.

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.