project-conventions

Name: project-conventions
Availability: InStock
Author: MicroTools-Hub

Enforce consistent command patterns and error handling across Core, MCP, and CLI surfaces.

Updated Apr 22, 2026

Search Tags:#integration #cli #mcp #conventions #parity #excelmcp #core-commands

Ready to run

npx skills add https://github.com/MicroTools-Hub/Excel-V2 --skill project-conventions-microtools-hub

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: project-conventions
Source: https://github.com/MicroTools-Hub/Excel-V2/tree/main/sources/mcp-server-excel-main/mcp-server-excel-main/.squad
Command: npx skills add https://github.com/MicroTools-Hub/Excel-V2 --skill project-conventions-microtools-hub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ExcelMcp's development practices can drift across MCP Server, CLI, and core commands. This skill codifies core conventions to ensure consistent error handling, COM interop discipline, and reliable cross-surface parity.

Core Features & Use Cases

Consistent error handling: Core commands propagate exceptions rather than swallowing them, enabling uniform failure envelopes across MCP and CLI.
Robust COM cleanup: All dynamic COM objects are released in finally blocks to prevent leaks.
Cross-surface parity: Guidelines ensure MCP Server, CLI, and tooling share a coherent contract and behavior.

Quick Start

Adopt these conventions when adding new Core commands, MCP tools, or CLI surface, to ensure parity and maintainability.

Frequently Asked Questions about project-conventions

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

FAQPage Schema

How do I enforce consistent error handling across CLI, MCP, and core commands?▼

To enforce consistent error handling across CLI, MCP, and core commands, you should propagate exceptions in core commands rather than swallowing them. This ensures a uniform failure envelope across all execution surfaces.

What is the best way to prevent COM object leaks during Excel MCP development?▼

The best way to prevent COM object leaks during Excel MCP development is to release all dynamic COM objects within finally blocks. This cleanup discipline ensures robust memory management across core command execution.

How do I maintain cross-surface parity between MCP Server and CLI tooling?▼

Maintaining cross-surface parity between MCP Server and CLI tooling requires codifying shared development conventions. This ensures both surfaces share a coherent contract and behave consistently during command execution.

Why does ExcelMCP development drift across different command surfaces?▼

ExcelMCP development drifts across surfaces because independent implementation of MCP Server, CLI, and core commands lacks unified conventions. Applying standardized checks and examples prevents this drift and restores reliability.

Do I need to apply these conventions when adding new CLI surface or MCP tools?▼

Yes, you need to apply these conventions when adding new CLI surface or MCP tools. Adopting these patterns during development ensures immediate parity, consistent error handling, and long-term maintainability.

What are the limitations of relying on ad-hoc patterns for ExcelMCP core commands?▼

Relying on ad-hoc patterns for ExcelMCP core commands limits cross-surface parity and risks COM interop leaks. Without codified conventions, error handling drifts and failure envelopes become inconsistent across MCP and CLI.