Software Data Github Interact Developer Helper

• Outcome: Pass
• Latest audit: Jul 29, 2026 · 5:51 AM UTC
• Version: 0.20260729.110214

Overview

This is a documentation-style GitHub/developer workflow helper with overly broad activation wording but no hidden execution, persistence, credential use, or data exfiltration behavior in the inspected artifacts.

Install only if you want a general GitHub-style developer workflow helper. Be aware that its trigger wording is loose, so it may activate for generic CLI, API, issue, or bug-fix requests unless your agent platform lets you require explicit invocation.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Trigger Abuse: Overly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (10)

Vague Triggers

High

• Confidence: 95% confidence
• Finding: The trigger phrases are excessively broad and can match ordinary user requests unrelated to this specific skill, causing unintended invocation. In an agent ecosystem, overbroad activation can route sensitive or general-purpose development tasks into the wrong skill, increasing the chance of unsafe actions, confusion, or privilege misuse through mis-scoped automation.

Vague Triggers

Medium

• Confidence: 93% confidence
• Finding: The trigger phrases are broad enough to match ordinary requests about software, GitHub, CLI, issues, APIs, PRs, and bug fixes, which can cause the skill to activate outside the user's explicit intent. In an agent environment, over-broad activation can route unrelated tasks into this skill, increasing the chance of unintended actions, confused delegation, or misuse of GitHub-oriented workflows on sensitive requests.

Vague Triggers

Medium

• Confidence: 93% confidence
• Finding: The trigger list is very broad and includes common terms like "github", "cli", "issue", "run", and "api", which are likely to appear in many unrelated developer requests. This can cause the skill to activate unintentionally, leading to misrouting, irrelevant guidance, or unsafe over-application of this skill in contexts where a more specific or safer skill should handle the request.

Vague Triggers

Medium

• Confidence: 88% confidence
• Finding: The example trigger sentences are truncated, repetitive, and malformed, so they do not clearly communicate when the skill should be invoked. Poor activation guidance increases the chance of accidental invocation or inconsistent routing behavior, especially if downstream systems or authors rely on these examples to shape matching logic.

Vague Triggers

High

• Confidence: 95% confidence
• Finding: The trigger keywords are very broad (`github`, `cli`, `run`, `api`, `issue`) and overlap with ordinary developer conversations, making accidental invocation likely. In an agent environment, over-broad activation can route unrelated requests into this skill, causing confused-deputy behavior, inappropriate actions, or bypass of safer/more specific workflows.

Vague Triggers

Medium

• Confidence: 88% confidence
• Finding: The description says to use the skill when users ask for broad categories like `software-and-data`, `github`, `interact`, `cli`, or `issue`, but it does not define boundaries for what requests are in scope. This ambiguity increases the chance that the agent applies the skill to unrelated or sensitive tasks, which can expand authority unexpectedly and reduce reliability of routing decisions.

Vague Triggers

Medium

• Confidence: 90% confidence
• Finding: The sample trigger phrases are generic help-seeking expressions (`Help me`, `I need a practical workflow`) attached to a long demand statement, without any security or scope constraints. Such examples can train or bias invocation systems toward matching common language patterns, increasing false activations and making downstream behavior less predictable.

Vague Triggers

Medium

• Confidence: 92% confidence
• Finding: The skill enables implicit invocation while providing only a broad, generic description of when it should be used. This can cause the agent platform to auto-select the skill in contexts the user did not clearly intend, increasing the chance of unintended GitHub- or developer-workflow actions, misleading guidance, or over-broad access to adjacent tasks.

Vague Triggers

High

• Confidence: 96% confidence
• Finding: The trigger sentence begins with a very broad everyday phrase ('Help me'), which can cause the skill to activate for many unrelated user requests. In an agent environment, overbroad activation increases the chance the wrong skill is selected, leading to unintended repository, CLI, or workflow guidance being injected into contexts where it was not requested.

Vague Triggers

Medium

• Confidence: 94% confidence
• Finding: The trigger description and sample trigger sentences define scope too loosely, covering generic requests for practical workflows without clear limits to GitHub-style development tasks. This ambiguity can cause accidental invocation across unrelated software or general-help scenarios, which is risky because the skill is positioned to provide implementation and issue-handling guidance that may not fit the user's actual intent.

VirusTotal

64/64 vendors flagged this skill as clean.

Static analysis

No suspicious patterns detected.