skills/beam/beam-tools/beam-get-task-details/SKILL.md
Get detailed information about a specific Beam.ai task including status, parameters, node execution, and graph state. Load when user says "get task details", "task info", "show task", "task status", "what happened with task", or needs to inspect a specific task.
npx skillsauth add beam-ai-team/beam-next-skills beam-get-task-detailsInstall 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.
Retrieve detailed information about a specific Beam.ai task.
.env file at project root:
# Beam.ai - BID instance (default)
BEAM_API_KEY=your_bid_api_key
BEAM_WORKSPACE_ID=your_bid_workspace_id
# Beam.ai - Production instance
BEAM_API_KEY_PROD=your_prod_api_key
BEAM_WORKSPACE_ID_PROD=your_prod_workspace_id
Dependencies: pip install requests python-dotenv
# Get task details
python 03-skills/beam-get-task-details/scripts/get_task_details.py <task_id>
# Get task details from production
python 03-skills/beam-get-task-details/scripts/get_task_details.py <task_id> --workspace prod
# Output as JSON
python 03-skills/beam-get-task-details/scripts/get_task_details.py <task_id> --json
# Get multiple tasks
python 03-skills/beam-get-task-details/scripts/get_task_details.py <task_id1> <task_id2> <task_id3>
# Save output to file
python 03-skills/beam-get-task-details/scripts/get_task_details.py <task_id> --output task_details.json
| Workspace | API Endpoint | Default |
|-----------|--------------|---------|
| bid | api.bid.beamstudio.ai | Yes |
| prod | api.beamstudio.ai | No |
| Flag | Description | Default |
|------|-------------|---------|
| task_ids | One or more task IDs (required) | - |
| --workspace, -w | Workspace: bid or prod | bid |
| --json | Output as JSON | false |
| --full | Show full response (all fields) | false |
| --output, -o | Save to file | - |
| Field | Description |
|-------|-------------|
| id | Task ID (UUID) |
| customId | Custom identifier (if provided) |
| status | Task status (COMPLETED, FAILED, IN_PROGRESS, etc.) |
| createdAt | Task creation timestamp |
| updatedAt | Last update timestamp |
| completedAt | Completion timestamp (if completed) |
| Status | Description |
|--------|-------------|
| QUEUED | Task is queued for execution |
| IN_PROGRESS | Task is currently running |
| COMPLETED | Task completed successfully |
| FAILED | Task failed during execution |
| ERROR | Task encountered an error |
| STOPPED | Task was stopped (condition failed) |
| TIMEOUT | Task timed out |
| USER_INPUT_REQUIRED | Task waiting for user input |
| CANCELLED | Task was cancelled |
| Field | Description |
|-------|-------------|
| agentTaskNodes | Array of node execution data |
| agentTaskNodes[].toolData | Node tool configuration and reasoning |
| agentTaskNodes[].userQuestions | Required user inputs |
| Field | Description |
|-------|-------------|
| graphState.current | Current node in execution |
| graphState.variables | Task variables and context |
Task Details
============================================================
Task ID: abc123-def456-789...
Custom ID: INS-12345
Status: COMPLETED
Created: 2024-01-15T10:30:00Z
Updated: 2024-01-15T10:31:45Z
Completed: 2024-01-15T10:31:45Z
=== EXECUTION ===
Duration: 105 seconds
Nodes: 5 executed
=== NODE DETAILS ===
[1] ParameterExtraction
Status: completed
Parameters extracted: company_name, contact_email
[2] DataLookup
Status: completed
Tool: hubspot_search
[3] ProcessData
Status: completed
[4] GenerateOutput
Status: completed
[5] SendNotification
Status: completed
=== RESULT ===
{
"success": true,
"output": "Task completed successfully"
}
Uses Beam.ai task details endpoint:
GET /agent-tasks/{taskId}| Error | Solution |
|-------|----------|
| BEAM_API_KEY not found | Add to .env file |
| 401 Unauthorized | Verify API key is valid |
| 404 Not Found | Task ID doesn't exist |
beam-get-agent-analytics - Get agent performance metricsbeam-debug-issue-tasks - Debug failed tasks with Langfuse tracesbeam-retry-tasks - Retry failed tasksdevelopment
--- 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".