resolve-conventions

Document and enforce development conventions for resolve-mcp tool modules.

3|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/jenkinsm13/resolve-mcp --skill resolve-conventions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resolve-conventions
Source: https://github.com/jenkinsm13/resolve-mcp/tree/main/.claude/skills/resolve-conventions
Command: npx skills add https://github.com/jenkinsm13/resolve-mcp --skill resolve-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a standardized set of conventions and patterns for developing tools within the resolve-mcp project, ensuring consistency and maintainability.

Core Features & Use Cases

  • Tool Module Pattern: Defines a consistent structure for creating new Resolve tools.
  • Naming Conventions: Establishes clear naming rules for functions and modules.
  • Import Guidelines: Promotes the use of relative imports for better module organization.
  • Error Handling: Outlines best practices for error management within tools.
  • Use Case: When adding a new feature to resolve-mcp, developers can consult this Skill to understand the expected code structure, naming, and error handling, leading to faster integration and fewer style-related issues.

Quick Start

Follow the tool module pattern outlined in this skill for all new tool development.

Frequently Asked Questions about resolve-conventions

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

FAQPage Schema
What are development conventions for Python tool modules?

Development conventions for Python tool modules define a consistent structure for creating tools, including specific naming rules, relative import strategies, and error handling patterns to ensure code maintainability.

How do I structure a new tool module in resolve-mcp?

To structure a new tool module in resolve-mcp, follow the defined tool module pattern which specifies function and module naming conventions, relative import guidelines, and standard error handling practices for consistent integration.

Why use relative imports for Python development patterns?

Relative imports are used in Python development patterns to promote better module organization within the project, ensuring that tool modules maintain a standardized and predictable structure across the codebase.

What is the best way to handle errors in Python tool modules?

The best way to handle errors in Python tool modules is to follow the outlined best practices for error management, which ensure consistent behavior and maintainability across the project's toolset during feature integration.

Do I need specific coding standards for Gemini AI tool integration?

Yes, integrating Gemini AI tools requires adhering to specific coding standards and guidelines outlined for the resolve-mcp project, ensuring new modules follow expected naming conventions, import strategies, and structural patterns.