Security Audit

amcards-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

amcards-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, 1 high, 0 medium, and 0 low severity. Key findings include Potential Arbitrary Code 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

Manifest Analysis

100%

Static Code Analysis

100%

Dependency Graph

100%

LLM Behavioral Safety

85%

Behavioral Risk Signals

Shell Execution

1 finding

Dynamic Code

1 finding

Excessive Permissions

1 finding

Security Findings1

Severity	Finding	Layer	Location
HIGH	Potential Arbitrary Code Execution via RUBE_REMOTE_WORKBENCH The skill documentation mentions `RUBE_REMOTE_WORKBENCH` for 'Bulk ops' using `run_composio_tool()`. The term 'workbench' and 'bulk ops' often imply a more privileged or less constrained execution environment. If `run_composio_tool()` within this context allows execution of arbitrary code, shell commands, or access to system resources beyond the intended Amcards API, it poses a significant command injection and excessive permissions risk. The exact scope and sandboxing of `RUBE_REMOTE_WORKBENCH` are not clearly defined in the documentation, making it a potential vector for malicious operations. Clarify the exact capabilities and security boundaries of `RUBE_REMOTE_WORKBENCH` and `run_composio_tool()`. Ensure it is strictly sandboxed and only permits operations within the defined scope of Amcards, without allowing arbitrary code execution, filesystem access, or other privileged system interactions. If arbitrary code execution is an intended feature, it must be explicitly documented with severe warnings and strong sandboxing guarantees.	LLM	SKILL.md:80

Scan History

Embed Code

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