Back to Skills

convex-security-audit

Deep security review patterns for authorization logic, data access boundaries, action isolation, rate limiting, and protecting sensitive operations

401stars32forksUpdated 8/17/2026

Security Assessment

Safe(95/100)
Security Score95/100

About convex-security-audit

Convex Security Audit is a defensive security-review reference skill for Convex applications. It provides patterns and annotated TypeScript examples for auditing five areas: authorization logic (who can do what), data access boundaries (what data users can see), action isolation (protecting external API calls), rate limiting (preventing abuse), and protecting sensitive operations. It solves the problem of applying consistent, best-practice security checks when building or reviewing Convex backends.

The skill directs the reader to fetch the latest official Convex documentation before implementing (linking to Convex auth, production, and llms.txt resources) rather than assuming APIs. Its body is worked examples: role-based and permission-based access control helpers (requireRole, requirePermission with a role hierarchy), ownership-verified queries that avoid revealing whether a record exists, shared-resource access lists, and action isolation that reads API keys from environment variables (never hardcoded), authenticates the caller, and logs API calls for an audit trail. The guidance is defensive throughout, emphasizing least-privilege authorization, ownership checks, and not exposing secrets in responses.

Target users are Convex developers and reviewers who want to harden authorization, data-access, and external-integration code, or to run a structured security pass over an existing Convex project. The included files are a SKILL.md, an agent configuration, and a small SVG logo asset; the credential handling shown follows standard environment-variable practice with no exfiltration.

FAQ

What does this skill cover?

Five audit areas for Convex apps: authorization logic, data access boundaries, action isolation for external API calls, rate limiting, and protecting sensitive operations, each with annotated TypeScript patterns.

Is this offensive or defensive security tooling?

Defensive. It teaches best-practice access control, ownership checks, and secret handling to harden applications; it contains no exploit code or attack automation.

How does it handle API keys and secrets?

External API keys are read from environment variables (process.env), never hardcoded, and are not exposed in responses; calls are logged for an audit trail.

Does it require external calls?

It recommends fetching the latest official Convex documentation before implementing, and its example actions call external APIs, but the skill itself is a pattern/reference guide.

Who is it for?

Convex developers and reviewers who want to audit or harden authorization, data-access boundaries, and external-integration code in their applications.

All Files

3 files
SKILL.md14.5 KB
View
agents/openai.yaml0.1 KB
View
assets/small-logo.svg1.2 KB
View

Install convex-security-audit

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill