ClawKit Logo
ClawKitReliability Toolkit
Back to Registry
Official Verified utilities Safety 4/5

Permissions Broker

Skill by stephancill

Why use this skill?

Use the Permissions Broker skill to securely authorize your OpenClaw agent to access Google, GitHub, and iCloud services with human-in-the-loop Telegram approval.

skill-install — Terminal

Install via CLI (Recommended)

clawhub install openclaw/skills/skills/stephancill/permissions-broker
Or

What This Skill Does

The Permissions Broker skill acts as a secure, human-in-the-loop bridge between your OpenClaw agent and your private third-party services. Rather than granting the agent broad, persistent access to your personal accounts, this skill utilizes a user-issued API key to initiate gated requests. Every external interaction—such as accessing Google Drive files, fetching GitHub repository data, or checking your iCloud calendars—must be explicitly authorized by you via a Telegram notification. This ensures you maintain full sovereignty over your data at all times, providing a layer of granular verification for every sensitive operation the agent attempts to perform.

Installation

To integrate the Permissions Broker into your agent, run the following command in your OpenClaw environment:

clawhub install openclaw/skills/skills/stephancill/permissions-broker

Ensure you have your Telegram bot configured to handle incoming authorization requests, as the broker relies on this interface for the approval-gated workflow.

Use Cases

  • Cloud Storage Integration: Securely list or retrieve files from Google Drive without sharing account credentials directly with the agent.
  • Version Control Management: Safely fetch issues, PR details, or repository metadata from GitHub while keeping your OAuth tokens or personal access tokens behind the broker's proxy.
  • Calendar Coordination: Check availability or import events from iCloud calendars for scheduling tasks, using the broker to securely handle CALDAV authentication flows.
  • Third-Party API Execution: Automate tasks that require authentication by proposing specific API requests to the broker that the user can approve on-the-fly.

Example Prompts

  1. "Permissions Broker, can you please fetch the latest pull requests from the openclaw/core repository on GitHub?"
  2. "Use the Permissions Broker to check my iCloud calendar for any conflicts on Tuesday between 2 PM and 4 PM."
  3. "I need to summarize the document titled 'Q3 Strategy' located in my Google Drive; please request the necessary access."

Tips & Limitations

  • Security First: Never share your PB_API_KEY in plain text within chat logs or code repositories. Store it only in your secure environment variable file.
  • Approval Workflow: The agent will poll for your approval in Telegram. If you do not see a notification, ensure your Telegram bot is online and properly linked.
  • Session Persistence: You may choose to persist your API key, but for higher security, opt for session-based usage where the agent forgets the key once the session ends.
  • Provider Support: If a specific service isn't supported, remember that the broker is designed for extensibility; check the source repository for updates on supported providers.

Metadata

Stars982
Views1
Updated2026-02-14
View Author Profile
AI Skill Finder

Not sure this is the right skill?

Describe what you want to build — we'll match you to the best skill from 16,000+ options.

Find the right skill
Add to Configuration

Paste this into your clawhub.json to enable this plugin.

{
  "plugins": {
    "official-stephancill-permissions-broker": {
      "enabled": true,
      "auto_update": true
    }
  }
}

Tags(AI)

#security#authentication#api-proxy#automation#privacy
Safety Score: 4/5

Flags: external-api