MySQL8 CRM Schema Design Expert
v1.0.0MySQL 8 database schema design for CRM systems. Use this skill whenever the user needs to design, review, optimize, or generate database schemas for Customer...
⭐ 0· 19·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Benign
high confidencePurpose & Capability
The name/description match the provided content: detailed MySQL 8 CRM design guidance, reference docs, and example schemas. There are no extraneous environment variables, binaries, or installation steps requested that would be unrelated to database schema design.
Instruction Scope
SKILL.md and the reference files instruct the agent to read local reference files and produce SQL/design recommendations. There are no instructions to read unrelated system files, access credentials, contact external endpoints, or exfiltrate data. The guidance explicitly focuses on schema design, indexing, tenancy, and migration patterns.
Install Mechanism
No install spec or code files that would download or execute external artifacts are present — this is an instruction-only skill, which minimizes disk/execute risk.
Credentials
The skill declares no required environment variables, credentials, or config paths. The content references standard DB practices (encryption, keyrings) but does not request keys or other secrets from the environment.
Persistence & Privilege
always is false and the skill is user-invocable; it does not request persistent privileges or modify other skills or system-wide agent settings. Autonomous invocation is allowed by platform default but is not combined with other concerning capabilities here.
Assessment
This skill appears to do what it claims: provide MySQL 8 CRM schema guidance and example SQL. Before using generated SQL in production, review it carefully and run migrations in a staging environment. Verify tenant filters (tenant_id) and unique/index choices match your app to avoid cross-tenant leaks. Pay attention to sensitive fields: follow the guidance to encrypt highly sensitive columns and never store plaintext secrets. Finally, validate performance/indexing decisions against your real workload and adapt BIGINT/partitioning choices to your scale.Like a lobster shell, security has layers — review code before you run it.
latestvk97bw6gm576621qcfw442kc9n984by8p
License
MIT-0
Free to use, modify, and redistribute. No attribution required.