taruvi-functions
Overview
Guide for authoring Taruvi serverless functions — deciding when a function is needed, which execution mode to use, how to call the injected sdk_client, and how to invoke functions from the frontend.
Compliance rule: This skill's prescribed patterns (exact function signature, SDK usage, mode selection) are mandatory. Do not invent SDK methods, skip validation, or hardcode secrets. If a requirement cannot be met, stop and ask the user.
When to Use This Skill
- Any action that touches 2 or more resources (database + storage, users + database, etc.)
- Custom backend logic beyond simple CRUD
- Reacting to data events (
RECORD_CREATE,RECORD_UPDATE,RECORD_DELETE) - Reacting to user lifecycle events (
POST_USER_CREATE,POST_USER_DELETE, etc.) - Scheduled / cron background jobs
- Calling external APIs using stored secrets
- Long-running tasks (>30s) that must not block the UI
- Public unauthenticated endpoints
- Function-to-function pipelines
- Authorization-gated operations
More from taruvi-ai/taruvi-skills
taruvi-app-developer
>
19taruvi-database
>
18taruvi-storage
>
18taruvi-refine-providers
>
18taruvi-backend-provisioning
Provision Taruvi backend resources via the Taruvi MCP server — datatables with Frictionless schemas, storage buckets, users, roles, Cerbos policies, serverless functions, analytics queries, secrets, tags, and audited raw SQL. Use when the user wants to create a datatable, add a role, write a Cerbos policy, provision a bucket, upsert schema, assign a role, register a function, run an analytics query, or otherwise change Taruvi's backend state. TRIGGERS include "Taruvi datatable", "Frictionless schema", "Cerbos policy", "manage_policies", "provision Taruvi", "upsert rows", "multi-tenant table", "Taruvi MCP tools", "create_update_schema", "delete_datatable", "execute_raw_sql". SKIP when writing Python code that runs inside a Taruvi function (use taruvi-functions) or building Refine UI (use taruvi-refine-frontend). Knows all 24 MCP tool contracts, correct invocation order, destructive-op protocol, and the Frictionless/Cerbos essentials the tools expect.
8