agentleFS
alectivismalectivism/maven-template/.claude/skills/briefing-prep/SKILL.md

briefing-prep

Skill1 starsChanged 6 months agoMITView on GitHub

Meeting prep — attendee info, past interactions, agenda, talking points. Use for "prep for", "brief me on", "meeting prep".

The file

Files
SKILL.md

Meeting Preparation

Process

Step 1: Identify the Meeting

  • Meeting name, date, time
  • Attendees (names and organizations)
  • Agenda or topic (if available)

Step 2: Gather Context

For each key attendee, collect:

  • Role & company — web search if needed
  • MMA relationship — member? board? prospect? partner?
  • Recent interactions — check email (Outlook) for recent correspondence
  • Asana tasks — any open tasks involving them or their company
  • Past meetings — check session logs for prior meeting notes

For the topic:

  • Related MMA programs — which think tanks, labs, or research is relevant
  • Recent developments — web search for industry news
  • Internal context — check SharePoint sites for relevant documents

Step 3: Build the Brief

Structure the output as:

Meeting Brief: [Meeting Name]

Date: [date/time] Duration: [if known]

Attendees

NameRoleCompanyMMA RelationshipNotes

Context

[2-3 sentences on why this meeting is happening and what matters]

Key Topics & Talking Points

  1. [Topic] — [your angle, data points to reference, questions to ask]
  2. [Topic] — [same]

Open Items

  • [Any pending action items with these people]
  • [Unresolved questions from past interactions]

Relevant MMA Assets

  • [Programs, research, or resources to reference]
  • [SharePoint links if applicable]

Suggested Outcomes

  • [What should this meeting accomplish?]
  • [What decisions need to be made?]

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.