beam-ai-team/follow-up-automation
skills/general/follow-up-automation/SKILL.md
Streamlined follow-up system for sales calls based on call transcripts. Load when user mentions "follow-up", "follow up email", "call follow-up", "send follow-up", "post-call follow-up", "follow-up automation", "create follow-up", "generate follow-up", or when user provides a call transcript and needs to send follow-up communication and update CRM. Analyzes call transcripts to extract technical requirements, decision makers, timeline, and pain points, then generates concise technical follow-up emails (under 200 words) and updates CRM with lead status and next steps.
tools
Updated May 7, 2026
$ install --global
skillsauthnpx skillsauth add beam-ai-team/beam-next-skills follow-up-automationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 7, 2026, 3:24 AM121.9s1 file scanned
SKILL.md
- name:
- follow-up-automation
- version:
- 1.0
- description:
- Streamlined follow-up system for sales calls based on call transcripts.
- author:
- Quentin
- category:
- general
- updated:
- 2025-12-12
- visibility:
- team
Follow-up Automation
Streamlined follow-up system that analyzes call transcripts and generates concise technical follow-up emails with CRM updates.
Purpose
This skill automates post-call follow-up workflows by:
- Analyzing call transcripts to extract key insights (technical requirements, decision makers, timeline, pain points)
- Generating concise, action-focused follow-up emails (under 200 words)
- Updating CRM with lead status, next steps, and decision timeline
Key Features:
- Technical focus (removes partnership/strategic language)
- Professional tone matching call language
- Clear next steps and timeline
- Simple CRM integration
Time Estimate: 5-10 minutes per follow-up
Workflow
Step 1: Initialize TodoList
Create TodoWrite with all workflow steps:
- [ ] Receive and analyze call transcript
- [ ] Extract key insights and technical requirements
- [ ] Generate follow-up email draft
- [ ] Review and refine email
- [ ] Update CRM with call notes and next steps
- [ ] Close session to save progress
This creates transparency and allows progress tracking.
Mark tasks complete as you finish each step.
Step 2: Analyze Call Transcript
Actions:
- Request call transcript from user (if not already provided)
- Extract essential call components:
- Technical Requirements: Key technical needs and integration points
- Decision Makers: Who needs to be involved in next steps
- Timeline: When decisions need to be made
- Pain Points: Main challenges to address
Mark this todo complete before proceeding.
Step 3: Generate Follow-up Email
Create concise, technical follow-up email using this structure:
Email Structure:
-
Concise Opening (1 sentence)
- Brief thank you and call recap
- Example: "Thanks for the call today—great discussion about [main topic]."
-
Technical Details (2-3 sentences)
- Specific next steps and access information
- Address key technical questions raised
- Example: "Based on our discussion, I'll send over evaluation access to [product] for your team to test [specific use case]."
-
Clear Timeline (1 sentence)
- When things will happen
- Example: "I'll follow up on Friday to check on progress and address any questions."
-
Simple CTA (1 sentence)
- What they need to do next
- Example: "Let me know if you need anything else in the meantime."
Quality Guidelines:
- Keep under 200 words (3-4 paragraphs maximum)
- Focus on technical details, not partnership language
- Professional tone matching the call
- Clear, specific actions with timelines
Mark this todo complete before proceeding.
Step 4: Review and Refine
Actions:
- Present draft email to user
- Ask: "Does this capture the key points? Any changes?"
- Refine based on feedback
- Confirm final version
Mark this todo complete before proceeding.
Step 5: Update CRM
Create simple CRM update with:
Call Notes:
- Key technical points discussed
- Specific requirements or pain points mentioned
- Decision makers involved
Follow-up Status:
- What's been sent (evaluation access, docs, etc.)
- What's pending (next meeting, follow-up call)
Decision Timeline:
- When to expect next contact
- Key dates or milestones
Technical Fit:
- How well requirements match capabilities
- Any red flags or concerns
Format: Present as structured text block user can copy-paste into CRM
Mark this todo complete before proceeding.
Step 6: Share to Team (Optional but Recommended)
After using this skill successfully, consider sharing it with the team via Notion:
Benefits of sharing:
- Team discovers and reuses your work
- Collaborative improvement (others can update)
- Centralized skill library for the company
To share:
Say "export this skill to Notion" or use the export-skill-to-notion skill.
What happens:
- AI packages the skill (or uses existing .skill file)
- AI infers Team (likely "Sales" for this workflow)
- You confirm metadata before pushing
- Skill appears in "Beam Nexus Skills" database
- Teammates can query and import with
query-notion-dbandimport-skill-to-nexus
Skip this if:
- Skill is personal/experimental/not ready to share
- Contains sensitive or client-specific info
Mark this todo complete after deciding (share or skip).
Final Step: Close Session
Once the workflow is complete, automatically trigger the close-session skill:
Auto-triggering close-session to save progress...
The close-session skill will:
- Update system memory
- Save context for next session
- Create session report
- Clean up temporary files
This is the final mandatory step. Do not skip - it ensures all progress is preserved.
Follow-up Sequence Timing
Immediate Follow-up (Within 24 hours)
- Provide technical access or demo scheduling
- Address specific technical questions raised
- Clear timeline for follow-up actions
- Relevant technical documentation only
Short-term Follow-up (1-3 days)
- Check on evaluation progress
- Address additional questions
- Include decision makers if needed
- Schedule technical deep-dive or decision meeting
Notes
About Email Quality:
- Maximum 200 words keeps emails scannable
- Technical focus maintains professionalism
- Clear CTAs drive next steps
- Matching call tone builds rapport
About CRM Updates:
- Focus on actionable information
- Track technical fit for qualification
- Document decision timeline for follow-up scheduling
- Keep notes concise but complete
Related Skills
beam-ai-team/skills/general/taste-skill
development
VerifiedTrustedCommunity
--- name: taste-skill type: skill version: '1.0' author: Leonxlnx (packaged by Zhichao Li) category: general tags: - frontend - design - anti-slop - landing-page updated: '2026-06-11' visibility: public description: Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check. license: MIT.
SKILL.mdUpdated Jun 12, 2026
beam-ai-team/numbers
development
VerifiedTrustedCommunity
Use when communicating quantitative information in any form — Slack updates, emails, reports, decks, dashboards, landing pages, product UI, public talks. Covers two integrated layers: (1) making numbers semantically meaningful (translation, anchoring, simplification, story-pairing) and (2) showing numbers cleanly (chart vs table vs prose, chart-by-message, pre-attentive emphasis, color discipline, decluttering). Distilled and integrated from *Show Me the Numbers* (Stephen Few) and *Make Numbers Count* (Chip Heath & Karla Starr). Not for raw data analysis or statistics — this is about communication of numbers, not their derivation.
SKILL.mdUpdated Jun 12, 2026
beam-ai-team/impeccable
development
VerifiedTrustedCommunity
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
SKILL.mdUpdated Jun 12, 2026
beam-ai-team/beam-teach
tools
VerifiedTrustedCommunity
Stateful multi-session tutor adapted for Beam — teach a stakeholder to understand, trust, and operate a specific agent, or teach a Solution Engineer a client's business process for delivery. Grounds every lesson in Knowledge Hub sources (real agent graphs, real tasks, transcripts, Linear) before any web resource. Also works for any general topic. Trigger on "teach me", "beam teach", "教我", "onboard <person> on <agent>", "help <stakeholder> understand the agent", "learn this client's process".
SKILL.mdUpdated Jun 12, 2026