[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EMZD894FBWNSTNNACEYMXH":3,"skill-same:01M7EMZD894FBWNSTNNACEYMXH":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7EMZD894FBWNSTNNACEYMXH","event-marketing",null,"Plan and promote events — conferences, trade shows, webinars-as-events, and field marketing that drives pipeline.","TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-event-marketing\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: event-marketing\ndescription: Plan and promote events — conferences, trade shows, webinars-as-events, and field marketing that drives pipeline.\ncategory: business-marketing\n---\n\n## Overview\n\nEvent marketing creates high-trust, high-attention moments: conferences, trade shows, executive dinners, roadshows, and owned summits. This skill covers event strategy (own vs. sponsor vs. attend), promotion that fills seats, on-site execution that captures demand, and post-event follow-up that converts conversations into pipeline.\n\n## When to use\n\n- Deciding which events to sponsor or attend\n- Planning an owned event (summit, dinner, roadshow)\n- Promoting an event to hit attendance targets\n- Maximizing ROI from a trade show booth\n- Building post-event follow-up sequences\n- Measuring event-sourced pipeline\n\n- Deciding between virtual, hybrid, or in-person formats\n- Building event sponsorship packages\n- Creating year-round community from annual events\n- Measuring event influence on pipeline\n## Core concepts\n\n**Event strategy tiers.** Own (full control, highest cost\u002Feffort: summits, dinners), sponsor (borrowed audience: booths, speaking slots), attend (networking, lowest cost). Match tier to goal: pipeline → sponsor\u002Fown with speaking; relationships → intimate dinners; awareness → large conferences.\n\n**Audience-first planning.** Define exactly who should attend (titles, companies, pains) before choosing venue, format, or content. An event for \"everyone\" attracts no one valuable.\n\n**Promotion mix.** Email (to house list and partners), paid social (targeted by title\u002Fcompany), partner co-marketing, speaker promotion (speakers bring audiences), SDR outreach to target accounts, and community posts. Start promotion 6–8 weeks out; most registrations come in the final 2 weeks.\n\n**Content and experience.** Agenda built around attendee problems, not your product. Interactive formats (panels, workshops, roundtables) beat lecture marathons. Feed people well; details signal quality.\n\n**Lead capture.** Badge scanning, session check-ins, demo bookings, content downloads on-site. Define what counts as a \"lead\" before the event — a scanned badge is not a qualified lead.\n\n**Follow-up velocity.** Speed wins: follow up within 24–48 hours while memory is fresh. Segment by engagement level (hot: requested demo → sales within 24h; warm: nurture sequence; cold: thank-you + content).\n\n\n**Format selection.** In-person: relationship depth, high cost, limited reach. Virtual: scale and data, low engagement depth. Hybrid: both audiences, double production complexity.\nChoose by goal: pipeline acceleration favors in-person; brand reach favors virtual; community favors recurring small formats over annual spectacles.\n**Sponsorship design.** Tier by outcomes sponsors actually buy: lead generation (badge scans, session attendance), brand visibility (keynotes, signage), and thought leadership (speaking slots).\nPrice on value delivered, not on your costs. Overpriced sponsorships with weak ROI kill renewals.\n**Content capture.** Every session recorded, transcribed, and atomized: highlight clips, quote graphics, blog recaps, podcast episodes.\nEvent content should fuel 3 months of marketing — plan capture (cameras, mics, permissions) before the event, not after.\n## Practical workflow\n\n1. **Set goals and budget.** Pipeline target, attendance target, cost per attendee\u002FSQL. Work backward to required registrations (assume 40–60% show rate for free events).\n2. **Choose format and venue.** Match format to audience size and goal. Venue checklist: location convenience, AV quality, wifi capacity, catering, branding opportunities.\n3. **Build the program.** Agenda with attendee value first. Recruit speakers (customers and industry voices draw better than executives). Plan networking deliberately — structured mixers beat hoping people mingle.\n4. **Promote.** Launch registration page (short form — every field costs signups), run the promotion mix, send reminder sequence (1 week, 1 day, morning-of). Track registrations by source.\n5. **Execute.** Run-of-show document (minute-by-minute), staff briefings, lead capture process tested, social coverage plan, contingency plans (speaker no-show, tech failure).\n6. **Follow up and measure.** 24–48h follow-up sequences by segment. Debrief within a week. Measure: attendance, engagement, leads by quality tier, pipeline sourced\u002Finfluenced, cost per SQL, and ROI vs. target.\n\n**Run-of-show essentials:** timeline, owner per item, speaker contacts, AV cues, catering times, lead capture process, social posts scheduled, emergency contacts.\n\n\n**Event ROI model:** define the primary goal first (pipeline, brand, community), then set targets: registrations → attendance rate (aim 40–60% for free virtual, 70–85% for paid in-person) → engaged attendees (participated in 2+ sessions or visited sponsor booths) → qualified follow-ups → pipeline influenced. Cost per qualified lead = total event cost \u002F qualified follow-ups; compare against your blended CPL before declaring success.\n\n**Run-of-show essentials:** minute-by-minute agenda with owners, speaker prep calls 1 week out (tech check + content review), dry run for keynotes, backup plans for AV\u002Finternet failure, real-time social coverage plan, and a lead-capture method tested before doors open. Assign one person as the single decision-maker for day-of changes.\n\n**Pre-event promotion timeline:** 8 weeks: save-the-date to core audience → 6 weeks: agenda published, early-bird opens → 4 weeks: speaker announcements (staggered) → 2 weeks: urgency push (\"selling out\") → 1 week: logistics emails → day-before: final reminders.\nRegistration curves are predictable — 50%+ registers in the final 2 weeks. Plan promotion spend accordingly.\n**Post-event follow-up (within 48 hours):** thank-you + recording to attendees → content assets to no-shows → hot-lead alerts to sales (session attendance = intent signal) → survey (keep under 5 questions) → social recap.\nSpeed matters: follow-up after 1 week converts at half the rate.\n## Common pitfalls\n\n- **No clear goal.** \"Brand awareness\" without pipeline targets makes ROI unprovable. Define success metrics upfront.\n- **Late promotion.** Starting 3 weeks out and wondering why attendance is thin. Promote 6–8 weeks ahead.\n- **Product-pitch agendas.** Attendees come to learn, not to be sold to. Lead with their problems.\n- **Weak follow-up.** Collecting 500 badges and emailing them all a generic \"great meeting you\" a month later. Speed + segmentation.\n- **Counting badges as leads.** Inflated success metrics. Qualify on-site or score post-event.\n- **Ignoring the no-show rate.** Planning catering and staffing for registrations, not actual attendance (typically 40–60% of free registrations).\n- **No debrief.** Repeating the same mistakes next event. Document learnings within a week.\n- **No follow-up plan before the event.** Leads go cold within 48 hours. Write the follow-up emails and assign owners before the event starts, not after.\n- **Measuring attendance instead of outcomes.** 500 attendees means nothing without engagement and pipeline data. Instrument the event like a campaign.\n- **Vanity attendance goals.** Optimizing for headcount over right-fit attendees. 100 ideal prospects beat 1,000 random registrants.\n- **No sales alignment.** Marketing celebrates attendance; sales ignores the leads. Joint planning on follow-up before the event is mandatory.\n- **No-shows ignored.** Accepting 50% no-show rates as normal. Reminder sequences, calendar holds, and commitment devices cut no-shows significantly.\n- **Generic swag.** Forgettable giveaways. Useful, quality items get kept — cheap items get trashed with your brand on them.\n- **Skipping debriefs.** No post-event retrospective. Document learnings within a week or repeat the same mistakes.\n","## Overview\n\nEvent marketing creates high-trust, high-attention moments: conferences, trade shows, executive dinners, roadshows, and owned summits. This skill covers event strategy (own vs. sponsor vs. attend), promotion that fills seats, on-site execution that captures demand, and post-event follow-up that converts conversations into pipeline.\n\n## When to use\n\n- Deciding which events to sponsor or attend\n- Planning an owned event (summit, dinner, roadshow)\n- Promoting an event to hit attendance targets\n- Maximizing ROI from a trade show booth\n- Building post-event follow-up sequences\n- Measuring event-sourced pipeline\n\n- Deciding between virtual, hybrid, or in-person formats\n- Building event sponsorship packages\n- Creating year-round community from annual events\n- Measuring event influence on pipeline\n## Core concepts\n\n**Event strategy tiers.** Own (full control, highest cost\u002Feffort: summits, dinners), sponsor (borrowed audience: booths, speaking slots), attend (networking, lowest cost). Match tier to goal: pipeline → sponsor\u002Fown with speaking; relationships → intimate dinners; awareness → large conferences.\n\n**Audience-first planning.** Define exactly who should attend (titles, companies, pains) before choosing venue, format, or content. An event for \"everyone\" attracts no one valuable.\n\n**Promotion mix.** Email (to house list and partners), paid social (targeted by title\u002Fcompany), partner co-marketing, speaker promotion (speakers bring audiences), SDR outreach to target accounts, and community posts. Start promotion 6–8 weeks out; most registrations come in the final 2 weeks.\n\n**Content and experience.** Agenda built around attendee problems, not your product. Interactive formats (panels, workshops, roundtables) beat lecture marathons. Feed people well; details signal quality.\n\n**Lead capture.** Badge scanning, session check-ins, demo bookings, content downloads on-site. Define what counts as a \"lead\" before the event — a scanned badge is not a qualified lead.\n\n**Follow-up velocity.** Speed wins: follow up within 24–48 hours while memory is fresh. Segment by engagement level (hot: requested demo → sales within 24h; warm: nurture sequence; cold: thank-you + content).\n\n\n**Format selection.** In-person: relationship depth, high cost, limited reach. Virtual: scale and data, low engagement depth. Hybrid: both audiences, double production complexity.\nChoose by goal: pipeline acceleration favors in-person; brand reach favors virtual; community favors recurring small formats over annual spectacles.\n**Sponsorship design.** Tier by outcomes sponsors actually buy: lead generation (badge scans, session attendance), brand visibility (keynotes, signage), and thought leadership (speaking slots).\nPrice on value delivered, not on your costs. Overpriced sponsorships with weak ROI kill renewals.\n**Content capture.** Every session recorded, transcribed, and atomized: highlight clips, quote graphics, blog recaps, podcast episodes.\nEvent content should fuel 3 months of marketing — plan capture (cameras, mics, permissions) before the event, not after.\n## Practical workflow\n\n1. **Set goals and budget.** Pipeline target, attendance target, cost per attendee\u002FSQL. Work backward to required registrations (assume 40–60% show rate for free events).\n2. **Choose format and venue.** Match format to audience size and goal. Venue checklist: location convenience, AV quality, wifi capacity, catering, branding opportunities.\n3. **Build the program.** Agenda with attendee value first. Recruit speakers (customers and industry voices draw better than executives). Plan networking deliberately — structured mixers beat hoping people mingle.\n4. **Promote.** Launch registration page (short form — every field costs signups), run the promotion mix, send reminder sequence (1 week, 1 day, morning-of). Track registrations by source.\n5. **Execute.** Run-of-show document (minute-by-minute), staff briefings, lead capture process tested, social coverage plan, contingency plans (speaker no-show, tech failure).\n6. **Follow up and measure.** 24–48h follow-up sequences by segment. Debrief within a week. Measure: attendance, engagement, leads by quality tier, pipeline sourced\u002Finfluenced, cost per SQL, and ROI vs. target.\n\n**Run-of-show essentials:** timeline, owner per item, speaker contacts, AV cues, catering times, lead capture process, social posts scheduled, emergency contacts.\n\n\n**Event ROI model:** define the primary goal first (pipeline, brand, community), then set targets: registrations → attendance rate (aim 40–60% for free virtual, 70–85% for paid in-person) → engaged attendees (participated in 2+ sessions or visited sponsor booths) → qualified follow-ups → pipeline influenced. Cost per qualified lead = total event cost \u002F qualified follow-ups; compare against your blended CPL before declaring success.\n\n**Run-of-show essentials:** minute-by-minute agenda with owners, speaker prep calls 1 week out (tech check + content review), dry run for keynotes, backup plans for AV\u002Finternet failure, real-time social coverage plan, and a lead-capture method tested before doors open. Assign one person as the single decision-maker for day-of changes.\n\n**Pre-event promotion timeline:** 8 weeks: save-the-date to core audience → 6 weeks: agenda published, early-bird opens → 4 weeks: speaker announcements (staggered) → 2 weeks: urgency push (\"selling out\") → 1 week: logistics emails → day-before: final reminders.\nRegistration curves are predictable — 50%+ registers in the final 2 weeks. Plan promotion spend accordingly.\n**Post-event follow-up (within 48 hours):** thank-you + recording to attendees → content assets to no-shows → hot-lead alerts to sales (session attendance = intent signal) → survey (keep under 5 questions) → social recap.\nSpeed matters: follow-up after 1 week converts at half the rate.\n## Common pitfalls\n\n- **No clear goal.** \"Brand awareness\" without pipeline targets makes ROI unprovable. Define success metrics upfront.\n- **Late promotion.** Starting 3 weeks out and wondering why attendance is thin. Promote 6–8 weeks ahead.\n- **Product-pitch agendas.** Attendees come to learn, not to be sold to. Lead with their problems.\n- **Weak follow-up.** Collecting 500 badges and emailing them all a generic \"great meeting you\" a month later. Speed + segmentation.\n- **Counting badges as leads.** Inflated success metrics. Qualify on-site or score post-event.\n- **Ignoring the no-show rate.** Planning catering and staffing for registrations, not actual attendance (typically 40–60% of free registrations).\n- **No debrief.** Repeating the same mistakes next event. Document learnings within a week.\n- **No follow-up plan before the event.** Leads go cold within 48 hours. Write the follow-up emails and assign owners before the event starts, not after.\n- **Measuring attendance instead of outcomes.** 500 attendees means nothing without engagement and pipeline data. Instrument the event like a campaign.\n- **Vanity attendance goals.** Optimizing for headcount over right-fit attendees. 100 ideal prospects beat 1,000 random registrants.\n- **No sales alignment.** Marketing celebrates attendance; sales ignores the leads. Joint planning on follow-up before the event is mandatory.\n- **No-shows ignored.** Accepting 50% no-show rates as normal. Reminder sequences, calendar holds, and commitment devices cut no-shows significantly.\n- **Generic swag.** Forgettable giveaways. Useful, quality items get kept — cheap items get trashed with your brand on them.\n- **Skipping debriefs.** No post-event retrospective. Document learnings within a week or repeat the same mistakes.\n",{"name":5,"category":24,"description":7},"business-marketing","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-event-marketing",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill event-marketing",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill event-marketing",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill event-marketing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-event-marketing\u002FSKILL.md",true,[],[48,55,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]