Security Audit

cutt-ly-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

cutt-ly-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 Excessive Permissions via Generic Tool Execution.

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	Excessive Permissions via Generic Tool Execution The skill 'cutt-ly-automation' provides a 'Quick Reference' entry for 'Bulk ops' using `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()`. The function name `run_composio_tool()` is generic and not explicitly scoped to Cutt Ly operations within the provided documentation. If this function can execute any Composio tool, it grants the LLM broader permissions than implied by the skill's name and stated purpose (Cutt Ly automation). This could allow the LLM to interact with other services or perform actions outside the intended scope, leading to privilege escalation if a malicious prompt instructs it to use this generic function for unintended purposes. Clarify the scope of `run_composio_tool()` within `RUBE_REMOTE_WORKBENCH` to explicitly state it is limited to Cutt Ly operations. If it is intended to be generic, the skill's name and description should reflect this broader capability, or consider if this generic function should be exposed in a skill specifically for Cutt Ly. Renaming the function to `run_cutt_ly_tool()` if it's indeed Cutt Ly-specific would also improve clarity and reduce risk.	LLM	SKILL.md:63

Scan History

Embed Code

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