liatrio-labs/mastra-api
skills/mastra-api/SKILL.md
Interact with Mastra development server API for debugging agents, viewing conversation threads, listing/inspecting tools and workflows, accessing observability data, and managing Mastra resources. Use when working with Mastra agents and need to inspect runtime state, debug agent errors, view thread history, see available tools/workflows, or access API endpoints at localhost:4111/api or similar ports.
$ install --global
skillsauthnpx skillsauth add liatrio-labs/ai-prompts mastra-apiInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 6, 2026, 9:55 PM80.8s9 files scanned
SKILL.md
- name:
- mastra-api
- description:
- Interact with Mastra development server API for debugging agents, viewing conversation threads, listing/inspecting tools and workflows, accessing observability data, and managing Mastra resources. Use when working with Mastra agents and need to inspect runtime state, debug agent errors, view thread history, see available tools/workflows, or access API endpoints at localhost:4111/api or similar ports.
Mastra Development API
Interact with the Mastra dev server API to debug agents, view conversations, inspect tools and workflows, and access observability data.
Quick Start
Agent Debugging
Run these scripts/... commands from the skills/mastra-api/ directory. From repo root, prefix them with skills/mastra-api/.
# Get latest conversation
scripts/get_latest_thread.sh <agent-id> [port]
# Debug errors
scripts/debug_agent_error.sh <agent-id> [port]
# View thread messages
curl --globoff -sS \
"http://localhost:4111/api/memory/threads/THREAD_ID/messages?page=0&perPage=50&agentId=my-agent&orderBy[field]=createdAt&orderBy[direction]=DESC" \
| jq '.'
Tools and Workflows
Run these scripts/... commands from the skills/mastra-api/ directory. From repo root, prefix them with skills/mastra-api/.
# List all tools
scripts/list_tools.sh [port]
# List all workflows
scripts/list_workflows.sh [port]
# Get workflow details
scripts/get_workflow_details.sh <workflow-name> [port]
# Get workflow runs
scripts/get_workflow_runs.sh <workflow-name> [port]
Resource Listing
# List all agents
curl -sS http://localhost:4111/api/agents | jq 'keys'
# List all tools
curl -sS http://localhost:4111/api/tools | jq 'keys'
# List all workflows
curl -sS http://localhost:4111/api/workflows | jq 'keys'
Common Tasks
Debug Agent Failures
- Get latest thread:
scripts/get_latest_thread.sh my-agent - Check for errors:
scripts/debug_agent_error.sh my-agent - Inspect message content for error details
Inspect Available Resources
# See what tools an agent can use
curl -sS http://localhost:4111/api/agents | \
jq '.["my-agent"].tools | keys'
# See what workflows an agent can invoke
curl -sS http://localhost:4111/api/agents | \
jq '.["my-agent"].workflows | keys'
# List all registered tools
scripts/list_tools.sh
# List all registered workflows
scripts/list_workflows.sh
Debug Workflows
# Get workflow structure and steps
scripts/get_workflow_details.sh my-workflow
# Check workflow execution history
scripts/get_workflow_runs.sh my-workflow
# Find failed workflow runs
scripts/get_workflow_runs.sh my-workflow | \
jq '.runs[] | select(.status == "failed")'
Check Tool/Workflow Schemas
# Get tool input parameters
curl -sS http://localhost:4111/api/tools | \
jq '.YOUR_TOOL_KEY.inputSchema | fromjson.json.properties | keys'
# Get workflow input requirements
curl -sS http://localhost:4111/api/workflows/my-workflow | \
jq '.inputSchema | fromjson.json.properties | keys'
Access Observability Data
# Get traces
curl -sS http://localhost:4111/api/observability/traces | jq '.'
# Get logs
curl -sS http://localhost:4111/api/logs | jq '.'
Important Notes
Use --globoff with curl
Query parameters with brackets must use --globoff:
curl --globoff -sS "...&orderBy[field]=updatedAt&orderBy[direction]=DESC"
Without --globoff, curl treats [...] as character ranges.
API Base URLs
Standard: http://localhost:4111/api
Swagger Documentation
Complete interactive API docs: http://localhost:4111/swagger-ui
Debugging Workflow
When UI doesn't show errors clearly:
- Get latest thread -
scripts/get_latest_thread.sh <agent-id> - Extract thread ID from response
- Get messages - Use thread ID to fetch conversation
- Look for errors - Search for
"error"or"failed"fields - Review content - Inspect message content for details
This is the fastest way to debug agent issues.
Reference
See references/api_endpoints.md for:
- Complete endpoint reference
- Query parameter details
- Pagination and ordering
- Project-specific configurations
- Error handling patterns
See references/tools_and_workflows.md for:
- Tools API documentation
- Workflows API documentation
- Schema parsing examples
- Integration with agents
- Common debugging patterns
Scripts
Agent Debugging
scripts/get_latest_thread.sh <agent-id> [port] [detailed]- Get latest conversation threadscripts/debug_agent_error.sh <agent-id> [port]- Quick error debugging
Tools & Workflows
scripts/list_tools.sh [port]- List all registered tools with descriptionsscripts/list_workflows.sh [port]- List all registered workflows with stepsscripts/get_workflow_details.sh <workflow-name> [port]- Get detailed workflow informationscripts/get_workflow_runs.sh <workflow-name> [port] [page] [perPage]- Get workflow execution history
Related Skills
liatrio-labs/plan-epic
testing
VerifiedTrustedCommunity
Interactive GitHub Epic planner. Plans one milestone at a time. The first epic is always Shell (scaffold + CI with a fixed set of stories). Each subsequent epic is defined through operator dialogue. Use /plan-issue to create the individual stories once an epic is defined.
2SKILL.mdUpdated Jun 12, 2026
liatrio-labs/browser-qa
development
VerifiedTrustedCommunity
Use when you need lightweight browser QA for a web page, local HTML file, or app: inspect console errors, broken assets, keyboard/focus behavior, viewport readability, and publish evidence-backed findings JSON through a local HTML report viewer.
2SKILL.mdUpdated May 29, 2026
liatrio-labs/liatrio-dns
data-ai
VerifiedTrustedCommunity
Provision DNS records for liatr.io subdomains in the liatrio/liatrio-external-dns repository. Use when adding, modifying, or removing DNS CNAME records, A records, or other Route53 records for liatr.io or k8s-ignite.com domains. Triggers on requests like 'add a domain', 'create a subdomain', 'point X.liatr.io to Y', or 'set up DNS for a new site'.
2SKILL.mdUpdated May 8, 2026
liatrio-labs/uv-usage
development
VerifiedTrustedCommunity
Provides concise guidance for using uv (Python package manager), including project workflows, pip-compatible commands, Python version management, and PEP 723 inline script dependencies. Use when users mention uv, uv run, inline dependencies, PEP 723, or Python dependency/project management.
2SKILL.mdUpdated Apr 6, 2026