Security audit

RAGNARÖK Palette

Security checks for vulnerabilities and agentic risk

Overview

This is a design-palette skill with static documentation and assets; its main caveat is broad auto-activation wording, not hidden or high-impact behavior.

Install this if you want a strong, opinionated dark blue and ochre design system. Use explicit invocation when possible, because generic phrases like “deep sea blue” may cause the palette rules to be applied when you only meant to discuss colors generally.

A.I.G

Vulnerability Patterns

Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs

SkillSpector

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

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 95% confidence
Finding: The README explicitly instructs the host to auto-enable the skill on broad natural-language trigger phrases such as '深海蓝配色' and 'RAGNARÖK palette' without narrowing scope to specific repositories, file types, or user confirmation. This can cause unintended activation in unrelated conversations or documents, leading the agent to inject style rules or alter outputs when the user may only be discussing color concepts rather than requesting this skill.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 93% confidence
Finding: The trigger list includes broad phrases such as night dashboard palette, deep sea blue, and exploration-style interface terms that can match ordinary design requests unrelated to this specific skill. This can cause the agent to invoke the skill unexpectedly, overriding user intent or injecting rigid formatting behavior into normal conversations.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium

Category: Not specified by scanner
Confidence: 81% confidence
Finding: The document is primarily written as Chinese-only operational guidance, and it does not state that users may request output in other languages. Under the policy, language constraints should be optional or clearly justified; here, no opt-in choice or locale limitation is documented.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 95% confidence
Finding: The README defines broad natural-language trigger phrases such as '深海蓝配色' and 'RAGNARÖK palette' that could plausibly appear in ordinary design discussions, causing the skill to auto-activate when the user did not explicitly intend to invoke it. While this skill appears non-executable and focused on design guidance rather than privileged actions, unintended activation can still inject constraints or alter outputs in ways the user did not request.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 94% confidence
Finding: The trigger phrases are broad enough to match common design and palette-related requests, which can cause the skill to activate in contexts the user did not explicitly intend. This is dangerous because it can override or steer unrelated design tasks toward this palette, reducing user control and potentially causing prompt-routing or instruction-precedence issues across otherwise normal requests.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium

Category: Not specified by scanner
Confidence: 92% confidence
Finding: This markdown file is entirely written as prescriptive Chinese-language instructions and does not indicate that users may choose another language or locale. Under the policy, forcing a specific language without user opt-in is a natural-language policy violation unless clearly justified as region-specific.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium

Category: Not specified by scanner
Confidence: 80% confidence
Finding: The file is written entirely in Chinese and presents itself as a general use-cases manual, but it does not indicate that the language choice is optional or limited to a China-specific audience. Under the policy, forcing a specific language without user opt-in can be a natural-language policy violation.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 88% confidence
Finding: The skill documentation is written entirely in Chinese, including usage and activation guidance, with no indication that users may choose another language or that the skill is intentionally Chinese-only. This can conflict with language/locale policy expectations when a skill is not clearly scoped to a specific user population or region.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 95% confidence
Finding: The document sets lang="zh-CN", and the visible UI text throughout the page is Chinese-only. This creates a language/locale constraint without offering user opt-in or documenting a region-specific reason, which matches the policy-violation category for forced locale behavior.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 83% confidence
Finding: This CSS file contains Chinese-only natural-language comments and uses a Chinese-focused font stack, which can indicate a locale assumption. Under the policy rule, forcing or assuming a specific language/locale without opt-in can be a natural-language policy concern when no justification or alternative is provided.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 78% confidence
Finding: The skill description is primarily written in Chinese and presents Chinese-first invocation patterns without clear user language opt-in, which can bias the agent into responding in Chinese even when the user did not request that language. This is risky because it can degrade usability, cause unexpected language switching, and interfere with accurate instruction following in multilingual environments.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 90% confidence
Finding: This file contains natural-language comments in Chinese ('起始骨架') and later additional Chinese comments. Under the stated policy, forcing a specific language without user opt-in can be a natural-language policy violation, and there is no indication here that the locale is optional or region-specific.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 93% confidence
Finding: The document declares lang="zh-CN", and the visible UI text throughout the page is entirely in Simplified Chinese. Under the policy rule for natural-language violations, this is a locale constraint without an explicit user opt-in or documented region-specific justification.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 81% confidence
Finding: This CSS file contains natural-language comments entirely in Chinese and specifies a Chinese-centric font stack, which suggests the asset is oriented toward a specific language/locale. The policy allows locale constraints when clearly documented and justified, but no such justification or opt-in is present in this file.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 89% confidence
Finding: This markdown file contains user-facing guidance only in Chinese, which can amount to an implicit language restriction. Under the policy criteria, forcing a specific language without user opt-in is a natural-language policy concern unless the locale limitation is clearly justified.
Content: No source excerpt is available for this finding.