Trust Assessment
ably-automation received a trust score of 90/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 2 findings: 0 critical, 0 high, 1 medium, and 1 low severity. Key findings include Potential for Excessive Permissions via Generic Tool Execution, Unpinned Managed Component Provider (MCP) Dependency.
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 Findings2
| Severity | Finding | Layer | Location | |
|---|---|---|---|---|
| MEDIUM | Potential for Excessive Permissions via Generic Tool Execution The skill instructs the LLM to use generic Rube MCP tools like `RUBE_MULTI_EXECUTE_TOOL` and `RUBE_REMOTE_WORKBENCH` (with `run_composio_tool()`). While the stated purpose is 'Ably automation', these tools allow for the execution of any tool discovered via `RUBE_SEARCH_TOOLS`. If the Rube MCP exposes tools with broad permissions (e.g., filesystem access, network access beyond Ably, arbitrary code execution), this skill effectively grants the LLM the ability to use those broad permissions, potentially exceeding the principle of least privilege for its stated function. The dynamic discovery mechanism (`RUBE_SEARCH_TOOLS`) further increases this risk, as the LLM might be instructed to use tools not explicitly intended for Ably operations. Implement stricter access controls within the Rube MCP to limit the scope of tools available to this specific skill, or ensure that the LLM's execution environment is sandboxed to prevent abuse of powerful tools. Consider using a more specific tool execution mechanism if available, rather than a generic multi-tool executor, or explicitly whitelist allowed tool slugs. | Static | SKILL.md:49 | |
| LOW | Unpinned Managed Component Provider (MCP) Dependency The skill's manifest declares a dependency on the 'rube' Managed Component Provider (MCP) without specifying a version (`'mcp': ['rube']`). This lack of version pinning means that if a new, potentially malicious or incompatible version of the 'rube' MCP is introduced, the skill's behavior could change unexpectedly or maliciously without explicit developer review. This introduces a supply chain risk for the MCP itself. Specify a precise version or version range for the 'rube' MCP dependency in the manifest to ensure deterministic behavior and mitigate risks from unvetted updates. For example, `"mcp": ["rube@1.2.3"]` or `"mcp": ["rube@^1.0.0"]`. | Static | SKILL.md:1 |
Scan History
Embed Code
[](https://skillshield.io/report/0a9b553ff6d33f84)
Powered by SkillShield