Maestro Native Integrations

What problem does it solve?

This Skill provides an opinionated, policy-driven guide for connecting third-party business systems to the Maestro operator without unsafe credential handling or uncontrolled tool usage.

Core Features & Use Cases

• Native vs MCP Preference: Chooses Hermes-native skills over MCP when a native option exists and is sufficient, with clear escalation rules when MCP is safer or required.
• Specialist Profile & Handoff Guidance: Documents Slack-facing workflow control handoffs and prescribes how to use internal workers (profiles) and bounded terminal commands for reliability.
• Credential and Permission Policy: Establishes presence-only credential checks, required credential lists per provider, and guidance to minimize scopes and avoid secret leakage.
• Provider-Specific Operational Constraints: Defines GitHub read/write boundaries, Linear mutation constraints, Mobbin design research usage, Stitch generation as design-only, and Google Workspace mutation approvals.
• Setup and Integration URLs: Consolidates onboarding links for each integration type to reduce friction during configuration.

Quick Start

Use this Skill when selecting the correct Hermes-native integration (or deciding to fall back to MCP) and when you need provider-specific credential, permission, and approval rules for a Maestro operator workflow.