event-follow-up SKILL.md skillA
event-follow-up from prosyo-ai/gtm-skill is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add prosyo-ai/gtm-skill/event-follow-up@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- prosyo-ai/gtm-skill
- Path
plugin/skills/event-follow-up/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0.0, committed Oct 23, 2026
- Size
- 3,948 bytes
- Repository stars
- 13
- License
- MIT
Use this skill when you need to turn a conference, trade show, webinar or roundtable into pipeline: "follow up with event leads", "post-webinar email", "trade show follow-up sequence", "pre-event outreach to book meetings". Plans pre-event outreach to book meetings, sorts leads after the event by conversation quality, and writes follow-ups that reference the actual conversation or session, with timing and channel for each lead group.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
Use this around any event. Most event leads go cold because follow-up is slow and generic; a fast follow-up that references the real conversation stands out from every other booth. ## Inputs - The event, your presence (booth, talk, sponsor, attendee) and dates. - Lead list with notes: who you spoke with and about what; webinar registrants and attendees. - What you presented or demoed. ## The play ### 1. Before the event: book meetings Two to three weeks before, reach target accounts attending: a short email or LinkedIn message with a reason to meet (a specific session, a private demo, a small dinner). Meetings booked before the event beat badge scans after it. ### 2. Sort leads within 24 hours | Group | Who | Follow-up | | --- | --- | --- | | Hot | Real conversation about a live need; asked for a next step | Personal email same or next day, meeting proposal | | Warm | Good conversation, no clear need yet | Personal email within 2 days, useful resource | | Session | Attended your talk or webinar | Recording, slides, one insight, soft ask | | Cold | Badge scan, giveaway, no conversation | Light nurture, not sales outreach | …
Read the whole file at its exact version.
How to install
mdr add prosyo-ai/gtm-skill/event-follow-up@sha256:2b4107d19ac9f863The line at the top of this page pins the label v1.0.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_t3btx2po2oaudmii)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 23, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3948 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
prosyo-ai/gtm-skill · 13 stars · license MIT · pushed 2026-10-26 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_t3btx2po2oaudmii GET https://markdownregistry.com/api/v1/resolve?ref=prosyo-ai/gtm-skill/event-follow-up GET https://markdownregistry.com/api/v1/blob/2b4107d19ac9f863752749fa623c9938835660782dfefb6915540dbcd5cd9d5c
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.