Convex
v1.0.0Build and maintain Convex backends with schema-safe modeling, query and mutation patterns, auth guards, and production rollout checks.
⭐ 0· 344·2 current·2 all-time
byIván@ivangdavila
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (Convex backend modeling, queries, auth, rollouts) match the instructions and supporting docs. The only declared external footprint is a local config path (~/convex/) used for project memory — this is appropriate for a developer-focused assistant that keeps project notes and checklists.
Instruction Scope
SKILL.md and auxiliary docs limit actions to reading/writing project context under ~/convex/, offering guidance on schema, indexes, auth, and rollouts. Instructions explicitly forbid storing secrets and calling external services by default. There is no instruction to read unrelated files or credentials.
Install Mechanism
Instruction-only skill with no install spec and no code files — nothing is downloaded or installed. This is the lowest-risk pattern and consistent with the described behavior.
Credentials
The skill declares no required env vars, no credentials, and only requires a config path under the user's home. Those requirements are proportional to a memory/ops playbook assistant and match the content of the SKILL.md.
Persistence & Privilege
The skill persists reusable project context to ~/convex/ (memory.md, notes). This is expected for its purpose, and always:false (not force-enabled) reduces risk. Users should be aware these files live on disk and confirm when the skill saves activation preferences or project context.
Assessment
This skill appears coherent and local-only, but before installing: (1) Confirm you're comfortable with the skill creating and writing files under ~/convex/ (it will store memory.md, notes, and playbooks). (2) Never paste secrets or raw API keys into those memory files; follow the skill's own admonition to treat secrets as user-managed. (3) Add ~/convex/ files to your .gitignore if you store code repositories nearby to avoid accidental commits. (4) Review the created files after first use to verify no sensitive data was stored and to set appropriate file permissions. (5) If you want tighter control, run the skill in an environment (VM/container) where home-directory writes are isolated.Like a lobster shell, security has layers — review code before you run it.
latestvk97ezy2w219x706cc9n7m2w2xd823q06
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
DB Clawdis
OSLinux · macOS · Windows
Config~/convex/