agentleFS
Sign inStart free
QuixiAIQuixiAI/Hexis/skills/installed/meeting-prep/SKILL.md

meeting-prep

Skill623 starsChanged 10 months agoMITView on GitHub

Prepare briefings for upcoming calendar events with attendee context and relevant memories

53 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use meeting-followup, social-listening and 6 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.
  • yakatotechSkill

    meeting-followup

    Create meeting minutes and follow-up email from meeting notes in one workflow. Execute all post-meeting tasks at once

    Also in 3 projects that use this

  • vivy-yiSkill

    social-listening

    Use when needing to understand audience needs, monitor brand mentions, track competitor activities, discover trends, or gather market intelligence from Xiaohongshu conversations

    Also in 3 projects that use this

  • refly-aiSkill

    zoom

    Integrate with Zoom for video meetings. Use when you need to: (1) schedule Zoom meetings, (2) create instant meetings, or (3) manage meeting details and invitations programmatically.

    Also in 3 projects that use this

  • vijpatel7Skill

    cold-outreach

    Write highly effective cold emails and LinkedIn messages to recruiters, hiring managers, founders, and engineers at target companies. Based on Ben Lang's proven cold outreach framework (Next Play). Use when the user wants to: (1) write a cold email to someone at a company they want to work for, (2) craft LinkedIn messages or InMail to recruiters or hiring managers, (3) reach out about unadvertised positions, (4) follow up on outreach or applications, (5) network with founders or executives for job opportunities, (6) prepare an outreach campaign to multiple companies. Triggers on: cold email, outreach, reach out to, contact recruiter, email founder, write to hiring manager, job email, networking email, LinkedIn message, InMail.

    Also in 4 projects that use this

  • AnthropicSkill

    standup

    Generate a standup update from recent activity. Use when preparing for daily standup, summarizing yesterday's commits and PRs and ticket moves, formatting work into yesterday/today/blockers, or structuring a few rough notes into a shareable update.

    Also in 5 projects that use this

  • Phoenixrr2113Skill

    morning-brief

    Full morning brief — calendar, email, meeting prep, execute actionable items, create follow-up tasks. Runs at 8:03 AM or when Randy asks for a morning update.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 48 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When the user asks "what do I have coming up" or "prep me for my next meeting"

    line 21
  2. Distinctive:

    When a daily briefing skill delegates meeting context to this skill

    line 22
  3. Distinctive:

    Before any meeting where attendee relationships or prior context would be valuable

    line 23
  4. Very specific:

    Identify the meeting: Use calendar_events to find the next upcoming event (or a specific one if the user named it).

    line 27
  5. Very specific:

    Recall prior interactions: Use recall with each attendee's name or company to surface past conversations, decisions, promises, or open …

    line 29
  6. Very specific:

    Recall topic context: If the meeting title or description references a project, product, or topic, run a targeted recall for that subject …

    line 30
  7. Distinctive:

    Keep briefings concise. A wall of text defeats the purpose.

    line 41
  8. Distinctive:

    If calendar credentials are unavailable, fall back to asking the user what meeting they want to prepare for.

    line 43
  9. Distinctive:

    When attendees are unknown, note this explicitly rather than guessing.

    line 44

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

Compile a briefing for an upcoming meeting by pulling together calendar details, attendee background, relevant memories, and suggested talking points.

When to Use

  • During heartbeats when a meeting is starting within the next 30-60 minutes
  • When the user asks "what do I have coming up" or "prep me for my next meeting"
  • When a daily briefing skill delegates meeting context to this skill
  • Before any meeting where attendee relationships or prior context would be valuable

Step-by-Step Methodology

  1. Identify the meeting: Use calendar_events to find the next upcoming event (or a specific one if the user named it). Extract the title, time, location/link, and attendee list.
  2. Look up attendees: For each attendee, call search_contacts to pull their name, role, company, and relationship notes. If a contact is unknown, note them as a new face.
  3. Recall prior interactions: Use recall with each attendee's name or company to surface past conversations, decisions, promises, or open items. Focus on the last 30 days of episodic memories.
  4. Recall topic context: If the meeting title or description references a project, product, or topic, run a targeted recall for that subject to gather relevant semantic and strategic memories.
  5. Synthesize the briefing: Combine all gathered context into a structured brief:
    • Meeting logistics (time, location, link)
    • Attendee profiles and relationship notes
    • Key context and recent history
    • Open items or promises to follow up on
    • Suggested talking points or questions
  6. Deliver or store: In chat context, present the briefing directly. In heartbeat context, store it as a working memory so it surfaces at the right time.

Quality Guidelines

  • Keep briefings concise. A wall of text defeats the purpose; aim for a scannable format with headers and bullets.
  • Prioritize actionable context over trivia. "You promised to send them the proposal by Friday" matters more than "they like coffee."
  • If calendar credentials are unavailable, fall back to asking the user what meeting they want to prepare for.
  • When attendees are unknown, note this explicitly rather than guessing. Suggest the user add them as contacts.
  • Respect the energy budget: skip deep recall when energy is low and provide a lighter briefing instead.

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.

Check your setup, free