Security Audit

ninox-automation

github.com/ComposioHQ/awesome-claude-skills

AI SkillCommit 27904475d127

TRUSTED

Scanned about 2 months ago

Critical

Immediate action required

High

Priority fixes suggested

Medium

Best practices review

Low

Acknowledged / Tracked

Trust Assessment

ninox-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 1 finding: 0 critical, 0 high, 1 medium, and 0 low severity. Key findings include Broad tool execution capability 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

Manifest Analysis

100%

Static Code Analysis

100%

Dependency Graph

100%

LLM Behavioral Safety

93%

Behavioral Risk Signals

Shell Execution

1 finding

Excessive Permissions

1 finding

Security Findings1

Severity	Finding	Layer	Location
MEDIUM	Broad tool execution capability via RUBE_REMOTE_WORKBENCH The skill documentation for 'ninox-automation' mentions `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` for 'Bulk ops'. While the skill is named for Ninox automation, the generic naming of `run_composio_tool()` suggests it might be capable of executing any Composio tool, not just those explicitly scoped to Ninox. If `run_composio_tool()` can be leveraged to interact with other platforms or functionalities beyond Ninox, this skill could expose an overly broad permission surface. An attacker could potentially prompt the LLM to use this generic function to access or manipulate data on other connected Composio platforms, exceeding the intended scope of Ninox automation. Clarify the scope of `run_composio_tool()` when used within the `ninox-automation` context. If its functionality is strictly limited to Ninox operations, consider renaming it or adding explicit scope checks within the Rube MCP implementation to prevent cross-platform execution. If it is intended to be generic, document the full scope of its capabilities and assess if exposing such a broad tool is appropriate for a skill specifically named 'ninox-automation'.	LLM	SKILL.md:64

Scan History

Embed Code

[![SkillShield](https://skillshield.io/api/v1/badge/640bfa719a732ba5.svg)](https://skillshield.io/report/640bfa719a732ba5)