Init

Security checks across malware telemetry and agentic risk

Overview

This is a disclosed onboarding skill that asks setup questions and writes local Solo Factory configuration files for later use.

Install only if you want Solo Factory to create or update ~/.solo-factory/defaults.yaml and .solo/ files in a selected project. Review the generated files, avoid putting secrets in the answers, confirm the project path before running, and skip the optional Solograph/uvx check if you do not want external package execution.

SkillSpector

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

Vague Triggers

Medium
Confidence
91% confidence
Finding
The trigger phrases include broad language such as 'configure defaults', 'first time setup', and 'onboard me', which can cause the skill to activate in contexts where the user did not intend persistent configuration changes. Because this skill writes files to both the home directory and project directory, accidental invocation can lead to unwanted state changes and privacy-sensitive data being stored.

Missing User Warnings

Medium
Confidence
95% confidence
Finding
The skill description does not prominently warn that it will write persistent configuration files under both ~/.solo-factory and the current project's .solo directory. Users may consent to onboarding without realizing that org identifiers, team IDs, repository names, and preferences will be stored on disk for later reuse by other skills.

VirusTotal

66/66 vendors flagged this skill as clean.

View on VirusTotal