Trust Assessment
session-logs received a trust score of 73/100, placing it in the Caution category. This skill has some security considerations that users should review before deployment.
SkillShield's automated analysis identified 2 findings: 0 critical, 2 high, 0 medium, and 0 low severity. Key findings include Potential Command Injection in `rg` search pattern, Potential Command Injection in file path placeholder.
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 18, 2026 (commit b62bd290). SkillShield performs automated 4-layer security analysis on AI skills and MCP servers.
Layer Breakdown
Behavioral Risk Signals
Security Findings2
| Severity | Finding | Layer | Location | |
|---|---|---|---|---|
| HIGH | Potential Command Injection in `rg` search pattern The skill provides example commands where user-supplied 'keyword' or 'phrase' is directly inserted into `rg` commands (e.g., `rg -i "keyword"`). If the agent replaces these placeholders with unsanitized user input, a malicious user could inject arbitrary shell commands by breaking out of the quoted string or craft a denial-of-service regex pattern. This could lead to arbitrary code execution or resource exhaustion. Ensure all user-supplied input used in shell commands, especially regex patterns, is properly sanitized and quoted. For `rg`, consider using the `-F` (fixed strings) option if exact matches are desired, or carefully escape special regex characters if full regex is needed. Always quote variables when passing them to shell commands (e.g., `rg -i "$keyword"`). | LLM | SKILL.md:60 | |
| HIGH | Potential Command Injection in file path placeholder Several example commands use placeholders like `<session>.jsonl` and `<id>.jsonl` for file paths. If these placeholders are replaced by unsanitized user input, an attacker could inject arbitrary shell commands by crafting a malicious path (e.g., `"; rm -rf /; #.jsonl"`). This could lead to arbitrary code execution, data deletion, or unauthorized file access. All user-supplied input intended for file paths must be strictly validated against allowed characters and patterns, and properly quoted when passed to shell commands. Avoid allowing path traversal characters (`..`, `/`) in user-controlled parts of the path. Consider using a dedicated file access API instead of direct shell execution for file operations. | LLM | SKILL.md:55 |
Scan History
Embed Code
[](https://skillshield.io/report/154a61dd1f59b730)
Powered by SkillShield