permissions-brokerInteract with the Permissions Broker service to fetch data from Google APIs behind a Telegram approval gate. Use when an agent needs to read Google Drive/Doc...
Install via ClawdBot CLI:
clawdbot install stephancill/permissions-brokerGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://permissions-broker.steer.funUses known external API (expected, informational)
api.github.comAudited Apr 17, 2026 · audit v1.0
Generated Mar 21, 2026
AI assistants can use this skill to access user data from Google Drive or GitHub without storing credentials locally, ensuring privacy. The user approves each request via Telegram, making it ideal for tasks like retrieving documents or code repositories. This is useful for automating personal workflows while maintaining security.
Teams can integrate iCloud CALDAV calendars through the broker to schedule meetings or sync events without sharing login details. The skill handles approval-gated requests, allowing managers to coordinate across time zones securely. This reduces manual entry and enhances collaboration in distributed work environments.
Developers can build apps that interact with Spotify via the broker to fetch playlists or control playback with user consent. Each API call requires approval, preventing unauthorized access to streaming accounts. This enables personalized music experiences in fitness or social apps.
Software teams can use the broker to test integrations with providers like GitHub without hardcoding tokens in CI/CD pipelines. Requests are approved on-demand via Telegram, streamlining development while keeping credentials safe. This is practical for agile environments needing frequent API interactions.
Health apps can leverage the broker to pull data from user-linked providers like Google Fit, with each request requiring explicit approval. This ensures compliance with privacy regulations while enabling personalized health insights. It's suitable for telemedicine or wellness platforms.
Offer the broker as a SaaS platform where businesses pay monthly for secure, approval-gated access to multiple providers. Revenue comes from tiered plans based on request volume and supported integrations. This model targets companies needing compliant data handling without infrastructure overhead.
Provide a free tier for individual developers to integrate the broker into personal projects, with paid upgrades for higher limits and premium features like advanced analytics. Monetize through enterprise licenses and support services. This attracts a broad user base while scaling with demand.
License the broker technology to large organizations for internal use, customizing it to fit their security policies and provider ecosystems. Charge upfront implementation fees and ongoing maintenance contracts. This model serves industries like finance or government with strict data governance needs.
💬 Integration Tip
Always include a clear consent_hint in requests to explain the purpose to users, and poll for approvals within 30 seconds to minimize delays in responses.
Scored Apr 19, 2026
Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.
Registra contrato de locação via Google Forms.
Google Sheets integration. Manage analytics data, records, and workflows. Use when the user wants to interact with Google Sheets data.
Google Drive integration. Manage Drives, Users, Permissions. Use when the user wants to interact with Google Drive data.
Gmail, Calendar, Drive, Docs, Sheets — NO Google Cloud Console required. Just OAuth sign-in. Zero setup complexity vs traditional Google API integrations.
Google Slides API integration with managed OAuth. Create presentations, add slides, insert content, and manage slide formatting. Use this skill when users want to interact with Google Slides. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Google Slides connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Google Slides action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Google Slides examples; they add no Google Slides capability - Google Slides is not an event source, a trigger cannot read Google Slides data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).