cc-tooling

Standardize MCP server inventories, Mermaid diagram rendering, and .claude configuration.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/leonardoacosta/central-claude --skill cc-tooling
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cc-tooling
Source: https://github.com/leonardoacosta/central-claude/tree/main/skills/cc-tooling
Command: npx skills add https://github.com/leonardoacosta/central-claude --skill cc-tooling

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a consistent set of tooling standards and operational guidance to manage MCP servers, reliably render Mermaid diagrams, map agents to skills, and maintain shared project configuration so teams avoid ad-hoc integrations, token leaks, and fragile diagram rendering workflows.

Core Features & Use Cases

  • MCP Inventory & Selection: Criteria and process to evaluate, test, secure, and document MCP servers before adding them to the inventory.
  • Mermaid Rendering Guidance: Authoritative guidance to render .mmd files locally using mmdc, manage Puppeteer executable paths, and avoid fragile Live URL approaches.
  • Skill Integration Patterns: Agent-to-skill mapping patterns, discovery recommendations, and maintenance guidance for skill references and search indexes.
  • Shared Config Architecture & RTK: Conventions for ~/.claude/shared layouts, project and machine-local overrides, and token-optimizing CLI proxy (RTK) usage and verification.

Quick Start

Use the cc-tooling skill to evaluate and add a new MCP server against the selection criteria, render a Mermaid diagram locally with mmdc, or update shared .claude configuration using the documented conventions.

Frequently Asked Questions about cc-tooling

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

FAQPage Schema
How do I render Mermaid diagrams locally with mmdc without errors?

To render Mermaid diagrams locally with mmdc, you must manage the Puppeteer executable path to ensure reliable rendering. This approach avoids fragile Live URL workflows and enforces local rendering constraints for consistent diagram generation.

What criteria should I use to evaluate and select MCP servers?

Evaluating MCP servers requires checking selection, security, and performance constraints before adding them to your inventory. You should test and document servers to prevent token leaks and avoid ad-hoc integrations across your project environment.

How do I manage shared .claude configuration and machine-local overrides?

Managing shared .claude configuration involves using documented conventions for ~/.claude/shared layouts alongside project and machine-local overrides. This structure standardizes configuration and supports token-optimizing CLI proxy usage for verification.

Why should I use Docker when configuring MCP servers for write access?

Docker is recommended for MCP servers requiring write access to satisfy security constraints and isolate operations. Using Docker prevents unauthorized file modifications and protects your environment while maintaining necessary server functionality.

Where should I store secrets when setting up MCP servers?

Secrets must be stored in environment files when configuring MCP servers to satisfy security constraints. This standard prevents token leaks and ensures sensitive data is managed safely outside of shared project configuration files.

Can I map agents to skills using standardized integration patterns?

Mapping agents to skills uses standardized integration patterns that provide discovery recommendations and maintenance guidance. This process maintains skill references and search indexes to avoid fragile, ad-hoc skill integrations within your workflow.