Toolverse
All skills
Security

clerk-install-auth

by jeremylongshore

Install and configure Clerk SDK/CLI authentication.\nUse when setting up a new Clerk integration, configuring API keys,\nor initializing Clerk in your project.\nTrigger with phrases like \

Installation

Pick a client and clone the repository into its skills directory.

Installation

Quick info

Author
jeremylongshore
Category
Security
GitHub repo

About this skill

Install and configure Clerk SDK/CLI authentication.\nUse when setting up a new Clerk integration, configuring API keys,\nor initializing Clerk in your project.\nTrigger with phrases like \

How to use

  1. Przygotuj wymagane informacje: masz zainstalowany Node.js 18 lub nowszy, menedżer pakietów (npm, pnpm lub yarn) oraz konto Clerk z dostępem do API Keys w dashboard.clerk.com — potrzebujesz Publishable Key (pk_test_*) i Secret Key (sk_test_*).

  2. Wyzwól umiejętność frazą taką jak "install clerk", "setup clerk", "clerk auth", "configure clerk API key" lub "add clerk to project" — system automatycznie zainstaluje odpowiedni pakiet SDK dla Twojego frameworka (Next.js, React SPA, Express lub backend).

  3. Skonfiguruj zmienne środowiskowe: umiejętność utworzy plik .env.local z polami NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY i CLERK_SECRET_KEY — wstaw tam swoje klucze z dashboardu Clerk i upewnij się, że .env.local znajduje się w .gitignore.

  4. Dodaj ClerkProvider do layoutu aplikacji: dla Next.js App Router umiejętność wstawi ClerkProvider w app/layout.tsx, dla React SPA zawiń aplikację w ClerkProvider w głównym pliku — to umożliwi dostęp do kontekstu autentykacji w całej aplikacji.

  5. Zweryfikuj działanie: sprawdź czy komponenty SignedIn, SignedOut i UserButton są dostępne w Twojej aplikacji — system powinien wyświetlić przyciski logowania i profil użytkownika po poprawnej konfiguracji.

Related skills

software-security

by project-codeguard

A software security skill that integrates with Project CodeGuard to help AI coding agents write secure code and prevent common vulnerabilities. Use this skill when writing, reviewing, or modifying code to ensure secure-by-default practices are followed.

Security
1678

python-expert

by Shubhamsaboo

Senior Python developer expertise for writing clean, efficient, and well-documented code.\nUse when: writing Python code, optimizing Python scripts, reviewing Python code for best practices,\ndebugging Python issues, implementing type hints, or when user mentions Python, PEP 8,

Security
2777

payload

by payloadcms

Use when working with Payload CMS projects (payload.config.ts, collections, fields, hooks, access control, Payload API). Use when debugging validation errors, security issues, relationship queries, transactions, or hook behavior.

Security
50171

obsidian

by gapmiss

Comprehensive guidelines for Obsidian.md plugin development including all 27 ESLint rules, TypeScript best practices, memory management, API usage (requestUrl vs fetch), UI/UX standards, and submission requirements. Use when working with Obsidian plugins, main.ts files,

Security
14111

reviewing-code

by CaptainCrouton89

Systematically evaluate code changes for security, correctness, performance, and spec alignment. Use when reviewing PRs, assessing code quality, or verifying implementation against requirements.

Security
1493

backend-security-coder

by sickn33

Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.

Security
1133