Security Audit

hystruct-automation

github.com/ComposioHQ/awesome-claude-skills

AI SkillCommit 99e2a2951545

TRUSTED

Scanned about 2 months ago

Critical

Immediate action required

High

Priority fixes suggested

Medium

Best practices review

Low

Acknowledged / Tracked

Trust Assessment

hystruct-automation received a trust score of 89/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, 0 high, 2 medium, and 0 low severity. Key findings include Broad tool access 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

Manifest Analysis

100%

Static Code Analysis

100%

Dependency Graph

100%

LLM Behavioral Safety

86%

Behavioral Risk Signals

Shell Execution

1 finding

Excessive Permissions

1 finding

Security Findings2

Severity	Finding	Layer	Location
MEDIUM	Broad tool access via RUBE_REMOTE_WORKBENCH The skill documentation instructs the LLM to use `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()`. While the skill is named 'Hystruct Automation', `run_composio_tool()` implies the ability to execute arbitrary tools within the broader Composio ecosystem. This could grant the LLM access to functionalities beyond Hystruct, potentially leading to unintended actions or data manipulation if the LLM is prompted to use this broad capability. Clarify or restrict the scope of `RUBE_REMOTE_WORKBENCH` to Hystruct-specific operations if possible. If `run_composio_tool()` can indeed call any Composio tool, explicitly state the broader implications and consider if this skill truly needs such extensive access.	LLM	SKILL.md:60
MEDIUM	Unpinned Rube MCP dependency The skill's manifest declares a dependency on the `rube` MCP (`"mcp": ["rube"]`) without specifying a version. This means the skill will always attempt to use the latest available version of the `rube` MCP. This introduces a supply chain risk, as a malicious or breaking update to the `rube` MCP could be automatically incorporated, potentially leading to security vulnerabilities or unexpected behavior without explicit review. Pin the `rube` MCP dependency to a specific, known-good version in the manifest (e.g., `"mcp": ["rube@1.2.3"]`) to ensure stability and security. Regularly review and update the pinned version.	LLM	SKILL.md

Scan History

Embed Code

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