action-builder-skill

Create consistent Nango API wrapper actions with zod schemas and TypeScript exports.

Updated May 13, 2026
One-click install
npx skills add https://github.com/SirDannyMunn/nango-integration-templates-self-hosted --skill action-builder-skill-sirdannymunn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: action-builder-skill
Source: https://github.com/SirDannyMunn/nango-integration-templates-self-hosted/tree/main/.claude/skills/action-builder-skill
Command: npx skills add https://github.com/SirDannyMunn/nango-integration-templates-self-hosted --skill action-builder-skill-sirdannymunn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides patterns and structure for building thin API wrapper actions with Nango, ensuring consistent input/output handling and safe, repeatable integration logic.

Core Features & Use Cases

  • Thin API wrappers using createAction() to implement CRUD-like endpoints and simple integrations.
  • Enforced inline schemas with zod for strong typing and predictable validation.
  • Clear guidance on exporting action types and registration patterns (index.ts) to ensure discoverability and testability.

Quick Start

Create a new action using the provided patterns and then register it by importing it in index.ts.

Frequently Asked Questions about action-builder-skill

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

FAQPage Schema
How do I create consistent Nango action wrappers for API integrations?

Build Nango action wrappers using the createAction pattern with inline zod schemas for input validation and explicit TypeScript exports. This enforces consistent structure, type-safety, and safe execution across thin API wrapper endpoints.

What is the best way to handle input validation in TypeScript Nango actions?

The best way to handle input validation in TypeScript Nango actions is by enforcing inline zod schemas. This approach guarantees strong typing and predictable validation directly within your createAction implementation.

Why should I use inline zod schemas instead of external schema files for Nango actions?

Inline zod schemas keep action logic self-contained and ensure strong typing directly within the createAction implementation. This structure improves maintainability and guarantees predictable validation for thin API wrappers.

How do I register a new Nango action after creating it?

To register a new Nango action, import the action into your index.ts file after creating it. This export and registration pattern ensures discoverability and testability within your Nango integration project.

Does this Nango action pattern support explicit retry logic for API requests?

Yes, the Nango action pattern supports explicit retries for API requests. Using createAction allows you to define safe execution parameters, ensuring reliable integration logic when wrapping external endpoints.

When should I refactor existing Nango actions into thin API wrappers?

Refactor existing Nango actions into thin API wrappers when you need consistent input/output handling and maintainable TypeScript exports. Applying the createAction pattern with inline zod schemas ensures type-safety during endpoint additions or logic updates.