clerk-install-auth

The skill is coherent with its stated purpose: guiding a developer through installing Clerk SDKs and configuring authentication keys, wrapping the app with ClerkProvider, and enabling middleware. It relies on official registry packages and uses conventional environment-based credentials. Data flows align with typical Clerk usage, and there is no evident credential harvesting, covert data leakage, or unauthorized actions. Overall risk is low to moderate (benign), with standard credential handling caveats. Ensure secret keys are kept out of version control and rotated per Clerk best practices.