debug

Troubleshoot Outfitter stack issues with Result handling, MCP, CLI output, exit codes, and logging.

6|1|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/outfitter-dev/outfitter --skill debug-outfitter-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/outfitter-dev/outfitter/tree/main/packages/claude-plugin/skills/debug
Command: npx skills add https://github.com/outfitter-dev/outfitter --skill debug-outfitter-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps troubleshoot and resolve common issues encountered when working with the Outfitter framework, including problems with Result handling, MCP server interactions, CLI output, exit codes, and logging configurations.

Core Features & Use Cases

  • Result Handling: Guides users through diagnosing why a Result might always be an error or why type narrowing fails.
  • MCP Issues: Provides steps to fix tools not appearing in MCP or failing during invocation.
  • CLI Output: Offers solutions for JSON not printing correctly or achieving the desired exit codes.
  • Logging: Addresses issues with redaction, missing context, or incorrect log levels.
  • Use Case: When an Outfitter CLI command unexpectedly exits with a non-zero code, or an MCP tool fails to register, this Skill provides targeted debugging steps.

Quick Start

Use the debug skill to troubleshoot why an MCP tool is not appearing in the server.

Frequently Asked Questions about debug

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

FAQPage Schema
Why does my Outfitter MCP tool fail to register or appear in the server?

MCP registration issues in the Outfitter framework are commonly caused by incorrect server configuration or invocation errors. This Skill provides targeted debugging steps to identify why MCP tools are failing and how to resolve the registration problems.

How do I fix Outfitter CLI output when JSON is not printing correctly or the exit code is wrong?

To fix CLI output and exit code issues in Outfitter, you need to verify the active output mode configuration. This Skill helps diagnose unexpected non-zero exit codes and malformed JSON output by troubleshooting the CLI's output handling logic.

How do I troubleshoot Outfitter Result handling when type narrowing fails or always returns an error?

Troubleshooting Result handling involves verifying that your Outfitter Result types are correctly configured for type narrowing. This Skill guides you through diagnosing why a Result might consistently evaluate to an error state instead of success.

What is the best way to resolve Outfitter logging issues like missing context or incorrect log levels?

Resolving Outfitter logging issues requires checking your logging configurations for redaction rules and level assignments. This Skill addresses problems with missing contextual data and incorrect log levels to ensure proper framework telemetry.

Do I need to understand Outfitter stack components to debug unexpected framework errors?

Yes, debugging Outfitter stack issues requires understanding Result types, MCP server registration, CLI output modes, and logging configurations. This Skill applies this framework knowledge to troubleshoot unexpected errors and wrong output modes.