Can it fix my CLI exit codes?

Yes, it provides a standardized exit code table (ranging from validation errors to internal failures) and demonstrates how to use the exitWithError helper to ensure consistent process termination.

Why isn't my JSON output appearing in the CLI?

This skill helps you verify if the OUTFITTER_JSON environment variable is overriding your flags and ensures that your output functions are properly awaited before the process exits.

What is the Outfitter Stack?

The Outfitter Stack is a collection of TypeScript packages and patterns designed for building robust agents, focusing on predictable error handling via the Result type and standardizing CLI/MCP behaviors.

How does this skill help with MCP issues?

It identifies common registration errors, ensures tool handlers are correctly marked as async, and validates that Zod schemas include the descriptions necessary for AI models to understand them.

Outfitter Stack Debugger

Name: Outfitter Stack Debugger
Author: outfitter-dev

byoutfitter-dev

•

Analytics & Monitoring

Troubleshoots Outfitter Stack issues including Result types, MCP protocol problems, CLI output, and logging configurations.

About

The Outfitter Stack Debugger is a specialized skill designed to diagnose and resolve common development hurdles within the Outfitter ecosystem. It provides expert guidance on handling TypeScript Result patterns, debugging Model Context Protocol (MCP) server integrations, and fixing CLI behavior such as incorrect exit codes or JSON output modes. Whether you are dealing with broken type narrowing, missing log context, or async execution errors, this skill offers actionable code snippets and systematic checklists to restore functionality to your Outfitter-based applications.

Key Features

Troubleshoots TypeScript Result type narrowing and async handling errors
Provides standardized exit code mapping for Outfitter-compliant packages
18 GitHub stars
Fixes CLI output formatting and environment-specific JSON overrides
Diagnoses MCP tool registration and Zod schema validation issues
Resolves logging issues including redaction failures and missing context

Use Cases

Tracing complex Result chains to identify where an error originates
Debugging why a CLI command returns the wrong status code on failure
Fixing 'Tool Not Found' errors in custom MCP servers

About

Key Features

Troubleshoots TypeScript Result type narrowing and async handling errors
Provides standardized exit code mapping for Outfitter-compliant packages
18 GitHub stars
Fixes CLI output formatting and environment-specific JSON overrides
Diagnoses MCP tool registration and Zod schema validation issues
Resolves logging issues including redaction failures and missing context

Use Cases

Tracing complex Result chains to identify where an error originates
Debugging why a CLI command returns the wrong status code on failure
Fixing 'Tool Not Found' errors in custom MCP servers