my-function-api

Deploy JavaScript functions to a managed edge runtime.

83|Updated May 8, 2026
One-click install
npx skills add https://github.com/myapihq/myapi --skill my-function-api
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: my-function-api
Source: https://github.com/myapihq/myapi/tree/main/skills/my-function-api
Command: npx skills add https://github.com/myapihq/myapi --skill my-function-api

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the complexity of deploying backend functions by letting AI agents and developers publish serverless JavaScript workloads to a managed edge runtime without operating infrastructure.

Core Features & Use Cases

  • Edge Function Deployment: Register, upload, and deploy single-file JavaScript functions to the MyAPI edge runtime with live invocation URLs.
  • Secure Function Operations: Manage scoped capability keys, secrets, cron triggers, invocation history, and function lifecycle operations.
  • Use Case: Build an automated backend workflow that processes requests, runs scheduled jobs, or connects to other MyAPI capabilities through controlled permissions.

Quick Start

Ask the skill to create and deploy a JavaScript edge function that exposes an HTTP endpoint or runs on a schedule.

Frequently Asked Questions about my-function-api

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

FAQPage Schema
How do I deploy JavaScript edge functions without managing servers?

Deploying serverless JavaScript edge functions without servers requires registering and uploading a single-file bundle to a managed runtime, which provides a live invocation URL immediately after deployment.

Can I run scheduled cron jobs using serverless edge functions?

Yes, serverless edge functions support scheduled cron jobs by attaching cron triggers during function registration, enabling automated backend workflows to run at specified intervals without manual invocation.

How do I secure HTTP APIs deployed to a managed edge runtime?

Securing HTTP APIs on an edge runtime involves managing scoped capability keys and configuring secrets to control permissions, ensuring only authorized requests can trigger your deployed functions.

Does this serverless deployment approach work for automation workflows?

Yes, this serverless deployment approach works for automation workflows by connecting edge functions to other capabilities through controlled permissions, processing automated requests without operating infrastructure.

How do I monitor serverless function invocations after deployment?

Monitoring serverless function invocations involves reviewing the invocation history tracked by the managed edge runtime, allowing you to observe API request behavior and lifecycle operations post-deployment.