CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

sec-check

Security check and audit for Convex apps and any app with a React, Vite, Next.js, or Expo frontend, built from real incidents across shipped repos. Runs a secret scanner plus a per function surface ledger, then gates every candidate finding on a real attacker path before it gets a severity. Covers leaked keys, client prefixed secrets, public functions with no auth, caller identity taken from args, paid AI and AI Gateway spend, unsigned webhooks, open uploads, unsafe HTML, prompt injection into agent tools, component boundaries, derived data that outlives its source, status moves that skip steps, unbounded reads, and CI deploy keys. Use before any deploy, before making a repo public, when adding AI, webhooks, uploads, env vars, admin features, or agent tools, when reviewing AI generated code or a PR, when checking whether a security fix worked, or when the user says sec check, security check, security audit, pen test, find vulnerabilities, verify the fix, or is this safe to ship.

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exceptionally well-built skill file: the quick-check workflow is fully sequenced with explicit validation and rerun loops, every command is copy-paste executable with flags and caveats, and all bulk material (21 rules, fix code, audit mode, probe commands) is properly deferred to real, well-signaled reference files. The only weakness is mild length in the changelog-logging step and the Resources link list, which could be tightened without losing anything.

Suggestions

Trim step 10's changelog mechanics (runs-folder options, index.md rebuild details) down to the command and the three hand-edit steps, moving storage-location details into the script's --help output.

Consolidate the six Convex doc URLs in Resources into the single docs index (https://docs.convex.dev/llms.txt) already listed, keeping only the auth and testing links that the workflow directly relies on.

DimensionReasoningScore

Conciseness

The body is dense with operational specifics ("The scanner works per file. A file that calls an auth helper anywhere passes, even if one function in it skips the check") and never explains concepts Claude already knows, but step 10's changelog mechanics ("It also rebuilds `~/sec-check-runs/index.md`, one row per repo. Set `SEC_CHECK_RUNS` or pass `--runs DIR`...") and the six Convex doc URLs in Resources could be trimmed. It is efficient with only minor over-explanation, matching anchor 4 rather than 5.

4 / 5

Actionability

Fully executable, copy-paste ready commands cover every common case: "bash <skill-dir>/scripts/sec-scan.sh . --strict", "node <skill-dir>/scripts/surface.cjs . --json", "node <skill-dir>/scripts/changelog.cjs . --mode quick --note \"one line on this run\"", plus a concrete regression-test pattern ("call the fixed function with `t.withIdentity({ subject: \"B\" })` and expect it to throw"). Not 4: commands include flags, caveats (--no-history, --strict, gitleaks install), and a complete report template with no gaps.

5 / 5

Workflow Clarity

The 9-step numbered checklist is copied into the conversation and worked top to bottom, with explicit validation checkpoints and feedback loops: "Repeat until the scanner exits 0 and every ledger `open` row is fixed", "Before merging, say what breaks if the fix is wrong and how to roll back", and a 17-item pre-ship gate checklist. The destructive/batch validation cap does not apply because verification (step 8 rerun, verify-a-fix verdicts, tsc typecheck) is explicit throughout. Not 4: both the sequence and its checkpoints are fully explicit, including error-recovery guidance for inconclusive verdicts.

5 / 5

Progressive Disclosure

The main file is a clear overview with well-signaled one-level-deep references that all exist on disk: "Read the full rule in [references/rules.md](references/rules.md) before you fix or reject a finding", "Apply the matching rule from [references/rules.md] and the code in [references/patterns.md]", with rules.md (303 lines), patterns.md (945 lines), audit.md, and probe.md holding the bulk detail and deep-link anchors (#11, #13, #18, #19) verified present. Not 4: all four references and three scripts are real, clearly signaled with what each contains, and content is appropriately split — nothing that belongs in a reference is inlined in the main file.

5 / 5

Total

19

/

20

Passed

Description

96%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A model description: it states a concrete three-stage pipeline in third person, enumerates fourteen specific finding classes, and gives an explicit 'Use when' clause saturated with natural trigger phrases and synonyms. The only soft spot is that its generic security triggers (pen test, security audit, find vulnerabilities) overlap with any general security-review skill, slightly raising conflict risk.

DimensionReasoningScore

Specificity

Multiple concrete actions are stated in third person ("Runs a secret scanner plus a per function surface ledger, then gates every candidate finding on a real attacker path before it gets a severity") with comprehensive coverage of finding types ("leaked keys, client prefixed secrets, public functions with no auth, caller identity taken from args, paid AI and AI Gateway spend, unsigned webhooks, open uploads..."). Not 4: the pipeline (scan, ledger, gate, severity) plus a fourteen-item coverage list leaves no meaningful gaps.

5 / 5

Completeness

Both what and when are explicitly answered: the what is the scanner-plus-ledger-plus-gate pipeline with an enumerated coverage list, and the when is fully explicit ("Use before any deploy, before making a repo public... or when the user says sec check, security check, security audit..."). Not 4: the when clause is explicit and concrete rather than implied or generic.

5 / 5

Trigger Term Quality

Comprehensive natural-language triggers with synonyms: "when the user says sec check, security check, security audit, pen test, find vulnerabilities, verify the fix, or is this safe to ship", plus situational triggers ("before any deploy, before making a repo public, when adding AI, webhooks, uploads, env vars, admin features, or agent tools"). Not 4: these are exactly the phrases a user would naturally say when they need this skill, with both synonyms and situation-based variants covered.

5 / 5

Distinctiveness Conflict Risk

The niche is clear ("Security check and audit for Convex apps and any app with a React, Vite, Next.js, or Expo frontend") and the "sec check" phrasing is distinctive, but generic triggers like "security audit", "pen test", and "find vulnerabilities" would also naturally fire a general security-review skill, and the frontend scope is broad. Mostly distinct with minor overlap risk against closely related security skills, matching anchor 4 rather than 5; not 3 because the Convex/frontend stack scoping keeps it clearly distinguishable.

4 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

waynesutton/convexskills

Path

skills/sec-check/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.