Security Audit
googlemeet-automation
github.com/ComposioHQ/awesome-claude-skillsTrust Assessment
googlemeet-automation received a trust score of 100/100, placing it in the Trusted category. This skill has passed all critical security checks and demonstrates strong security practices.
SkillShield's automated analysis identified 1 finding: 0 critical, 0 high, 0 medium, and 0 low severity. Key findings include Skill requires broad Google Meet and Calendar permissions.
The analysis covered 4 layers: Manifest Analysis, Static Code Analysis, Dependency Graph, LLM Behavioral Safety. All layers scored 70 or above, reflecting consistent security practices.
Last analyzed on February 17, 2026 (commit 99e2a295). SkillShield performs automated 4-layer security analysis on AI skills and MCP servers.
Layer Breakdown
Behavioral Risk Signals
Security Findings1
| Severity | Finding | Layer | Location | |
|---|---|---|---|---|
| INFO | Skill requires broad Google Meet and Calendar permissions The skill's described functionality, which includes creating/managing Google Meet spaces, scheduling/updating calendar events, finding free time slots, and searching contacts, inherently requires broad access to a user's Google Meet and Google Calendar data. While necessary for the skill's operation, users should be aware of the significant OAuth scopes that will likely be requested by the underlying Rube MCP toolkits (googlemeet, googlecalendar, gmail) during the connection process. This is not a vulnerability in the skill definition itself, but a characteristic of its powerful capabilities. Ensure that the underlying Rube MCP toolkits request the minimum necessary OAuth scopes for their functionality. Users should carefully review and understand the permissions requested during the authorization flow before granting access to the Rube MCP. | LLM | SKILL.md:40 |
Scan History
Embed Code
[](https://skillshield.io/report/3ad4769c752969b6)
Powered by SkillShield