skills/beam/beam/beam-connect/SKILL.md
Connect to Beam AI workspace for runtime agent operations. Load when user mentions 'beam', 'beam agent', 'beam task', 'beam analytics', 'list agents', 'create task', 'debug task', 'feedback automation', 'agent pricing', or any Beam AI runtime operations. Meta-skill that validates config, discovers agents, and routes to appropriate operations. For build-time operations (create/modify/optimize agent graphs), use beam-agent-manager instead.
npx skillsauth add beam-ai-team/beam-next-skills beam-connectInstall 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.
User-facing meta-skill for Beam AI workspace integration.
Single entry point for all Beam AI operations:
Follows the master/connect pattern - references beam-master for shared scripts and references.
Before any command that creates tasks, retries tasks, approves/rejects HITL work, updates graph nodes, or otherwise changes Beam state, show the target workspace, agent/task/node IDs, payload summary, and expected side effects. Require explicit user approval in the current turn. Read-only discovery, analytics, status checks, and local draft preparation do not require approval.
Load this skill when user says:
Before ANY Beam operation, validate configuration:
python skills/beam/beam/beam-master/scripts/check_beam_config.py --json
| ai_action | What to Do |
|-------------|------------|
| proceed_with_operation | Config OK → Continue |
| prompt_for_api_key | Ask user for API key, save to .env |
| prompt_for_workspace_id | Ask user for workspace ID, save to .env |
| run_setup_wizard | Run interactive setup |
I need to set up Beam AI integration first.
To get your credentials:
1. Log into Beam AI (app.beam.ai)
2. Go to Settings → API Keys
3. Create a new API key
4. Also get your Workspace ID from Settings → Workspace
Please provide:
1. Your Beam API key:
After user provides key:
# Write to .env
BEAM_API_KEY=xxx
BEAM_WORKSPACE_ID=workspace-id
# Re-run config check to verify
python skills/beam/beam/beam-master/scripts/check_beam_config.py --json
Trigger: Before any operation
Script: check_beam_config.py --json
Output: Config status, required actions
Trigger: "list agents", "show beam agents", "my agents"
python skills/beam/beam/beam-master/scripts/list_agents.py --json
Display Format:
Found 5 agents in your workspace:
1. Customer Support Agent
ID: abc-123-def
Type: beam-os
Created: 2024-01-15
2. Email Processor
ID: ghi-456-jkl
...
Cache agents for future reference:
Trigger: "get agent graph", "show agent workflow", "agent config for X"
python skills/beam/beam/beam-master/scripts/get_agent_graph.py --agent-id AGENT_ID --json
Display: Show nodes, connections, entry/exit points
Trigger: "create task", "run agent", "execute agent X"
Required: Agent ID, task query Optional: URLs to parse, context files
python skills/beam/beam/beam-master/scripts/create_task.py \
--agent-id AGENT_ID \
--query "Task description" \
--json
Follow-up: Offer to monitor task progress
python skills/beam/beam/beam-master/scripts/get_task_updates.py --task-id TASK_ID
Trigger: "analytics", "agent performance", "how is X performing"
python skills/beam/beam/beam-master/scripts/get_analytics.py \
--agent-id AGENT_ID \
--json
Display:
Analytics for Customer Support Agent (Last 30 days)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Tasks: 150 total (+15.5%)
├─ Completed: 135 (+12.3%)
└─ Failed: 15 (-5.2%)
Performance:
├─ Avg Eval Score: 87.5 (+4.5%)
├─ Avg Runtime: 45.7s (-8.7%)
└─ Positive Feedback: 120
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Trigger: "task status", "retry task", "approve task"
Get Task Details:
python skills/beam/beam/beam-master/scripts/get_task.py --task-id TASK_ID --json
Retry Failed Task:
python skills/beam/beam/beam-master/scripts/retry_task.py --task-id TASK_ID
Approve HITL Task:
python skills/beam/beam/beam-master/scripts/approve_task.py --task-id TASK_ID
Provide User Input:
python skills/beam/beam/beam-master/scripts/provide_user_input.py \
--task-id TASK_ID \
--input "User response"
Rate Task Output:
python skills/beam/beam/beam-master/scripts/rate_task_output.py \
--task-id TASK_ID \
--node-id NODE_ID \
--rating positive \
--feedback "Worked well"
Trigger: "test node", "update node config"
Test Node:
python skills/beam/beam/beam-master/scripts/test_graph_node.py \
--agent-id AGENT \
--node-id NODE \
--graph-id GRAPH \
--input '{"key": "value"}'
Update Node:
python skills/beam/beam/beam-master/scripts/update_graph_node.py \
--node-id NODE \
--objective "New objective"
Trigger: "optimize tool", "improve tool performance"
Start Optimization:
python skills/beam/beam/beam-master/scripts/optimize_tool.py --tool TOOL_NAME
Check Status:
python skills/beam/beam/beam-master/scripts/get_optimization_status.py --thread-id THREAD
Trigger: "debug task", "why did task fail", "langfuse trace", "investigate failure"
Hand off to beam-debug-issue-tasks skill for deep debugging via Langfuse traces.
What it does:
Trigger: "feedback automation", "create feedback sheet", "agent feedback", "evaluation sheet"
Hand off to beam-feedback-automation skill for structured feedback collection.
What it does:
Trigger: "agent pricing", "cost estimate", "how much does agent cost", "calculate pricing"
Hand off to calculate-beam-agent-pricing skill for cost estimation.
What it does:
When user mentions:
| Phrase | Route To | |--------|----------| | "list agents", "show agents" | Workflow 1 | | "agent graph", "agent workflow" | Workflow 2 | | "create task", "run task", "execute" | Workflow 3 | | "analytics", "performance", "metrics" | Workflow 4 | | "task status", "retry", "approve" | Workflow 5 | | "test node", "update node" | Workflow 6 | | "optimize tool" | Workflow 7 | | "debug task", "why failed", "langfuse" | Workflow 8 | | "feedback", "evaluation sheet" | Workflow 9 | | "pricing", "cost estimate" | Workflow 10 | | Agent name (from cache) | Show agent details, offer actions |
Common Errors:
| Error | Solution | |-------|----------| | 401 Unauthorized | Token expired - re-authenticate | | 403 Forbidden | Check workspace permissions | | 404 Not Found | Verify agent/task ID | | Rate Limited | Wait and retry |
On Error:
beam-master/references/error-handling.mdAfter listing agents, cache for session:
# Store in conversation context
agents_cache = [
{"name": "Customer Support", "id": "abc-123"},
{"name": "Email Processor", "id": "def-456"}
]
When user says "run Customer Support", match to cached agent ID.
This skill can hand off to specialized skills:
| Skill | When to Use |
|-------|-------------|
| beam-list-agents | Detailed agent listing |
| beam-get-agent-graph | Deep graph analysis |
| beam-get-agent-analytics | Extended analytics |
| beam-create-agent-task | Task creation with monitoring |
| beam-debug-issue-tasks | Debug failed tasks via Langfuse traces |
| beam-feedback-automation | Structured feedback collection via Google Sheets |
| calculate-beam-agent-pricing | Per-task and monthly cost estimation |
| beam-agent-manager | Build-time graph operations (create, modify, optimize agents) |
User: "list my beam agents"
AI:
Let me check your Beam configuration first...
✅ Configuration valid
Found 3 agents in your workspace:
1. Customer Support Agent
ID: abc-123-def
Description: Handles customer inquiries
2. Email Processor
ID: ghi-456-jkl
Description: Processes incoming emails
3. Report Generator
ID: mno-789-pqr
Description: Creates weekly reports
What would you like to do? Options:
- "get analytics for Customer Support"
- "create task for Email Processor"
- "show graph for Report Generator"
User: "create task for Customer Support: Process the latest support ticket"
AI:
Creating task for Customer Support Agent...
✅ Task Created!
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Task ID: AGE-785
Status: QUEUED
Query: Process the latest support ticket
Would you like me to monitor this task for updates?
Version: 1.0 Created: 2025-12-11 Status: Production Ready
tools
Build a Palantir-shape, PDF-native use-case proposal document for a sophisticated enterprise account: research-grounded use cases (each with description, challenge, impact, value), an operating-graph ontology page, a recommended PoC with a week-by-week plan, and a closing page that asks for one decision. Load when a client asks us to 'propose high-impact use cases', requests a use-case presentation/catalog for a function (finance, HR, ops), or when a technical evaluation team will review candidates to pick a PoC. NOT for single-account cold outreach (use prospect-brief), full process diagnostics (use operating-diagnostic), or priced proposals (use proposal-creation).
development
Convert Beam Figma slide designs into high-fidelity, editable HTML presentation decks. Use when Codex is asked to audit Figma slides, extract slide templates, rebuild Beam slides as HTML decks, decide whether Figma imagery should be exported or rebuilt in HTML/CSS, create Beam/Prism-compatible deck templates, or improve fidelity of existing Beam HTML slide rebuilds.
development
Use the Beam AI reusable slide library: individual HTML slide templates extracted from Beam Figma rebuilds, kept separate from deck themes and full deck templates. Load when the user asks for a slide library, specific Beam slide patterns, reusable Figma-inspired slides, Prism slide-library items, or slide-level HTML templates.
development
Use Beam AI deck and report design packs, HTML templates, and curated examples to create sales decks, customer intro decks, RPO decks, and DIN A4 use-case proposal reports. Load when the user asks for Beam-branded presentation templates, Prism-compatible deck templates, Beam report templates, customer intro decks, commercial proposals, or reusable HTML deck/report examples.