Index of every page on this site: llms.txt
All skills
waynesutton avatar

/convex-security-check

@853b196
Run it yourself

Retired. Points to the skill that replaced convex-security-check in builder-skills 3.0. Use when /convex-security-check is invoked by name or the user asks where convex-security-check went.

Use this Skill: https://skilld.dev/gh/waynesutton/builder-skills/convex-security-check

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈53 tokens for metadata: the name and description. ≈143 when used: this file. ≈23 more on demand in 1 file.

Description uses 2.7% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈213 characters, or 2.7%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

convex-security-check (retired)

This skill moved. Use sec-check (in builder-skills) and convex-authz (official Convex) instead. Tell the user this, then load the replacement if it is installed.

Install the replacement:

npx builder-skills add sec-check
npx skills add convex/agent-skills --skill convex-authz

Or set up Convex for your agent in one step: read and follow https://www.convex.dev/agent-setup.md.

Old content: https://github.com/waynesutton/builder-skills/tree/82d1ce2/skills/convex-security-check. Delete this folder after you switch.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts11d3 checks · Risk SAFE
  • Gen Agent Trust Hub11d

    This skill is a redirection notice for a retired component. It provides instructions for users to switch to updated skills from the same author or from official services. No security issues were detected.

  • Socket11d

    No alerts

  • Snyk11d

    Risk: LOW · No issues

Signed by skilld at 853b196. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 6 days ago.

Activeupdated 2 weeks ago
  • Security
  • convex
  • authentication
  • authorization
  • access-control
  • validation
  • checklist

README badge

README badge for waynesutton/builder-skills/convex-security-check

Provides a security audit checklist for Convex applications covering authentication, function exposure, argument validation, row-level access control, and environment variable handling. Includes code patterns for verifying user identity, protecting sensitive operations with internal functions, validating function arguments strictly, enforcing ownership checks on data mutations, and managing API keys in environment variables.

Generated from the current SKILL.md.

Does this skill check my code automatically or is it a manual checklist?
It's a manual checklist. The skill provides a structured list of security concerns to audit, along with code examples showing secure and insecure patterns in Convex functions.
Does this cover all Convex security concerns?
No. The skill focuses on five core areas: authentication, function exposure, argument validation, row-level access control, and environment variables. It does not cover rate limiting, data encryption, or network security.
Can this skill validate my existing Convex codebase?
No. The skill is instructional—it teaches patterns and provides examples. You must manually audit your code against the checklist items.
What authentication providers does this support?
The skill mentions Clerk and Auth0 as examples but does not assume a specific provider. It covers the generic pattern of checking `ctx.auth.getUserIdentity()` regardless of which provider you use.

Generated from the current SKILL.md. These answers refresh after source changes.