skills.rest
SirDannyMunn
SirDannyMunnCOMMUNITY
Explore all skills by this author →
GitHub

integration-patterns-skill

Enforce Nango action and sync best practices with inline schemas and index.ts registration.

Updated May 13, 2026
Search Tags:#type-safety#best-practices#nango#schemas#registration#integration-patterns
One-click install
npx skills add https://github.com/SirDannyMunn/nango-integration-templates-self-hosted --skill integration-patterns-skill-sirdannymunn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: integration-patterns-skill
Source: https://github.com/SirDannyMunn/nango-integration-templates-self-hosted/tree/main/.claude/skills/integration-patterns-skill
Command: npx skills add https://github.com/SirDannyMunn/nango-integration-templates-self-hosted --skill integration-patterns-skill-sirdannymunn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes and enforces best practices for Nango actions and syncs to ensure consistency, safety, and successful registrations across integrations.

Core Features & Use Cases

  • Pre-Flight Checks: Enforce working directory verification, relative path constraints, and consistent project layout.
  • Inline Schemas & Typing: Require inline zod schemas, explicit parameter names, null-default handling, and safe type mappings.
  • Registration & Import Hygiene: Mandate index.ts imports and clear registration patterns to ensure executables load correctly.
  • Endpoint Guidance: Promote static endpoints and documented API calls with proper doc links.

Quick Start

Add this skill to your project and import it in index.ts to activate the shared integration patterns.

Frequently Asked Questions about integration-patterns-skill

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

FAQPage Schema
How do I enforce consistent schemas and type safety for Nango actions and syncs?▼

Inline schemas standardize Nango integrations by enforcing strict parameter naming, explicit typing, and null-default handling, which prevents runtime errors and guarantees input-to-API parameter mapping consistency.

Why does my Nango integration fail to load when I register it in index.ts?▼

Nango integrations fail to load when index.ts registration imports are missing. Mandating explicit imports for every action and sync ensures executables load correctly during runtime.

What are the best practices for structuring a Nango integration project directory?▼

Best practices for Nango directories involve pre-flight working directory verification, relative path constraints, and consistent project layouts to guarantee reliable registration and execution.

How do I map input parameters to static API endpoints safely in Nango?▼

To map input parameters safely in Nango, use static endpoints and documented API calls with proper doc links, combined with explicit typing and inline schema definitions for strict parameter mapping.

Does my Nango sync need describe metadata and null-default handling to run properly?▼

Nango syncs require describe metadata and null-default handling to process data safely. These shared patterns ensure integrations execute consistently and handle missing values without failing.

What limitations are there when using shared patterns for Nango actions and syncs?▼

Shared patterns for Nango actions and syncs strictly require inline schemas, static endpoints, and index.ts registration. Deviating from these enforced structural constraints will cause the integration to fail pre-flight checks.

Related Skills

Explore More Software Engineering Skills→
salemazielsalemaziel

project-conventions

Define project directory structures, file naming conventions, and working standards.

Community
Basic
NangoHQNangoHQ
45

integration-patterns-skill

Implement Nango actions and syncs with strict schemas and explicit parameters.

Official
Advanced
NangoHQNangoHQ
45

action-builder-skill

Automate creation and refactoring of Nango integration actions in TypeScript projects.

Official
Intermediate
ultramaxoAIultramaxoAI

typed-service-contracts

Enforce end-to-end type safety for frontend-backend API contracts with Zod and TypeScript.

Official
Advanced