skills.rest
drillan
drillanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

mixseek-debug

Enable and inspect MixSeek-Plus debug logging for CLI and Python API workflows.

1|1|Updated Jan 16, 2026
Search Tags:#debugging#logging#python#cli#logfire#mixseek
One-click install
npx skills add https://github.com/drillan/mixseek-plus --skill mixseek-debug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mixseek-debug
Source: https://github.com/drillan/mixseek-plus/tree/main/.claude/skills/mixseek-debug
Command: npx skills add https://github.com/drillan/mixseek-plus --skill mixseek-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

MixSeek-Plus can be hard to troubleshoot when agent behavior, model logs, and tool calls are hidden behind default logging. This Skill gives you a guided way to turn on the right debug signals and confirm they are working.

Core Features & Use Cases

  • Unified verbose mode for MixSeek-Plus agent runs.
  • Fine-grained control for ClaudeCode model logging and Logfire tracing.
  • A shell checker that inspects your current environment and reports which debug features are active.
  • Useful when diagnosing failed tool calls, unexpected agent output, or missing workspace logs.

Quick Start

Ask the AI to enable MixSeek verbose debugging and verify the current debug environment variables in your workspace.

Frequently Asked Questions about mixseek-debug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enable verbose debugging for MixSeek agent execution?▼

To enable MixSeek verbose debugging, you configure environment variables like MIXSEEK_VERBOSE to activate detailed tool traces and member-agent logs for CLI and Python API workflows. This provides a unified verbose mode for agent runs.

What environment variables control MixSeek-Plus debug logging?▼

MixSeek-Plus debug logging is controlled by environment variables including MIXSEEK_VERBOSE, CLAUDECODE_MODEL_LOG_LEVEL, MIXSEEK_LOGFIRE, and MIXSEEK_WORKSPACE. These provide fine-grained control for model logging and Logfire tracing.

How do I check if MixSeek debug features are active in my workspace?▼

You can check active MixSeek debug features by running a shell checker that inspects your current environment. It reports which debug features are currently active in your workspace.

Does MixSeek debugging work with both CLI and Python API workflows?▼

Yes, MixSeek debugging applies to both CLI and Python API workflows. It enables verbose tool traces, member-agent logs, and ClaudeCode model debugging across these execution environments.

Do I need Python 3.13 to use MixSeek verbose debugging?▼

Yes, Python 3.13 or higher is required to use MixSeek verbose debugging. You also need mixseek-core or mixseek-plus installed to enable and inspect agent execution logs.

Why are MixSeek tool calls failing and how can I trace them?▼

MixSeek tool calls may fail due to hidden agent behavior or model issues. You can trace them by enabling MixSeek verbose debugging to inspect detailed tool traces, member-agent logs, and ClaudeCode model debugging output.

Related Skills

Explore More Software Engineering Skills→
drillandrillan
1

mixseek-skills

Initialize MixSeek workspaces, generate TOML configurations, and validate against schema rules.

Community
Intermediate
wsxwj123wsxwj123
7

langsmith-fetch

Fetch LangSmith traces to diagnose agent errors and tool calls.

Community
Advanced
drillandrillan
1

mixseek-team-config

Generate MixSeek team.toml configuration files for leader and member agents.

Community
Advanced
andershi666andershi666
1

agent-tracing

Records and inspects agent execution snapshots, including messages, context, and tool calls, via CLI.

Community
Intermediate