Security Audit
cloudflare-api-key-automation
github.com/ComposioHQ/awesome-claude-skillsTrust Assessment
cloudflare-api-key-automation received a trust score of 85/100, placing it in the Mostly Trusted category. This skill has passed most security checks with only minor considerations noted.
SkillShield's automated analysis identified 2 findings: 0 critical, 1 high, 1 medium, and 0 low severity. Key findings include Unpinned Rube MCP Dependency, Potential for Arbitrary Tool Execution via RUBE_REMOTE_WORKBENCH.
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 20, 2026 (commit 27904475). SkillShield performs automated 4-layer security analysis on AI skills and MCP servers.
Layer Breakdown
Behavioral Risk Signals
Security Findings2
| Severity | Finding | Layer | Location | |
|---|---|---|---|---|
| HIGH | Potential for Arbitrary Tool Execution via RUBE_REMOTE_WORKBENCH The skill suggests using `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` for 'Bulk ops'. The term 'workbench' and the function `run_composio_tool()` imply the ability to execute arbitrary tools or code within the Composio ecosystem. If `RUBE_REMOTE_WORKBENCH` lacks sufficient sandboxing, input validation, or fine-grained access controls, an attacker could potentially inject malicious commands or execute unintended operations through this interface, leading to excessive permissions or command injection. The skill itself encourages its use without detailing safeguards. Clarify the security model and sandboxing of `RUBE_REMOTE_WORKBENCH`. If it allows arbitrary tool execution, ensure robust input validation and strict permission scoping. Advise users on the potential risks and best practices for using this powerful tool. Consider if this tool should be exposed directly to the LLM without further constraints or if its capabilities should be limited. | LLM | SKILL.md:80 | |
| MEDIUM | Unpinned Rube MCP Dependency The skill explicitly requires the `rube` MCP but does not specify a version. This introduces a supply chain risk where updates to the `rube` MCP could introduce breaking changes, vulnerabilities, or malicious code without explicit review or pinning by the skill author. Without version pinning, the skill's behavior could change unexpectedly or maliciously if the `rube` MCP is updated. Specify a version or a version range for the `rube` MCP dependency in the skill's manifest to ensure stability and security. For example, `{"mcp": ["rube@1.2.3"]}` or `{"mcp": ["rube@^1.0.0"]}`. | LLM | SKILL.md:20 |
Scan History
Embed Code
[](https://skillshield.io/report/6e99edcbcb803c31)
Powered by SkillShield