skills/beam-next-learning/learn-integrations/SKILL.md
Learn about Beam Next integrations and MCP. Load when user mentions: learn integrations, what is MCP, connect tools, integration tutorial, add integration, external tools, API connections, third party, how to integrate. 10-12 min.
npx skillsauth add beam-ai-team/beam-next-skills learn-integrationsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This is an ONBOARDING skill with HIGH PRIORITY for proactive suggestion.
Check learning_tracker.completed.learn_integrations in user-config.yaml. If false:
PROACTIVELY SUGGEST when user:
Suggestion Pattern:
💡 I notice you haven't learned about integrations yet. Understanding how Beam Next
connects to external tools (like [tool they mentioned]) takes about 10 minutes
and will help you work more efficiently.
Would you like to run 'learn integrations' now? (You can always do it later)
DO NOT suggest if:
learning_tracker.completed.learn_integrations: trueLearn how to connect external tools to Beam Next via MCP (Model Context Protocol).
This skill teaches you how integrations work in Beam Next — what they are, which ones are available, and when/how to add them. By the end, you'll understand:
Time Estimate: 10-12 minutes
Ask: "Before we dive in — do you currently use any external tools for your work? Things like GitHub, Notion, Slack, Airtable, Google Drive, or Linear?"
Listen for: Tools they already use, how they use them, pain points.
Respond based on answer:
Display:
--- WHAT IS MCP? -------------------------------------------
MCP (Model Context Protocol) is like a universal adapter.
It lets me connect to your external tools and work with them directly.
WITHOUT MCP:
You: "Check my GitHub issues"
Me: "I can't access GitHub directly. Please copy-paste the info."
You: [manually copies data]
WITH MCP:
You: "Check my GitHub issues"
Me: [directly queries GitHub] "You have 5 open issues..."
Think of MCP as building bridges between Beam Next and your tools.
------------------------------------------------------------
Ask: "Does that make sense? Any questions about what MCP does?"
Display:
--- CORE INTEGRATIONS --------------------------------------
Beam Next includes master skills for these integrations:
🔷 BUILT-IN (Ready to Configure)
• Notion → "connect notion" → Databases, pages, search
• Airtable → "connect airtable" → Bases, records, automation
• Slack → "connect slack" → Messages, channels, team comms
• Google → "connect google" → Gmail, Docs, Sheets, Calendar, Drive, Tasks, Slides
• HubSpot → "connect hubspot" → CRM, contacts, deals
• Beam.ai → "beam" commands → AI agent workflows
[PLUG] MCP SERVERS (Via add-integration skill)
• GitHub → Repos, issues, PRs, actions
• Linear → Issues, projects, roadmaps
• PostgreSQL → Direct database queries
• Filesystem → Local file operations
• And 50+ more via MCP directory
------------------------------------------------------------
Ask: "Any of these tools sound relevant to your work?"
Display:
--- INTEGRATION DECISION FRAMEWORK -------------------------
[OK] ADD AN INTEGRATION WHEN:
• You frequently copy-paste data from a tool
• You want automated workflows (e.g., create GitHub issue from task)
• You need real-time data (e.g., check Slack messages)
• The tool is central to your daily work
[ERROR] SKIP INTEGRATION WHEN:
• You rarely use the tool
• Manual copy-paste is fast enough
• The tool doesn't have MCP support
• You prefer keeping systems separate
REMEMBER: Beam Next works perfectly standalone!
Integrations are power-ups, not requirements.
------------------------------------------------------------
Confirm: "Make sense? The key is: integrate what adds value to YOUR workflow."
Display:
--- ADDING INTEGRATIONS ------------------------------------
METHOD 1: Built-in Master Skills
Just say the command:
• "connect notion" → Notion setup wizard
• "connect airtable" → Airtable setup wizard
METHOD 2: MCP Server Setup
Say "add integration" → I'll guide you through:
1. Installing the MCP server
2. Getting API credentials
3. Configuring the connection
4. Testing it works
5. Documenting in your Memory
TIME: 10-20 minutes per integration
------------------------------------------------------------
Display:
--- EXAMPLE: NOTION INTEGRATION ----------------------------
BEFORE (No Integration):
You: "Add this task to my Notion board"
Me: "I can't access Notion. Here's the formatted text to copy..."
You: [Opens Notion, manually adds task]
AFTER (With Integration):
You: "Add this task to my Notion board"
Me: [Directly creates task in Notion] "Done! Added to your Tasks database."
OTHER USE CASES:
• "Query my projects database in Notion"
• "Sync session report to Notion"
• "Search my notes for [topic]"
------------------------------------------------------------
Ask: "Would you like to set up an integration now, or save it for later?"
IF YES (wants to integrate now):
notion-connectairtable-connectslack-connect (Slack lives under integrations/slack, not Google)google-connect, then the specific product skill as neededhubspot-connectadd-integrationIF NO (save for later):
'connect notion' for Notion'connect airtable' for Airtable'connect slack' for Slack'connect google' for Google Workspace (Gmail, Docs, Sheets, Calendar, Drive, Tasks, Slides)'add integration' for any other toolActions (MUST complete all):
Mark skill complete in user-config.yaml:
learning_tracker:
completed:
learn_integrations: true # ADD THIS LINE
Display completion:
[OK] Learn Integrations Complete!
You now understand:
• What MCP is (universal adapter for tools)
• Available integrations (Notion, Airtable, Slack, Google, HubSpot, etc.)
• When to integrate (adds value) vs skip (overhead)
• How to add them (connector skills or 'add integration')
Next steps:
• 'connect notion' / notion-connect
• 'connect airtable' / airtable-connect
• 'connect slack' / slack-connect
• 'connect google' / google-connect (Workspace)
• 'connect hubspot' / hubspot-connect
• 'add integration' - Other MCP tools
• 'learn projects' or 'learn skills' - Continue learning
Session ending tip:
💡 When you're done, open a NEW chat for your next topic.
learning_tracker.completed.learn_integrations: true in user-config.yamlKey Messages:
Related Skills:
add-integration - General MCP server setupnotion-connect / notion-master - Notionairtable-connect / airtable-master - Airtableslack-connect / slack-master - Slackgoogle-connect / google-master - Google Workspacehubspot-connect / hubspot-crm - HubSpotResources:
development
--- 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.
development
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.
development
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.
tools
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".