make-app-service

Designs and implements Make App Service APIs, adapters, and UI-Service contracts.

5|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/qfeius/make-platform-skills --skill make-app-service-qfeius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: make-app-service
Source: https://github.com/qfeius/make-platform-skills/tree/main/skills/make-app-service
Command: npx skills add https://github.com/qfeius/make-platform-skills --skill make-app-service-qfeius

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Building a Make App backend requires consistent Service routes, correct Make gateway adapter behavior, and a documented UI-Service contract; this Skill enforces those rules so generated or refactored apps/service code stays layered, secure, and contract-compliant. ## Core Features & Use Cases - Service API contract design: Defines route shapes, response modes, and apps/docs/api.md documentation for schema, records, presets, candidates, lookup, and file proxy routes. - Make Data API adapters: Implements gateway-origin config, appKey injection, login-context forwarding, direct Make response passthrough, and AbortSignal cancellation propagation. - Schema normalization and safety: Normalizes fields and createFields independently, isolates permission-trimmed caches per principal, and enforces layered source structure with tests. - Use Case: When generating a new Make App Service, use this Skill to scaffold the layered apps/service tree, implement record CRUD and file proxy routes, and document every route in apps/docs/api.md. ## Quick Start Ask the AI to use the make-app-service skill to implement the records list and detail Service routes with Make Data API adapters and update apps/docs/api.md.

Frequently Asked Questions about make-app-service

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

FAQPage Schema
How do I implement Make App Service API routes?

Define each route in apps/docs/api.md first, then keep route handlers thin: validate input, call a Make adapter or service, and send the documented response. Use the layered tree with make-client/, services/, and utils/ folders.

How should a Service proxy Make API responses?

A direct Make proxy must preserve the upstream status, Content-Type, and body unchanged for 2xx, 4xx, and 5xx responses. Only documented non-proxy aggregation routes may normalize successful results, and they must never wrap a completed Make error.

Can the Service use makecli to fetch records at runtime?

No. Published runtime routes must call the Make gateway Data API through adapters, since online containers do not have makecli. Local preview may resolve the gateway origin via makecli configure resolve but still calls the Make API.

How are Make gateway base URLs configured?

Read MAKE_API_BASE_URL or the MAKE_SERVER_URL fallback as a strict gateway origin such as http://make-gateway.make-dev. Adapters add the service scope: /make for published runtime and /api/make only for local preview.

Why must schema fields and createFields be normalized separately?

Make Meta Schema is permission-trimmed per principal, so createFields is an independent collection. A missing createFields means an empty create collection and must never fall back to the visible fields list.

What are the boundaries of the make-app-service skill?

It owns Service routes, adapters, and contracts only. UI layout belongs to makeui, authentication to make-app-auth, permission logic to make-app-permission, build and port rules to make-app-runtime, and DSL modeling to makedsl.