API Gateway

- Removed the file skill-card.md. - No other functional or documentation changes in this version.

No visible changes were detected in this release. - Version bumped to 1.0.123, but no file modifications or user-facing changes present. - All usage protocols, examples, and documentation remain unchanged.

No user-facing changes in this version. - No file changes detected between versions 1.0.121 and 1.0.122.

No functional or documentation changes in this release. - Version bump to 1.0.121 with no file or content updates detected.

No user-facing changes in this release; no file or documentation changes detected.

No user-visible changes in this version; documentation and file contents remain unchanged.

- Removed the references/meta-ads/README.md file from the project. - No user-facing changes to core skill behavior or documentation. - Use this version if you no longer need the Meta Ads reference file included in your distribution.

No user-facing changes in this version. - Version bumped to 1.0.117. - No file or documentation changes detected.

- Stricter user consent protocols for non-GET (write, modify, or delete) API calls; require explicit user approval with all request details before proceeding. - Updated instructions: Never infer approval for non-GET requests from the original user request—always prompt for confirmation first. - New connection creation now explicitly requires user approval specifying the service; do not create connections without user direction. - Scope selection guidance tightened: during OAuth, choose only scopes necessary for the current task. - Reminders to immediately remove connections after their use if no longer needed.

- Clarified security and usage protocols: all write operations are now blocked by default and require explicit user confirmation with resource details and intended effect. - Expanded authentication and credential safety instructions, emphasizing key secrecy and minimum-privilege principles. - Added stricter guidance for read/list-first workflow and explicit confirmation before any modification or high-impact operation. - Reordered and updated instructions for connection management and specifying connections. - Improved "Routing" and "Security & Permissions" sections for greater clarity and caution.

- Added explicit instructions to require user confirmation before executing non-read (POST, PUT, PATCH, DELETE) operations, especially those that are destructive, public-facing, financial, or purchase-related. - Clarified that all route invocations must happen only after the user specifies the exact app, account, and task. - Updated Routing section for stronger language around operation safety, explicit confirmation, and context verification. - No functional or CLI/API changes; documentation and security usage guidance improvements only.

- Added CLI usage examples for quick start, connection management, and specifying connections. - Documented CLI installation methods (NPM, Homebrew). - Updated authentication and connection management sections to include CLI and Python usage side-by-side. - Added five new reference files for Google Apps Script, Google Tag Manager, LinkedIn Community Management, YouTube Analytics, and YouTube Reporting. - Clarified the need to specify connections using CLI flags (`--connection`) or headers.

- Updated route usage instructions: Section on base URL and path construction is simplified and clarified. - Emphasized use of app-specific reference and read/list calls before making any changes. - Minor change in the description field, stressing to always consult the app-specific reference before changes. - No functional or interface changes; documentation is now clearer and more concise.

- Clarified skill purpose and usage rules, emphasizing starting with read/list calls and explicit user confirmation for changes. - Updated documentation to specify that API route paths must begin with the connection's app name (e.g., `/google-mail/...`) for correct routing. - Improved authentication and security guidance, including the handling of API keys and scope minimization. - Enhanced change operation requirements: now require confirmation of the exact app, connection, resource, payload, and expected result before any non-read action. - Streamlined language throughout for readability and precision.

Version 1.0.110 – Security and confirmation requirements clarified - Updated the description to explicitly require verification of connection and target resource, plus explicit user confirmation before performing any changes. - Clarified language regarding confirmation for data-modifying operations. - Revised authentication and compatibility notes for clarity. - No functional changes to code examples or API behavior.

- Updated security guidance to emphasize specifically choosing the intended connection before taking actions. - Clarified that the MATON_API_KEY should be read from the environment and never printed or logged. - Improved instructions throughout to reinforce use only for user-identified app, account, and task. - Minor language clarifications in authentication and security sections.

- Clarified security instructions: emphasized to keep MATON_API_KEY secret, never log or print it, and always use the environment for the Authorization header. - Updated recommendation to use Maton-Connection header when multiple connections exist for the same service. - Improved descriptions around connection targeting and account selection based on the user's choice. - No API or functional changes; documentation only.

Version 1.0.107 - Clarified and simplified the skill description, emphasizing required user selection and security. - Updated guidance about API route formatting and use of the app identifier in paths. - Improved security messaging: clearer instructions on API key secrecy and prudent connection management. - Streamlined and clarified examples for authentication and connection management. - Updated the "Supported Services" table headers for greater clarity. - Removed redundant or overly detailed content to make documentation more concise and user-friendly.

- Clarified description to emphasize routing only when the user specifies a service, account, and task. - Refined language in the description for greater precision and clarity on usage. - No functionality or API changes; documentation improvements only.

- Updated the skill description to clarify that API access is provided “when the user names a specific service and task.” - Clarified authentication details: Maton API key only identifies the Maton account (not third-party services). - Tweaked documentation wording for base URL section and read-only route examples for better clarity. - No functional or API changes; documentation improvements only.