agentleFS
Sign inStart free
ShawhinTShawhinT/non-coding-skills/meeting-prep/SKILL.md

meeting-prep

Skill40 starsChanged 13 days agoNo licenceView on GitHub

Prep Shaw for an upcoming meeting — a discovery call, a paid 1:1 Claude Workshop, a post-session or nurture check-in, a multi-session engagement wrap-up, a partner/channel call, or a recurring client sync. Use whenever Shaw asks to prep for a meeting or call, do pre-call research, or gather context before any conversation — \"prep for my call with X\", \"meeting prep for X\", \"do pre-call research for X\", \"I have a call with X today\", \"what should I bring up at the X sync\", or any reference to preparing for an upcoming meeting. Also trigger when Shaw mentions a person's name alongside a scheduled call; even casual mentions like \"call with X later\" or \"meeting with X, what should I know?\" count. Also invoked by CRM Workflow 7 (Discovery Call Intake) to create and populate the ABA Calls page for a freshly-booked discovery call. Covers prospects, clients, past clients, and partners.

53 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use email-digest, meeting-followup 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.
  • QuixiAISkill

    email-digest

    Digest and ingest emails into memory, surfacing important threads and action items

    Also in 3 projects that use this

  • 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

  • MicrosoftSkill

    inbox-triage

    Use this skill whenever the user asks to clean up, triage, declutter, or archive low-value Outlook inbox mail - "clean up my inbox", "triage my mail", "declutter my inbox", "sort out newsletters", "archive old resolved threads", "/inbox-triage" - to group only newsletters, auto-notifications, past-event meeting logistics, resolved threads, and redundant duplicates into reviewable move-proposals presented for per-bucket approval before any message moves. Do not use for reading mail, drafting or sending replies, deleting mail, executing moves without explicit per-bucket approval, or acting on messages from the user's manager, direct reports, active threads, flagged mail, or labelled/HR/Legal/Finance/Security senders.

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

The file

We split this skill into the rules it gives an agent

11 rules. 0 are common, 7 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 49 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

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

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