skills.rest
outfitter-dev
outfitter-devOFFICIAL
Explore all skills by this author →
Website𝕏@outfitter_devGitHub

trails-error-format

Classify Trails errors into runtime failures and host-boundary throws across CLI, MCP, and HTTP.

4|1|Updated Mar 28, 2026
Search Tags:#error#governance#taxonomy#retry#redaction#surface#trails
One-click install
npx skills add https://github.com/outfitter-dev/trails --skill trails-error-format
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trails-error-format
Source: https://github.com/outfitter-dev/trails/tree/main/plugin/skills/trails-error-format
Command: npx skills add https://github.com/outfitter-dev/trails --skill trails-error-format

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Trails projects complex error handling needs: distinguishing runtime failures from host-boundary throws, aligning surface projections, and ensuring redaction and retry behavior are consistent across CLI, MCP, HTTP.

Core Features & Use Cases

  • Classify and map Trails errors to appropriate surface representations (CLI, MCP, HTTP).
  • Provide guidance on redaction, retryability, and boundary governance.
  • Use for auditing and improving error taxonomy when adding or changing error classes.

Quick Start

Review changes to classify error semantics across surfaces and update mappings accordingly.

Frequently Asked Questions about trails-error-format

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

FAQPage Schema
How do I classify runtime failures versus host-boundary throws in an error taxonomy?▼

Error taxonomy classification separates runtime failures from host-boundary throws by mapping specific error scenarios to a TrailsError subclass, ensuring consistent projection and redaction across CLI, MCP, and HTTP surfaces.

How do I ensure consistent error redaction and retry guidance across CLI, MCP, and HTTP surfaces?▼

Error redaction and retry guidance are applied consistently across surfaces by classifying error scenarios and documenting the selected TrailsError subclass mapping to align projection behavior for CLI, MCP, and HTTP clients.

What is Trails error taxonomy and when do I need to update subclass mappings?▼

Trails error taxonomy defines how complex error handling is projected across different surfaces, requiring subclass mapping updates when you add or change error classes to maintain accurate boundary governance and retryability.

What's the best way to audit error taxonomy when adding new error classes?▼

Auditing error taxonomy involves reviewing changes to classify error semantics across surfaces and updating the TrailsError subclass mappings accordingly to ensure proper projection sources and test coverage requirements are met.

Does boundary governance require separate error projections for CLI, MCP, and HTTP clients?▼

Boundary governance requires distinct error projections for CLI, MCP, and HTTP surfaces to separate runtime failures from host-boundary throws, ensuring each surface receives appropriate redaction and retry guidance.

What test coverage requirements apply to Trails error subclass mapping?▼

Test coverage requirements for Trails error subclass mapping mandate validating that runtime failures and host-boundary throws project correctly across CLI, MCP, and HTTP surfaces with proper redaction and retry behavior.

Related Skills

Explore More Software Engineering Skills→
RayzerrekRayzerrek

unity-project-scout

Inspect Unity project version, packages, asmdef layout, and folder structure.

Community
Intermediate
dianlightdianlight
8

test-remote-environment

Test SRAT against a live Home Assistant environment with Playwright.

Community
Advanced
ArtisanCloudArtisanCloud
357

crud-http-ruleset

Validate PowerX HTTP handlers for CRUD, tenant, and DTO conventions.

Official
Advanced
atholaathola
326

error-patterns

Define error classification, recovery strategies, and logging patterns for plugin development.

Community
Basic