Security Audit
piloterr-automation
github.com/ComposioHQ/awesome-claude-skillsTrust Assessment
piloterr-automation received a trust score of 90/100, placing it in the Trusted category. This skill has passed all critical security checks and demonstrates strong security practices.
SkillShield's automated analysis identified 2 findings: 0 critical, 0 high, 1 medium, and 1 low severity. Key findings include Unpinned dependency in manifest, Reliance on broad-scope external tool.
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 | |
|---|---|---|---|---|
| MEDIUM | Unpinned dependency in manifest The `requires` field in the skill's manifest specifies the `rube` dependency without a version constraint. This means the skill will always fetch the latest version of `rube`. This practice can lead to unexpected behavior due to breaking changes, or introduce vulnerabilities if a malicious update to the `rube` package is published without explicit review. Pin the `rube` dependency to a specific version or a version range (e.g., `"rube": ["~1.0.0"]`) to ensure stability and mitigate supply chain risks from unexpected or malicious updates. | Static | SKILL.md:1 | |
| LOW | Reliance on broad-scope external tool The skill relies entirely on Rube MCP to access Piloterr operations. While the skill itself does not define permissions, it enables the LLM to interact with the Rube MCP system, which in turn orchestrates access to the Piloterr toolkit. The scope of permissions granted to the underlying Piloterr toolkit, once connected via `RUBE_MANAGE_CONNECTIONS`, is not explicitly defined or constrained within this skill's manifest or documentation. If the connected Piloterr account has broad permissions (e.g., full access to all user data or critical actions), the LLM, when using this skill, will inherit these potentially excessive permissions. Users should be aware of the full scope of permissions granted to the Piloterr connection through Rube MCP. Document the specific permissions required by the Piloterr toolkit when connected via Rube MCP. If possible, provide mechanisms for users to scope down these permissions during the connection setup process to adhere to the principle of least privilege. | Static | SKILL.md:1 |
Scan History
Embed Code
[](https://skillshield.io/report/40a29166e539c549)
Powered by SkillShield