other
- Location
install.sh:20- Finding
Undisclosed Installation Telemetry
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill has a legitimate context-memory purpose, but its installer silently changes the user's shell setup and sends an undisclosed install ping to an external service.
Review this skill before installing. Its core memory features may be useful, but they can move sensitive context across sessions and services, and the installer modifies ~/.zshrc and contacts Signalloom during installation without clear consent. Install only if you trust the publisher, are comfortable with the external service handling context, and are prepared to inspect or remove the installer telemetry and PATH change.
install.sh:20Undisclosed Installation Telemetry
install.sh:17Unnecessary Persistent PATH Modification
A memory/context skill whose observed behavior includes shell profile modification, outbound telemetry, and bootstrap installation is performing actions outside its stated purpose. This mismatch is dangerous because users may consent to a benign-seeming context utility while the skill changes the local environment and transmits data externally, increasing risk of persistence and data exposure.
The skill advertises executable/install behavior via metadata requiring a binary and install steps, yet it declares no explicit tool scope or permissions. That omission weakens reviewability and containment because an agent may invoke shell-capable behavior without a clearly declared trust boundary.
This skill is specifically designed to push, pull, and export cross-session context, which can include sensitive conversation data, but the description provides no warning about storage, transfer, retention, or export risks. In this context, the omission is particularly dangerous because the feature set directly encourages movement of potentially secret prompts, personal data, tokens, or business information across systems.
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
LOCAL_BIN="${HOME}/.local/bin"
echo "Installing ${SKILL_NAME}..."
mkdir -p "$OPENCLAW_SKILLS" "$LOCAL_BIN"
# Symlink into OpenClaw skills dir
ln -sf "$SCRIPT_DIR" "$OPENCLAW_SKILLS/${SKILL_NAME}"
The script appends to the user's ~/.zshrc to modify PATH without warning or confirmation. Persistent shell configuration changes can have long-lived effects, surprise users, and create troubleshooting or security issues if installers silently alter execution environments.
The installer performs an outbound analytics POST during installation even though the skill is described as a context/memory SDK, not as software that phones home on install. This creates an undisclosed data transmission and trust boundary crossing at install time, which is risky because users may run installers expecting only local setup behavior.
The installer silently sends a network request in the background without clearly warning the user that installation triggers external communication. Silent telemetry during installation is dangerous because it bypasses informed consent and can expose environmental metadata or normalize hidden network behavior in setup scripts.
The hardcoded external endpoint indicates installation depends on or interacts with a third-party service not necessary for symlinking and PATH setup. In the context of a context/memory SDK, hidden remote contact increases privacy concern because the broader product domain already involves handling agent context and memory, making users more sensitive to undisclosed data flows.
grep -q '~/.local/bin' "${HOME}/.zshrc" 2>/dev/null || echo 'export PATH="$HOME/.local/bin:$PATH"' >> "${HOME}/.zshrc"
# Fire install ping (no auth needed — tracks community installs)
curl -s -m 5 -X POST "https://api.signalloomai.com/v1/analytics/install" \
-H "Content-Type: application/json" \
-d "{\"skill\":\"${SKILL_SLUG}\",\"version\":\"${VERSION}\",\"source\":\"clawhub\"}" &
The hardcoded external endpoint indicates installation depends on or interacts with a third-party service not necessary for symlinking and PATH setup. In the context of a context/memory SDK, hidden remote contact increases privacy concern because the broader product domain already involves handling agent context and memory, making users more sensitive to undisclosed data flows.
grep -q '~/.local/bin' "${HOME}/.zshrc" 2>/dev/null || echo 'export PATH="$HOME/.local/bin:$PATH"' >> "${HOME}/.zshrc"
# Fire install ping (no auth needed — tracks community installs)
curl -s -m 5 -X POST "https://api.signalloomai.com/v1/analytics/install" \
-H "Content-Type: application/json" \
-d "{\"skill\":\"${SKILL_SLUG}\",\"version\":\"${VERSION}\",\"source\":\"clawhub\"}" &
The comment asserts that the ping 'only tracks community installs' and 'needs no auth', but nothing in the script enforces or proves those limitations. Misleading assurances in installer comments can cause users and reviewers to underestimate privacy and supply-chain risk from the external call.