agentleFS
alectivismalectivism/maven-template/.claude/skills/member-comms/SKILL.md

member-comms

Skill1 starsChanged 6 months agoMITView on GitHub

MMA member communications — onboarding, renewals, engagement, benefit summaries, member updates.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow-up cadence: Day 1 welcome, Week 2 engagement check, Month 1 value check

    line 35
  2. Distinctive:

    Check if there's relevant engagement data to personalize

    line 67

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Member Communications — MMA Standards

Member Segments

CMOs / Marketing Leaders

  • Decision-makers, time-scarce, results-oriented
  • Care about: peer connections, competitive advantage, evidence-based strategies
  • Tone: peer-to-peer, executive brevity
  • Reference: board composition (GM, Uber, Meta, Home Depot CMOs), CMO Alliance (350+ board members)

MarTech / AdTech Companies

  • Solution providers, innovation-focused
  • Care about: industry trends, client relationships, thought leadership positioning
  • Tone: collaborative, opportunity-focused
  • Reference: Future Labs partnerships, POSSIBLE sponsorship, SMARTIES recognition

Agency / Media Companies

  • Campaign executors, trend followers
  • Care about: creative effectiveness, measurement, client value
  • Tone: practical, data-driven
  • Reference: ACE (creative scoring), measurement frameworks, MMGF results

Communication Types

Welcome / Onboarding

  • Warm but efficient — respect their decision to join
  • Highlight top 3 immediate benefits they can access
  • Include key contacts (membership team: Stephen Wellman, Amanda Hyland, Shauna Peck)
  • Link to: member portal, Slack workspace, upcoming events
  • Follow-up cadence: Day 1 welcome, Week 2 engagement check, Month 1 value check

Renewal Outreach

  • Lead with value delivered (events attended, research accessed, connections made)
  • Include member-specific engagement data if available
  • Reference upcoming programs/events they'd miss
  • Soft urgency — don't pressure, demonstrate value

Program Announcements

  • Clear subject line: [Program Name] — [Key Benefit]
  • One paragraph: what it is and why it matters
  • Bullet list: key details (dates, cost, how to participate)
  • Single CTA

Event Invitations

  • Segment by relevance (don't invite everyone to everything)
  • Lead with "why this event matters for you"
  • Include social proof (past attendee quotes, NPS scores)

Value Propositions by Benefit Area

AreaPitch
Research"Access $3M+ in proprietary research that quantifies what works in marketing"
AI Labs"Test AI innovations with zero risk — free labs in personalization, creative, targeting, and audience discovery"
Peer Network"Join 350+ CMOs and marketing leaders who share challenges and solutions openly"
Events"Attend the industry's highest-rated executive gatherings (NPS 86% CMO Summit)"
Training"Upskill your team with DAM (2,100+ certified) and MAC certification"
Measurement"Benchmark your measurement maturity against 800+ companies"

Process

  1. Identify audience segment and communication type
  2. Check if there's relevant engagement data to personalize
  3. Draft with appropriate tone for segment
  4. Include specific value propositions and CTAs
  5. Present for review — always confirm before sending

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.