skills/beam/beam/beam-debug-issue-tasks/SKILL.md
Debug failed/issue tasks from Beam.ai using Langfuse traces. Load when user says "debug issue tasks", "check failed tasks", "why did task fail", "task errors", "debug agent", or needs to investigate task failures.
npx skillsauth add beam-ai-team/beam-next-skills beam-debug-issue-tasksInstall 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.
Debug failed Beam.ai tasks using Langfuse traces.
This skill is read-only for Beam and Langfuse state. Before saving or sharing debug reports, show the workspace, agent ID, task IDs, destination path, and any customer-sensitive fields that will be included. Require explicit user approval in the current turn before exporting reports outside the local workspace. Do not retry tasks, approve HITL work, update prompts, or modify graphs from this skill.
.env file at project root:
# Beam.ai - BID instance
BEAM_API_KEY=<bid-api-key>
BEAM_WORKSPACE_ID=<bid-workspace-id>
# Beam.ai - Prod instance
BEAM_API_KEY_PROD=<prod-api-key>
BEAM_WORKSPACE_ID_PROD=<prod-workspace-id>
# Langfuse (self-hosted)
LANGFUSE_PUBLIC_KEY=<langfuse-public-key>
LANGFUSE_SECRET_KEY=<langfuse-secret-key>
LANGFUSE_HOST=https://tracing.beamstudio.ai
Dependencies: pip install requests python-dotenv
# List issue tasks (default: last 1 day, BID workspace)
python skills/beam/beam/beam-debug-issue-tasks/scripts/debug_issue_tasks.py <agent_id>
# Debug specific task with full trace analysis
python skills/beam/beam/beam-debug-issue-tasks/scripts/debug_issue_tasks.py <agent_id> --task-id <task_id>
# Use prod workspace
python skills/beam/beam/beam-debug-issue-tasks/scripts/debug_issue_tasks.py <agent_id> --workspace prod
| Workspace | API Endpoint | Langfuse Project |
|-----------|--------------|------------------|
| bid (default) | api.bid.beamstudio.ai | cmauxbgww000582ry4644c2qr |
| prod | api.beamstudio.ai | clw5gbhuy0003u3rv4jzzoesh |
Tasks are flagged as "issue" if status is:
FAILED - Execution failedERROR - Processing errorSTOPPED - Condition failedCANCELLED - User cancelledTIMEOUT - Execution timeoutUSER_INPUT_REQUIRED - Missing input dataReports saved to: 04-workspace/agents/{agent_name}/debug/
Format: Smart Brevity (headline, takeaway, why it matters, details, fix)
Key spans analyzed:
ParameterSelection/v2 - How parameters were matchedExecuteGPT_Tool/v1 - Tool execution reasoningNodeSelection:EdgeEvaluation/v1 - Routing decisionsTaskSuccessCriteriaCheck/v1 - Why task stopped| Flag | Description | Default |
|------|-------------|---------|
| agent_id | Beam agent ID (required) | - |
| --workspace, -w | Workspace: bid or prod | bid |
| --days, -d | Look back period (1, 3, 7, 14, 30) | 1 |
| --task-id, -t | Debug specific task ID | - |
| --summary, -s | Show grouped summary | false |
| --limit, -l | Max tasks to show | 10 |
| --output, -o | Save to JSON file | - |
| --no-trace | Skip Langfuse lookup | false |
# Task stopped: condition failed
Checklist evaluation: subfolder must equal 'Schreiben Schuldner' but was null.
**Why it matters**: This task did not complete successfully and may need attention.
**The details**:
- **Status**: `STOPPED`
- **Task**: `ab3cbbb8-28da-41aa-b726-25931d14d7d4`
- **Latency**: 159.6s
- **Cost**: $0.1043
**Key spans**:
- NodeSelection:EdgeEvaluation/v1 (23.4s)
- TaskSuccessCriteriaCheck/v1 (7.2s)
**Root cause**:
> The criterion is not met because subfolder is not set to required value.
**Fix**: Review the condition that stopped execution. Check if input data meets requirements.
Each report includes direct links:
| Error | Solution |
|-------|----------|
| BEAM_API_KEY not found | Add to .env |
| Invalid workspace | Check workspace parameter (bid/prod) |
| No traces found | Verify agent has Langfuse integration |
| 401 Unauthorized | Verify API keys |
beam-get-agent-analytics - Performance metricsbeam-create-agent-task - Create test tasksbeam-list-agents - List available agentstools
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.