Software Data Github Interact Developer Helper

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

Overview

This is a documentation-only workflow helper for GitHub-style developer tasks, with broad activation wording but no hidden execution, credential handling, persistence, or destructive behavior.

Before installing, be aware that this skill may be selected for broad developer or GitHub-adjacent prompts. It does not appear to run code or access credentials by itself, but users should still review any proposed commands or code changes before approving them.

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 (9)

Vague Triggers

Medium

• Confidence: 90% confidence
• Finding: The trigger sentences are generic and expansive, causing the skill to activate for loosely related requests such as general software, GitHub, CLI, or issue-help tasks. Over-broad activation can route users into the wrong workflow, increasing the chance of inappropriate actions, confused delegation, or unsafe application of the skill in contexts it was not designed to handle.

Vague Triggers

Medium

• Confidence: 90% confidence
• Finding: The trigger phrases are broad enough to match many ordinary software-help requests, which can cause the skill to activate outside its intended scope. In an agent ecosystem, overbroad activation can route users into unintended workflows, increasing the chance of confused-deputy behavior, irrelevant actions, or accidental use of capabilities the user did not explicitly request.

Vague Triggers

Medium

• Confidence: 94% confidence
• Finding: The trigger keywords are very broad terms like "github", "cli", "issue", "run", and "api", which are common in ordinary developer conversations. This makes accidental activation likely, causing the wrong skill to engage in contexts it was not explicitly requested for, which can misroute workflows or produce irrelevant actions in multi-skill agent environments.

Vague Triggers

Medium

• Confidence: 92% confidence
• Finding: The example trigger sentences are vague, natural-language phrases that resemble ordinary user requests rather than deliberate skill invocation. In an agent-routing system, this increases the chance that unrelated conversations will match and activate the skill unexpectedly, reducing reliability and potentially bypassing more appropriate skills.

Vague Triggers

Medium

• Confidence: 95% confidence
• Finding: The trigger keywords include very common terms such as "github", "cli", "issue", "run", and "api", which are likely to appear in many unrelated user requests. This can cause unintended activation of the skill, leading the agent to apply the wrong workflow or expose behavior in contexts the user did not explicitly request.

Vague Triggers

Medium

• Confidence: 94% confidence
• Finding: The example trigger phrases are written as broad natural-language requests that closely resemble ordinary conversation, making accidental routing highly likely. Because they embed generic assistance wording rather than a distinctive activation pattern, the skill may be selected for many unrelated prompts involving help or workflows.

Vague Triggers

Medium

• Confidence: 94% confidence
• Finding: The skill enables implicit invocation while providing only a broad, generic description of when it should activate. This can cause the agent to invoke the skill in unintended contexts, potentially exposing repository, CLI, or workflow-related capabilities when the user did not clearly request them, increasing the risk of overreach or unsafe actions.

Vague Triggers

High

• Confidence: 95% confidence
• Finding: The trigger sentence is extremely broad and resembles common help-seeking language, which can cause the skill to activate outside its intended Github-style workflow scope. Overbroad activation increases the chance of prompt/skill hijacking, accidental invocation, and irrelevant handling of user requests that should be routed elsewhere.

Vague Triggers

Medium

• Confidence: 97% confidence
• Finding: The activation guidance provides keywords and trigger sentences but lacks clear boundaries, required conditions, and negative examples, so the skill may be selected for many unrelated software or general productivity requests. In an agentic system, ambiguous routing can expose users to incorrect actions, tool misuse, or unintended workflow execution under the wrong skill context.

VirusTotal

64/64 vendors flagged this skill as clean.

Static analysis

No suspicious patterns detected.