integration-endpoint

Integrate external-facing routes into the Integration API with TypeScript and Zod schemas.

1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/jaaroncara/NH-RAG-Memory-Engine --skill integration-endpoint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: integration-endpoint
Source: https://github.com/jaaroncara/NH-RAG-Memory-Engine/tree/main/.claude/skills/integration-endpoint
Command: npx skills add https://github.com/jaaroncara/NH-RAG-Memory-Engine --skill integration-endpoint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Integration API requires a standardized pattern to add new externally-facing routes with consistent authentication, routing, and provenance tracking. This Skill provides a clean template for wiring a TypeScript service wrapper, Zod schemas, and metadata enrichment to ensure predictable behavior across endpoints.

Core Features & Use Cases

  • Securely exposes new integration routes under the configured base path with timing-safe authentication mechanisms.
  • Includes a TypeScript service wrapper, Zod request schemas, and provenance metadata helpers to align with frontend and internal tooling.
  • Use cases include partner integrations, internal automation, and external service extensions.

Quick Start

Configure and invoke the new integration endpoint in a local dev environment to validate route wiring and authentication.

Frequently Asked Questions about integration-endpoint

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

FAQPage Schema
How do I add a new external API route with standardized authentication and metadata?

To add an external API route with standardized authentication, this Skill wires a TypeScript service wrapper, Zod schemas, and provenance metadata helpers to ensure predictable routing and timing-safe auth across endpoints.

What is the best way to standardize provenance tracking across multiple integration routes?

Standardizing provenance tracking across integration routes requires applying metadata enrichment helpers to your TypeScript service wrapper, ensuring consistent observability and predictable behavior for partner-facing endpoints.

Do I need Zod schemas to validate requests for partner-facing integration endpoints?

Yes, Zod schemas are required to validate incoming requests for partner-facing integration endpoints, pairing with the TypeScript service wrapper to enforce standardized routing and secure data handling.

How does timing-safe authentication work for external API integrations?

Timing-safe authentication for external API integrations works by applying secure verification mechanisms within the service wrapper, preventing timing attacks while standardizing access control across all configured base paths.

Can I use this integration endpoint pattern for internal automation and service extensions?

Yes, you can use this integration endpoint pattern for internal automation and external service extensions, as it standardizes error handling, routing, and metadata enrichment for both partner and internal workflows.

What are the limitations of building partner integrations without standardized routing and error handling?

Building partner integrations without standardized routing and error handling leads to unpredictable behavior and security gaps; this Skill mitigates those limitations by enforcing Zod schemas and provenance metadata across all external routes.