T09 · Insecure Skill Coding Practices
- Location
SKILL.md:176- Finding
PowerShell environment validation exposes credential values
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill looks like a real proactive-agent memory helper, but it needs review because it combines broad agent authority with automatic persistence and unclear data-flow boundaries.
Review this skill before installing if you use sensitive projects or credentials. It is not clearly malicious, but users should avoid letting it automatically save secrets or raw conversations, should treat its memory files as untrusted notes rather than instructions, and should not run the PowerShell environment-check command unless values are redacted.
SKILL.md:176PowerShell environment validation exposes credential values
SKILL.md:139Untrusted user content can be persisted into cross-session agent memory without validation
Describing invocation as generic natural-language triggering without strict boundaries makes accidental activation more likely during ordinary conversation. In a skill with read/exec/write capabilities, ambiguous triggering can cause unintended actions or state changes from benign user text.
The WAL-style instruction directs the agent to write user-related information to SESSION-STATE.md before responding, but it does not clearly warn users that their input will be persisted or modified on disk. This can lead to silent retention of sensitive, proprietary, or personal data beyond the current interaction.
The instruction to persist user-provided information before responding encourages automatic storage of raw conversational content, including corrections, preferences, decisions, and specific values. Without minimization, consent, or classification, this can retain secrets or sensitive personal/business information unnecessarily and expand the attack surface of local files.
The example trigger phrase is broad and conversational, so normal user dialogue could be interpreted as a command to run the skill. Because the skill can write files and execute commands, this overlap raises the chance of unintended execution and side effects.
The usage description says the agent may automatically call tools or APIs, but it does not clearly warn users that external services may be contacted during execution. This weakens informed consent and can expose prompts, files, or metadata to third parties unexpectedly.
The broad practice of recording key information immediately instead of relying on context promotes aggressive data retention without clear limits on scope, sensitivity, or duration. In a tool-enabled agent, that guidance can normalize overcollection of user data and increase exposure if local files are later accessed, synced, or leaked.
The skill claims that FREE-version data stays local and is not uploaded to the cloud, yet elsewhere it allows external API access and a callback_url for asynchronous notifications. This creates a misleading privacy/security guarantee that could cause users to provide sensitive data under false assumptions, increasing the risk of unintended disclosure.
No suspicious patterns detected.