api-endpoint

Create Node.js API endpoints with service, schema, resolver, repository, and caching layers.

1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/mateo-khalil/sumate-ya --skill api-endpoint-mateo-khalil
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-endpoint
Source: https://github.com/mateo-khalil/sumate-ya/tree/main/.agents/skills/api-endpoint
Command: npx skills add https://github.com/mateo-khalil/sumate-ya --skill api-endpoint-mateo-khalil

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Backend teams frequently need to add new API endpoints with a consistent, scalable architecture spanning service, schema, resolver/controller, repository, and caching layers for Node.js backends.

Core Features & Use Cases

  • Schema/Route definition for GraphQL and REST
  • Service + Resolver/Controller + Repository scaffolding
  • Built-in caching, error handling, and validation templates to enforce best practices

Quick Start

Create a new API endpoint by following the six-step workflow and using the provided templates to scaffold service, schema, resolver, repository, and tests.

Frequently Asked Questions about api-endpoint

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

FAQPage Schema
How do I scaffold a Node.js API endpoint with proper service and repository layers?

To scaffold a Node.js API endpoint, this Skill wires together service, schema, resolver/controller, repository, and caching layers. It generates the necessary files and enforces best practices like input validation, error handling, and security checks across the architecture.

Does this scaffolding workflow support both REST and GraphQL patterns?

Yes, the scaffolding workflow explicitly supports both REST and GraphQL patterns. It applies a consistent six-step process to generate resolvers or controllers, ensuring proper schema definition and explicit field selections for your chosen API style.

What's the best way to structure caching and validation for a new backend API?

The best way to structure caching and validation is to enforce them at the service layer. This Skill provides built-in templates that apply caching at the service level and validate inputs, ensuring backend performance and safety before data reaches the repository.

Why should I separate repository and service layers when creating backend endpoints?

Separating repository and service layers when creating backend endpoints ensures scalable architecture. The service layer handles business logic, caching, and validation, while the repository layer manages data access, keeping your Node.js backend maintainable and secure.

Can I automatically generate input validation and security checks for my API routes?

Yes, you can automatically generate input validation and security checks. The Skill includes built-in templates that enforce explicit field selections and apply necessary security checks directly during the endpoint scaffolding process.

Are there limitations when wiring caching layers for Node.js services?

A limitation when wiring caching layers is that caching must be explicitly enforced at the service layer to be effective. The Skill provides templates to enforce this, but developers must ensure the caching strategy aligns with their specific data consistency requirements.