error-transport-context
Preserve service request context across MCP and CLI error envelopes.
51
40%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.squad/skills/error-transport-context/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is overly abstract and jargon-heavy, failing to communicate concrete actions or when the skill should be selected. It lacks a 'Use when...' clause and does not include natural trigger terms a user would employ. The niche domain (MCP/CLI error envelopes) provides slight distinctiveness but is insufficient to compensate for the other weaknesses.
Suggestions
Add a 'Use when...' clause specifying explicit triggers, e.g., 'Use when encountering MCP tool call errors, CLI command failures, or when error context is lost across service boundaries.'
Replace abstract language with concrete actions, e.g., 'Wraps and unwraps error responses from MCP tool calls and CLI commands, preserving original request metadata, error codes, and stack traces.'
Include natural user-facing keywords such as 'error handling', 'tool call failure', 'retry context', 'debug errors', or 'error propagation' that users would actually mention.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses abstract language like 'preserve service request context' and 'error envelopes' without listing any concrete actions. It does not specify what the skill actually does in practical terms. | 1 / 3 |
Completeness | The description vaguely addresses 'what' (preserve context across error envelopes) but provides no 'when' clause or explicit trigger guidance. Both dimensions are weak. | 1 / 3 |
Trigger Term Quality | The terms 'MCP', 'CLI error envelopes', and 'service request context' are highly technical jargon that users would not naturally say. There are no common user-facing trigger terms included. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'MCP and CLI error envelopes' is somewhat niche and narrows the domain, but the vague phrasing 'preserve service request context' could overlap with other error-handling or context-management skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a concise, well-structured skill that clearly communicates architectural constraints for cross-cutting diagnostics. Its main weakness is the lack of concrete code examples showing the actual implementation pattern (e.g., what the request-context helper looks like, what the serialized error JSON should contain). Adding even brief code snippets would significantly improve actionability.
Suggestions
Add a short executable code snippet showing how to stamp `command` and `sessionId` on `ServiceResponse` in `ProcessAsync()`, so the pattern is copy-paste ready rather than requiring file exploration.
Include a brief expected output example showing the serialized error JSON shape with the new fields alongside existing compatibility fields.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line carries meaningful, non-obvious guidance specific to this codebase's architecture. No padding or explanation of concepts Claude would already know. | 3 / 3 |
Actionability | Provides specific file paths and method names, and clear architectural patterns, but lacks executable code snippets showing exactly how to stamp fields or enrich failures. The examples section points to files rather than showing concrete code. | 2 / 3 |
Workflow Clarity | The patterns and anti-patterns establish clear constraints, but there's no sequenced workflow for implementing changes across the three files, and no validation/verification steps to confirm the changes work correctly across both MCP and CLI. | 2 / 3 |
Progressive Disclosure | For a skill under 50 lines with a focused scope, the content is well-organized into clear sections (Context, Patterns, Examples, Anti-Patterns) with file path references that serve as natural navigation points. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- sbroenne/mcp-server-excel
- Commit
468809e
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.