agentleFS
sami2919sami2919/SignalForce/skills/meeting-followup/SKILL.md

meeting-followup

Skill9 starsChanged 3 months agoMITView on GitHub

Use when a meeting has been completed and you need to generate follow-up emails, when processing meeting notes to extract next steps and objections, or when routing post-meeting tasks based on meeting outcome

8 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use meeting-prep and research.

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.
  • OpenAISkill

    meeting-prep

    Use when creating Public Equity Investing meeting prep briefs. Do not use for private diligence, IB, FP&A, legal, or scheduling-only tasks.

    Also in 3 projects that use this

  • NVIDIASkill

    research

    Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 1

    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. Distinctive:

    Keep subject lines under 50 characters

    line 45
  2. Very specific:

    Stakeholder tasks: if stakeholders_needed is non-empty, create a task to arrange intro

    line 56
  3. Very specific:

    Re-qual flag: if outcome is negative, set reminder for 6 months

    line 57

“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 Follow-Up

Input

Provide one of:

  • Free-text meeting notes (transcript excerpt, CRM note, bullet points)
  • Structured MeetingOutcome record from scripts/models.py

Required fields: deal ID or company name, meeting date, attendees, outcome signal.

Step 1: Extract Structured Data

From notes, extract and populate a MeetingOutcome record:

FieldWhat to look for
outcomeBuying signal ("loved it", "interested") → positive; polite but vague → neutral; "not now", "no budget" → negative; no attendance → no_show
objectionsAny hesitation, technical concern, or blocker raised
next_stepsExplicit commitments or asks from either party
decision_timelineAny deadline or review window mentioned
stakeholders_neededNames or roles needed for sign-off
follow_up_resourcesDocs, case studies, or demos promised

Step 2: Select Template Sequence

Load config/templates/email-sequences/meeting-followup.md and select the block matching outcome:

  • positive → 3-email sequence (Day 0, 3, 7)
  • neutral → 3-email sequence (Day 0, 5, 14)
  • negative → 1 email only; flag for 6-month re-qualification
  • no_show → 2-email sequence (Day 0, 3)

Step 3: Generate Follow-Up Emails

For each email in the sequence:

  1. Fill all {{placeholders}} with data from MeetingOutcome
  2. Reference specific objections by name — never use generic language
  3. Tie resources to what was discussed, not generic product features
  4. Keep subject lines under 50 characters
  5. CTA must be low-friction: calendar link, async resource, or a direct question

Voice rules (from config/gtm-context.md): no "just checking in", no "hope this finds you well", no unsolicited demo asks.

Step 4: CRM and Sequencing Recommendations

Output a CRM action block:

  • Stage update: advance DealStage to MEETING_COMPLETED
  • Next touch date: Day 0 email send date + sequence cadence
  • Stakeholder tasks: if stakeholders_needed is non-empty, create a task to arrange intro
  • Re-qual flag: if outcome is negative, set reminder for 6 months

Output Format

## MeetingOutcome Record
[populated record]

## Follow-Up Sequence ([outcome])
### Email 1 — Day 0
Subject: ...
Body: ...

### Email 2 — Day N  (if applicable)
...

## CRM Actions
- Stage: MEETING_COMPLETED
- Next touch: [date]
- Tasks: [list]

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.