Skip to content
TrustedSkillsbeta
Back to all skills

Convex Http Actions

Checked
waynesutton·vlatest·backend·Apache-2.0

This skill executes HTTP requests using Convex, streamlining web interactions and enabling dynamic backend operations within your Convex apps.

Repository

Install on your platform

This skill no longer installs under the name convex-http-actions. 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 passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • 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 undeclared network calls: passed

    Makes no network calls.

    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.

  • 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-http-actions/SKILL.md
Scanned
2 files, 712 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-http-actions skill enables AI agents to perform HTTP actions such as GET, POST, PUT, and DELETE requests. It allows for seamless interaction with web services and APIs by handling request formatting, headers, authentication, and response parsing.

When to use it

  • To fetch data from a RESTful API endpoint during application initialization.
  • To submit form data or JSON payloads to a backend service for processing.
  • To update or delete records on a remote server using HTTP methods like PUT or DELETE.

Key capabilities

  • Supports common HTTP methods: GET, POST, PUT, and DELETE.
  • Handles request headers and authentication tokens.
  • Parses and returns structured response data from HTTP calls.

Example prompts

  • "Send a GET request to https://api.example.com/data and return the JSON response."
  • "POST the following JSON payload to https://api.example.com/submit: {"name": "John", "email": "[email protected]"}."
  • "Delete the resource at https://api.example.com/items/123 using a DELETE request."

Tips & gotchas

  • Ensure that any required authentication tokens or headers are included in your requests.
  • Be mindful of rate limits and API usage policies when making frequent HTTP calls.