KWDB Schema Design

• Outcome: Pass
• Latest audit: Aug 28, 2026 · 12:53 AM UTC
• Version: 1.2.1

Overview

This is a markdown-only KWDB schema-design skill whose risky SQL examples are disclosed and user-directed, though users should review destructive DDL and privilege examples carefully.

Installers should treat this as a KWDB-specific DDL helper, not a general SQL authority. Before running generated DROP, CASCADE, retention, or privilege commands, confirm the target database, backups, retention requirements, and authorization; for generic SQL requests, clarify whether KWDB is actually intended.

SkillSpector

Vulnerability Patterns

• Trigger Abuse: Overly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
• MCP Tool Poisoning: Hidden Instructions, Unicode Deception, Parameter Description Injection
• 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

Findings (8)

Intent-Code Divergence

Medium

• Confidence: 96% confidence
• Finding: The file states earlier that KWDB auto-creates an index for foreign key columns, but later examples and checklist items instruct users to manually create or remember FK indexes. In a schema-design skill, this contradictory guidance can cause duplicate index creation, unnecessary storage/write overhead, and propagate incorrect DDL into production schemas.

Description-Behavior Mismatch

Medium

• Confidence: 90% confidence
• Finding: The file documents user, role, and privilege administration even though the skill is explicitly scoped to schema design and marked as not for deployment or broader security administration. That scope expansion can cause the agent to answer requests about access control and account management that it was not intended to handle, increasing the chance of unsafe privilege guidance such as overbroad GRANT ALL usage or accidental assistance with unauthorized admin operations.

Intent-Code Divergence

Low

• Confidence: 79% confidence
• Finding: The note says schema design should focus on table structure, yet the document still includes operational security administration commands. This inconsistency can mislead routing and safety logic, making the agent more likely to surface security-sensitive DDL in contexts where it should stay within schema design, weakening intended boundaries.

Vague Triggers

Medium

• Confidence: 90% confidence
• Finding: The activation section includes very broad phrases such as 'create table', 'schema design', 'primary key', and generic relational terms that are not uniquely tied to KWDB. This can cause the skill to trigger for unrelated database requests, leading the agent to apply KWDB-specific guidance in the wrong context and potentially produce incorrect or unsafe DDL recommendations.

Natural-Language Policy Violations

Medium

• Confidence: 91% confidence
• Finding: The example includes Chinese-language guidance/comments in generated DDL output without any user request or opt-in, which can steer downstream agents to emit mixed-language responses unexpectedly. While not a direct code-execution issue, it can cause prompt-quality degradation, policy noncompliance, or user confusion in systems that assume output-language fidelity.

Vague Triggers

Medium

• Confidence: 90% confidence
• Finding: The trigger list includes very broad, common terms such as "schema," "table," "index," and generic domain words like "sensor" and "metrics," which can cause the skill to activate for unrelated requests. In an agentic system, over-broad activation can misroute user intent, produce out-of-scope guidance, and increase the chance that the wrong skill handles sensitive or high-impact tasks without proper specialization or clarification.

Missing User Warnings

Medium

• Confidence: 93% confidence
• Finding: The reference includes `DROP DATABASE` and `DROP SCHEMA ... CASCADE` examples without adjacent warning text about irreversible deletion. In a schema-design skill, users may copy commands directly, and the lack of explicit caution increases the chance of accidental destructive execution against the wrong environment or tenant.

Missing User Warnings

Medium

• Confidence: 89% confidence
• Finding: The document states that data exceeding retention is silently dropped, but it does not elevate this into an explicit warning about irreversible data loss or operational safeguards. In a schema-design skill, this can lead users to configure retention policies that automatically delete production time-series data without appreciating the consequence, causing availability and integrity loss for historical records, audits, or investigations.

VirusTotal

64/64 vendors flagged this skill as clean.

Static analysis

No suspicious patterns detected.