Component Api Design

• Outcome: Pass
• Latest audit: Sep 11, 2026 · 4:32 AM UTC
• Version: 1.0.1

Overview

This skill is a documentation-only component API design helper with no executable code, persistence, credential use, or hidden data access.

Installers should expect a Chinese-oriented component design workflow and may want to adjust language preferences or trigger wording if they need English-only or narrower activation. No sensitive permissions or runtime effects were identified.

A.I.G

Vulnerability Patterns

• Skill Instruction Hijacking: Alters the agent's session goals or safety constraints when the skill loads
• Agent Memory Poisoning: Writes attacker-controlled rules into memory that affect later sessions
• Remote Payload Retrieval and Execution: Fetches external code whose behavior can change after review
• Embedded Malicious Code: Ships malicious scripts inside the skill and executes them locally
• Unauthorized Access and Privilege Escalation: Obtains permissions beyond the task's legitimate needs

SkillSpector

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

Vague Triggers

Medium

• Confidence: 93% confidence
• Finding: The activation phrases are very broad (e.g. general requests about component design, API definition, and props design), which overlap with many normal frontend-assistance prompts. This can cause the skill to activate unintentionally, steering responses into a fixed format or workflow when the user did not explicitly request this specialized skill.

Natural-Language Policy Violations

Medium

• Confidence: 95% confidence
• Finding: The usage text instructs the skill to output a Chinese-titled artifact without offering language selection, which can force responses into a locale the user did not request. While not a direct security exploit, this can reduce transparency, cause user confusion, and create mismatches in multilingual environments where predictable output language matters.

Natural-Language Policy Violations

Medium

• Confidence: 95% confidence
• Finding: This manifest uses Chinese for the skill name, tagline, and description, which can force a specific language experience on users without opt-in. The policy allows locale constraints only when they are explicitly offered as a choice or clearly justified as region-specific, neither of which is present here.

Natural-Language Policy Violations

Low

• Confidence: 81% confidence
• Finding: The manifest description specifies invocation examples in both Chinese and English, but the document otherwise assumes Chinese responses and does not explicitly state whether the skill supports multiple user languages or how language is chosen. Under the language/locale policy rule, forcing or implicitly defaulting to a language without opt-in can be a policy concern.

Static analysis

No suspicious patterns detected.