permissions-broker
What this skill does
The skill is a permissions-broker mechanism that allows external data access and third-party actions using a user-issued API key. It requires user approval via Telegram before executing any requests.
github/leoyeai - Documentation - 2.1k stars
Threat analysis
Skill info
pkg:github/LeoYeAI/openclaw-master-skills@e5199b5?skill=permissions-brokerAssessments (1)
Documentation
Documentation via local-llm-review
SKILL.md
The skill's documentation mentions that the PB_API_KEY should never be committed to the repo, included in code, logs, or error output, and should only be reused across sessions with explicit user consBadge
Add the Anomity scan badge for permissions-broker to your README.
How Anomity governs this at runtime
Scan-time vetting tells you what a skill says it will do. Anomity's Endpoint Sensor sees what agents actually do: it discovers skills alongside every other AI artifact on the endpoint, and runtime governance can allow, deny, or log the tool calls a skill triggers. Policy violations route to your SIEM, Slack, email, or Jira, backed by a queryable 90-day audit trail.
Book a 30-minute demo to see your own skill inventory.
Methodology and disputes
Every skill is assessed by the Anomity Skill Intelligence engine against its public source; findings indicate risk patterns, not confirmed exploitation. Maintainer of permissions-broker? Report an issue or request a rescan.
