Skills convex-setup-auth

📦

convex-setup-auth

Name: convex-setup-auth
Author: get-convex

Content revision r1 Safe 🌐 Network access🔑 Env variables⚙️ External commands

Set Up Convex Authentication

Convex auth setup can fail when provider wiring, environment variables, and backend checks do not match. This skill guides the correct provider flow and adds verified Convex authentication patterns.

Supports: Claude Codex Code(CC)

🥈 80 Silver

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "convex-setup-auth" from https://skillstore.io/skills/get-convex-convex-setup-auth.md and its manifest at https://skillstore.io/api/skills/get-convex-convex-setup-auth/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/get-convex-convex-setup-auth.md Signed manifest GET /api/skills/get-convex-convex-setup-auth/manifest Signed lockfile GET /api/skills/get-convex-convex-setup-auth/lockfile

Test it

Using "convex-setup-auth". Set up auth for a new Convex app with Convex Auth.

Expected outcome:

Provider decision recorded, required setup steps completed, client provider wired, protected backend checks added, and local sign-in validation listed.

Using "convex-setup-auth". Connect Clerk to an existing Convex app.

Expected outcome:

The response identifies existing Clerk files, updates Convex auth wiring, confirms required environment values, and lists sign-in tests.

Using "convex-setup-auth". Make this Convex app production-ready for Auth0.

Expected outcome:

The result separates local and production tenant settings, checks redirect URLs, and warns when Auth0 token validation needs manual review.

Security Audit

Safe

v4 • 7/5/2026 Open versioned report

AI review found the static detections are false positives from Markdown links, inline code, TypeScript examples, and documented environment variable names. The skill handles sensitive auth configuration, but the reviewed files do not show credential exfiltration, prompt injection, unauthorized network requests, or executable shell behavior.

Files scanned

656

Lines analyzed

Review items

False positives ignored

Risk Factors

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/get-convex-convex-setup-auth/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/get-convex-convex-setup-auth/security.svg)](https://skillstore.io/skills/get-convex-convex-setup-auth?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/get-convex-convex-setup-auth?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/get-convex-convex-setup-auth/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/get-convex-convex-setup-auth.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

get-convex. (2026). convex-setup-auth security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/get-convex-convex-setup-auth/audits/4

BibTeX citation

@techreport{get-convex-get-convex-convex-setup-auth-2026,
  author = {get-convex},
  title = {convex-setup-auth security audit report (audit version 4)},
  institution = {Skillstore},
  year = {2026},
  number = {4},
  url = {https://skillstore.io/skills/get-convex-convex-setup-auth/audits/4},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "convex-setup-auth security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
  - name: "get-convex"
date-released: "2026-07-05"
url: "https://skillstore.io/skills/get-convex-convex-setup-auth/audits/4"
identifiers:
  - type: other
    value: "skillstore:get-convex-convex-setup-auth:audit:4"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Launch login in a Convex app

A product engineer adds sign-up, sign-in, and backend identity checks to a new Convex project.

Connect an existing auth provider

A full-stack developer links Clerk, WorkOS AuthKit, or Auth0 to Convex without replacing current auth flows.

Prepare production auth configuration

A technical lead reviews local and production provider settings before deploying protected Convex features.

Try These Prompts

Add basic login

Add authentication to this Convex app. Ask me which provider to use if the repo does not make it clear.

Wire an existing provider

This app already uses Clerk. Connect it to Convex auth, preserve the current sign-in flow, and verify Convex sees authenticated users.

Protect backend functions

Review my Convex queries and mutations. Add server-side identity checks and authorization for user-owned records where needed.

Prepare production auth

Configure production-ready Convex authentication for WorkOS AuthKit. Separate dev and production settings, then provide a validation checklist.

Best Practices

Choose the auth provider before writing setup code.
Use official provider documentation for current package and CLI steps.
Verify both frontend login and ctx.auth.getUserIdentity() in Convex functions.

Avoid

Do not trust client-provided user IDs for protected data.
Do not add a users table unless the app needs app-level user records.
Do not claim setup is complete until Convex recognizes the authenticated session.