Skip to content
TrustedSkillsbeta
Back to all skills

Convex Security Check

Listed
waynesutton·vlatest·security·Apache-2.0

Analyzes code and infrastructure configurations for convexity vulnerabilities to proactively prevent financial exploits.

Repository

Install on your platform

This skill no longer installs under the name convex-security-check. SKILL.md frontmatter is not valid YAML, so the skills CLI skips it.

We check each listing against its upstream repository with the rules the skills CLI uses, last on 2026-10-13. We don't show a command we know will fail.

Repository install instructions

What we know about this skill

Publisher

waynesutton

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No undeclared network calls: failed

    Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: api.resend.com.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

    Hosts contacted

    api.resend.comundeclared

    What it found

    • skills/convex-security-check/SKILL.md:236contacts api.resend.com
      const response = await fetch("https://api.resend.com/emails", {

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned waynesutton/convexskills at 8ef49c9667.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
8ef49c9667
Manifest
skills/convex-security-check/SKILL.md
Scanned
2 files, 371 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The convex-security-check skill performs automated security audits on codebases, identifying vulnerabilities such as insecure dependencies, misconfigurations, and potential injection attacks. It integrates with popular code repositories and provides actionable insights to improve overall system resilience.

When to use it

  • Before deploying a new application to production
  • After updating third-party libraries or frameworks
  • During routine security assessments of existing systems
  • When onboarding new developers to review code quality

Key capabilities

  • Scans for known vulnerabilities in dependencies
  • Detects common misconfigurations in environment files
  • Identifies potential SQL injection and XSS risks
  • Integrates with CI/CD pipelines for automated checks

Example prompts

  • "Run a security audit on the latest commit of our main branch."
  • "Check for insecure dependencies in the package.json file."
  • "Identify any misconfigurations in the .env files across all environments."

Tips & gotchas

Ensure that your code repositories are accessible to the skill, and grant it appropriate permissions. While it provides strong detection capabilities, manual review is still recommended for critical systems.