Trust Assessment
fomo-automation received a trust score of 78/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 Broad tool execution via RUBE_REMOTE_WORKBENCH, Unpinned Rube 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 | |
|---|---|---|---|---|
| HIGH | Broad tool execution via RUBE_REMOTE_WORKBENCH The skill instructs the LLM to use `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()`. This tool appears to allow the execution of arbitrary Composio tools via the Rube MCP. This grants very broad permissions, potentially allowing access to system resources or other services if the underlying Composio tools are not properly sandboxed or if the Rube MCP is compromised. While this may be intended functionality for an automation skill, it represents a high-privilege operation that could be misused. Review the capabilities and sandboxing of `RUBE_REMOTE_WORKBENCH` and `run_composio_tool()`. Ensure that the Rube MCP enforces strict access controls and that Composio tools executed through it operate with the principle of least privilege. Consider if this level of arbitrary tool execution is truly necessary for the skill's stated purpose or if a more restricted set of operations could be exposed. | Static | SKILL.md:60 | |
| MEDIUM | Unpinned Rube MCP dependency The skill's manifest specifies a dependency on `rube` MCP without a version constraint. This means the skill will use whatever version of Rube MCP is available, which could lead to unexpected behavior or security vulnerabilities if a malicious or incompatible version is introduced. This is a supply chain risk. Pin the `rube` MCP dependency to a specific, known-good version or a version range to ensure stability and security. 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/bb19469483132dd1)
Powered by SkillShield