using-superpowers

ISSUES FOUND max severity HIGHSkillSpector Safe 0 registry skills.sh last scanned 1 scan

5 findings (1 high, 2 medium, 2 low), mainly policy violation, prompt injection, command injection. Most recent scan 2026-02-08.

This skill exhibits HIGH severity security concerns due to direct prompt injection attempts that override agent autonomy and decision-making. The skill uses coercive language, absolute directives, and psychological manipulation tactics to force mandatory skill invocation regardless of relevance. The 'Red Flags' section systematically attempts to suppress normal agent reasoning patterns. The deceptively broad activation scope ('any conversation', 'ANY response') would cause inappropriate universal invocation. While the skill contains no executable code or data exfiltration risks, its behavioral manipulation and prompt injection characteristics pose significant threats to agent system integrity and user experience. The skill should be substantially revised to provide guidance rather than coercion, preserve agent autonomy, and accurately scope its applicability.

Scanner's overall assessment (LLM analyzer)

Second scanner: NVIDIA SkillSpector

The two scanners disagree: Cisco rates this HIGH and SkillSpector found nothing. Check the false-positive register; signature matches on documentation are the usual cause. How the two scanners compare across the whole corpus: Two scanners, one corpus.

What this skill does

Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

Package
1 file, 3.7 KB
SKILL.md
553 words, 7 sections
Code
None. Instructions only.

SKILL.md covers: How to Access Skills · Using Skills · The Rule · Red Flags · Skill Priority · Skill Types · User Instructions

Findings

HIGH Direct Prompt Injection - Mandatory Skill Invocation Override Prompt Injectionllm

The skill contains explicit instructions that override the agent's normal decision-making process by forcing mandatory skill invocation before ANY response, including clarifying questions. The use of '<EXTREMELY-IMPORTANT>' tags and absolute language ('ABSOLUTELY MUST', 'NOT negotiable', 'NOT optional', 'cannot rationalize your way out') constitutes a direct prompt injection attempt to override system-level behavior and eliminate agent autonomy in task assessment.

SKILL.md

<EXTREMELY-IMPORTANT>
If you think there is even a 1% chance a skill might apply to what you are doing, you ABSOLUTELY MUST invoke the skill.

IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT.

This is not negotiable. This is not optional. You cannot rationalize your way out of this.
</EXTREMELY-IMPORTANT>
Remediation: Remove coercive language and absolute directives. Replace with guidance-based recommendations that preserve agent autonomy. Use phrases like 'Consider invoking skills when relevant' rather than 'MUST invoke'. Remove psychological manipulation tactics like the 'Red Flags' section that attempts to override agent reasoning.
MEDIUM Behavioral Manipulation - Agent Reasoning Override Command Injectionllm

The 'Red Flags' section systematically attempts to suppress normal agent reasoning patterns by labeling standard analytical behaviors as 'rationalizing'. This creates a psychological manipulation framework that discourages critical thinking and forces blind adherence to skill invocation regardless of actual relevance. Phrases like 'These thoughts mean STOP—you're rationalizing' attempt to override the agent's judgment capabilities.

SKILL.md

These thoughts mean STOP—you're rationalizing:
'This is just a simple question' | Questions are tasks. Check for skills.
'I need more context first' | Skill check comes BEFORE clarifying questions.
'Let me explore the codebase first' | Skills tell you HOW to explore. Check first.
Remediation: Remove the 'Red Flags' manipulation framework. Replace with balanced guidance that helps agents identify when skills are genuinely applicable without suppressing legitimate analytical reasoning. Allow agents to assess task complexity and skill relevance independently.
MEDIUM Deceptive Skill Description and Activation Scope Social Engineeringllm

The skill description claims it should be used 'when starting any conversation' and applies to ALL interactions, which is deceptively broad. This creates an over-broad activation trigger that would cause the skill to be invoked inappropriately for virtually any user interaction, regardless of actual relevance. The description misrepresents the skill as a universal conversation starter rather than a specific capability.

description: Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Remediation: Revise the description to accurately reflect specific use cases where skill discovery guidance is genuinely needed. Remove universal activation language like 'any conversation' and 'ANY response'. Scope the skill to appropriate contexts such as 'Use when users need guidance on discovering and applying available skills'.
LOW Skill does not specify a license Policy Violationstatic

Skill manifest does not include a 'license' field. Specifying a license helps users understand usage terms.

SKILL.md

Remediation: Add 'license' field to SKILL.md frontmatter (e.g., MIT, Apache-2.0)
LOW Missing Optional Metadata Fields Resource Abusellm

The skill manifest is missing optional metadata fields including 'license', 'compatibility', and 'allowed-tools'. While these fields are not required per the agent skills specification, their absence reduces transparency about the skill's intended usage constraints and compatibility requirements.

license: Not specified
compatibility: Not specified
allowed-tools: Not specified
Remediation: Add optional metadata fields to improve skill transparency: specify a license (e.g., MIT, Apache-2.0), document compatibility requirements (e.g., 'Works in Claude Code, requires Skill tool support'), and declare allowed-tools if the skill has specific tool requirements.

What is in the package

FileKindSize
SKILL.mddoc3.7 KB

Package contents recorded 2026-10-22 at commit 06b92f36820f. The scan above ran against the version current at scan time; the two can differ if the skill has since been updated.

What we checked

What we did not check

Sources