clerk-data-handling

Pass

Audited by Gen Agent Trust Hub on Mar 24, 2026

Risk Level: SAFECOMMAND_EXECUTIONDATA_EXFILTRATIONPROMPT_INJECTION
Full Analysis
  • [SAFE]: No malicious patterns, obfuscation, or unauthorized access attempts were identified. The skill's instructions and referenced implementation guide follow established security and development practices for the stated use case of user data management.
  • [COMMAND_EXECUTION]: The skill is configured to allow Bash(npm:*) commands. This is a standard permission for development-focused skills to enable the installation and management of project dependencies like @clerk/nextjs.
  • [DATA_EXFILTRATION]: The implementation guide in lib/audit-log.ts includes a pattern for sending audit events to an external endpoint via the AUDIT_LOG_ENDPOINT environment variable. This is a legitimate implementation strategy for compliance auditing and centralized log management.
  • [PROMPT_INJECTION]: The skill processes user-supplied data from Clerk and application databases for features like data export. This creates a surface for indirect prompt injection if instructions are embedded in the processed data fields.
  • Ingestion points: Data retrieved via clerkClient and database queries in references/implementation-guide.md.
  • Boundary markers: No specific delimiters or "ignore instructions" markers are used in the provided code templates.
  • Capability inventory: The skill utilizes Read, Write, Edit, Bash, and Grep tools.
  • Sanitization: The sanitizeForExport function in the guide removes metadata like database IDs and timestamps but does not perform content-level sanitization or escaping of string data.
Audit Metadata
Risk Level
SAFE
Analyzed
Mar 24, 2026, 05:43 PM