Trust Assessment
rebalance-position received a trust score of 86/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 Delegation to highly privileged 'liquidity-manager' subagent.
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 13, 2026 (commit 13146e6a). SkillShield performs automated 4-layer security analysis on AI skills and MCP servers.
Layer Breakdown
Behavioral Risk Signals
Security Findings1
| Severity | Finding | Layer | Location | |
|---|---|---|---|---|
| HIGH | Delegation to highly privileged 'liquidity-manager' subagent The skill declares permission to delegate tasks to a 'liquidity-manager' subagent, as specified in the 'allowed-tools' manifest entry. The skill's workflow description in SKILL.md details that this subagent performs critical financial operations including collecting fees, removing 100% liquidity from existing positions, approving tokens, and adding new liquidity. While these actions are necessary for the skill's core function (rebalancing Uniswap positions), the 'liquidity-manager' represents a highly privileged component capable of direct asset manipulation. Any compromise or misuse of this delegation, either through a prompt injection against the LLM or a vulnerability in the subagent itself, could lead to significant financial loss. The skill relies on user confirmation and a 'safety-guardian' for validation, but the inherent power and broad scope of the delegated financial transactions remain a high-risk factor. Ensure the 'liquidity-manager' subagent is thoroughly audited, follows strict security best practices, and implements robust input validation and authorization checks. Implement strong, explicit user confirmation mechanisms for all financial transactions, ensuring the user understands the full implications and potential risks. Consider implementing fine-grained permissions for the 'liquidity-manager' if possible, rather than a single broad delegation, to adhere to the principle of least privilege. | LLM | Manifest |
Scan History
Embed Code
[](https://skillshield.io/report/2134fe7734349a05)
Powered by SkillShield