Skylv Agent Settings Manager

Security checks across malware telemetry and agentic risk

Overview

This is an instruction-only configuration-management skill with sensitive but disclosed examples and no bundled executable code.

Install only if you intend to let an agent assist with configuration administration. Before running any referenced config.js command, review the actual implementation, use least-privilege Git and secret-store credentials, require explicit confirmation for production changes or secret rotation, and avoid watch or auto-reload on critical systems without review and rollback controls.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (2)

Vague Triggers

Medium
Confidence
88% confidence
Finding
The skill metadata includes broad, generic activation terms such as configuration, env variables, and config validation, which can cause the skill to trigger in contexts beyond the user's actual intent. Because this skill includes operationally sensitive actions like secret management, sync, rollback, and environment promotion, unintended activation could lead an agent to suggest or perform risky configuration operations on sensitive systems or data.

Missing User Warnings

Medium
Confidence
94% confidence
Finding
The skill documents sensitive capabilities including secret setting/rotation, configuration rollback, auto-reload, and syncing from repositories, but it does not warn users about the security and operational risks of exposing secrets, overwriting state, or propagating bad configurations into production. In this context, the absence of warnings is more dangerous because the skill is explicitly positioned for cross-environment and production configuration management, where mistakes can cause outages, credential exposure, or unsafe changes at scale.

VirusTotal

64/64 vendors flagged this skill as clean.

View on VirusTotal