convex-functions

Define Convex queries, mutations, actions, and HTTP actions with validation.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/JuanQuenga/piggies-ts --skill convex-functions-juanquenga
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: convex-functions
Source: https://github.com/JuanQuenga/piggies-ts/tree/main/.agents/skills/convex-functions
Command: npx skills add https://github.com/JuanQuenga/piggies-ts --skill convex-functions-juanquenga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convex function primitives streamline building reliable serverless backends by standardizing how queries, mutations, actions, and HTTP actions are defined, validated, and executed.

Core Features & Use Cases

  • Validation-driven function signatures with explicit args and returns
  • Reactive queries, transactional mutations, actions, and HTTP actions covering common backend workflows
  • Internal functions for sensitive operations and clean separation of concerns
  • Scheduling and orchestration for asynchronous or delayed tasks
  • Clear patterns and best practices for error handling and runtime considerations

Quick Start

Create a Convex function module that declares and exports a few sample queries, mutations, and actions following the patterns shown in the unit's SKILL.md.

Frequently Asked Questions about convex-functions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are Convex functions and when should I use queries versus mutations?

Convex functions are serverless backend primitives where queries handle reactive data reads and mutations manage transactional database writes. Use queries for fetching real-time data and mutations whenever you need to modify or create records safely.

Can I use Convex actions for asynchronous workflows and external API integrations?

Yes, Convex actions orchestrate asynchronous workflows and external API integrations. They operate alongside queries and mutations to handle complex business logic, schedule delayed tasks, and communicate with third-party services.

What is the difference between internal functions and HTTP actions in a Convex backend?

Internal functions secure sensitive operations within your backend logic, while HTTP actions expose API endpoints for external requests. Both provide clean separation of concerns but serve different access and integration requirements.

Are there limitations when scheduling delayed tasks with Convex actions?

Convex actions support scheduling and orchestration for delayed tasks, but require careful runtime considerations and error handling. Ensure your asynchronous logic accounts for transactional boundaries and potential execution failures.