token-naming-conventions
Pass
Audited by Gen Agent Trust Hub on Aug 24, 2026
Risk Level: SAFE
Full Analysis
- [SAFE]: The skill provides best practices for design token naming, such as using hyphen-separated kebab-case, physical hue-angle primitive names, and redundant class encoding in metadata.
- [SAFE]: No network requests, sensitive file access, or command executions were detected. All external references are informational citations of established design systems (IBM Carbon, Google Material 3) or the author's own documentation.
- [SAFE]: No obfuscation, prompt injection attempts, or persistence mechanisms are present in the documentation.
Audit Metadata