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.
.env file at project root:
# Beam.ai - BID instance
BEAM_API_KEY=your_bid_api_key
BEAM_WORKSPACE_ID=your_bid_workspace_id
# Beam.ai - Prod instance
BEAM_API_KEY_PROD=your_prod_api_key
BEAM_WORKSPACE_ID_PROD=your_prod_workspace_id
# Langfuse (self-hosted)
LANGFUSE_PUBLIC_KEY=pk-lf-...
LANGFUSE_SECRET_KEY=sk-lf-...
LANGFUSE_HOST=https://tracing.beamstudio.ai
Dependencies: pip install requests python-dotenv
# List issue tasks (default: last 1 day, BID workspace)
python 01-skills/beam-debug-issue-tasks/scripts/debug_issue_tasks.py <agent_id>
# Debug specific task with full trace analysis
python 01-skills/beam-debug-issue-tasks/scripts/debug_issue_tasks.py <agent_id> --task-id <task_id>
# Use prod workspace
python 01-skills/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 agentsdevelopment
--- 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".