make-app-service
Use when generating, refactoring, reviewing, or debugging Make App apps/service APIs and UI-Service contracts, including server-side aggregation for dashboards, charts and 统计/汇总. Covers route design, apps/docs/api.md, layered structure, Make adapters, direct Make response passthrough, schema normalization including independent fields/createFields collections, record CRUD, record-write-permission and records/bulk, list filter/sort/groupFilter parsing, record groups, Entity Preset, candidate/lookup/file proxies, runtime config, login-context forwarding, AbortSignal propagation, validation, logging, and tests. Always coordinate /api/make/app/principal/permission through make-app-permission. Use make-app-actions for action semantics, make-app-sort for sorting, make-app-filter for filtering, and make-app-group for grouping. Does not own UI layout, auth, permission policy, build/runtime, DSL, Make CLI deployment, or CanvasTable internals.
How do I install this agent skill?
npx skills add https://github.com/qfeius/make-platform-skills --skill make-app-serviceIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill provides comprehensive guidelines for building secure Service APIs for the Make App platform, enforcing strict data validation, credential redaction in logs, and preventing command injection by forbidding runtime shell execution.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
make-app-service
明确的业务报表、趋势、构成、排名或分析指标需求用 make-app-analytics 规划口径、固定可视化和建设规模;本 Skill 继续拥有统计链路、宿主 API 和 Make 适配器。宿主声明业务群体、日期、分母、目标及公式含义,通用编排和派生/分组序列计算复用分析包,不在每个 App 重写算法。普通初始化不因此新增分析接口/探查;PRD 已要求分析时按范围实施。现有列表 total 与临时查数沿用原流程。包发布、Skill 安装与宿主验收分别核验;列表联动的完整条件与参数能力按 筛选交接 验证,不静默扩大统计范围。
统计接入前读取 聚合查询规划:同范围兼容指标合并,重复来源复用,避免逐对象 N+1;区分必要授权复核和重复网络初始化,使用有界并发、分页及请求预算。测量真实下游调用,不能只通过增大并发/超时或缓存业务结果解决慢页。
扩展分析模板按公共合同注册,DateTime按自然日范围合同接入;制品基线归分析Skill统一维护。本Skill负责业务来源、真实范围、目标唯一匹配及执行端口;排名先取完整候选,散点/热力不按点补查,多图和明细复用同份结果。
审批对象的 bpmDefinitionKey 按 独立绑定查询合同 从 Workflow 获取;先限定当前可访问对象,再查询绑定,不读取 Schema 旧属性。保持 UI → Service → Make 的可信配置、错误透传及取消链路,失败不能降级普通创建。
应用显示名称从运行时接口归一为共享 appName,后台改名后随既有刷新更新,禁止用配置或 DSL 固定名称覆盖;见 应用名称来源。
For administrator-contact feedback, reuse the published auth namespace proxy described by make-app-auth/references/access-help.md. Preserve completed denial status/body (including reason and permissionKey), Cookie and trusted forwarded host/proto; do not gate contact help on a successful business request or add a broad gateway proxy.
Apply the shared App context contract in the existing Make client for every Service-to-Gateway call, including auth/oauth and internal callers. This transport context does not replace authentication or permission checks.
Use this skill for Make App Service API work in apps/service.
make-app-service owns the Service API contract between apps/ui and apps/service, thin Make Data API orchestration, Service route shape, Make adapter runtime config semantics, direct Make response passthrough, Service-side validation, boundary logging, and Service API tests.
It does not own record-action behavior (make-app-actions), sorting behavior (make-app-sort), filtering behavior (make-app-filter), grouping behavior (make-app-group), Make AI 助手 transport semantics (make-ai-assistant), UI layout (makeui), authentication implementation (make-app-auth), single-app permission logic (make-app-permission), runtime build/start contracts (make-app-runtime), DSL modeling (makedsl), Make CLI execution (makecli), or CanvasTable rendering/editing (canvas-table-integration).
Quick start
- Inspect
apps/docs/api.md,apps/service/src,apps/service/src/config.tsor host-equivalent config entry, existing tests, and the host project's declared data flow. - Preserve the host API contract. Update
apps/docs/api.mdbefore or with any Service route or response-shape change. - For Make Deploy's default route split, treat published browser-facing Service routes as
/api/**. Prefix-free/app/**,/auth/**, or/healthroutes may be local compatibility only; do not document them as the published UI contract unless the deploy route actually exposes them. - Classify every route before implementation. Ordinary direct Make proxies preserve completed 2xx, 4xx, and 5xx status, Content-Type, and body; file downloads also preserve Content-Disposition and stream bytes. Make AI assistant is an explicit exception for errors: apply the selected adapter's safe public-error contract below, not generic raw-error passthrough. A genuine aggregation/normalization route may define its own successful result only when
apps/docs/api.mdnames it as non-proxy; ordinary completed Make errors remain unchanged. - For a new Make POC Service, use the platform layered source tree by default:
app.ts,server.ts,config.ts,logger.ts,make-client/,services/,utils/, with tests beside the route/adapter/helper they cover. - Do not read local DSL/YAML as a published runtime data source. Runtime schema and data come from Make/backend APIs or the host Service adapter.
- Use shared adapters for Make Meta/Data/Preset calls, candidate APIs, lookup, files, and schema normalization. Build Make adapter URLs and
appKeyfrom normalized runtime config, not from route-local domains or UI input. - Implement the default single-app permission proxy through
make-app-permission, including/api/make/app/principal/permission; do not omit it from a generated or refactored Make App. - Preserve permission-trimmed Schema collections independently: normalize
fieldsandcreateFieldsseparately; missingcreateFieldsmeans an empty create collection with no fallback tofields. Preserve unknown response properties, includingeditableFields, but leave their permission semantics tomake-app-permission. - If Schema is cached, isolate permission-trimmed results by tenant, principal/session, App, and access generation, and expose explicit invalidation for permission refresh.
- For Make record actions, implement the documented
record-write-permissionroute before edit UI and therecords/bulkroute for batch edit; usemake-app-actionsfor target, permission, one-request semantics, and the established complete UI-Service response contract. Keep its success, HTTP200 partial-denial and select-all403 projections; other completed HTTP failures preserve status, Content-Type and body, including reason, permissionKey and administrator contacts, rather than a generic code/message wrapper. - For cancellable or supersedable requests, propagate a request-scoped
AbortSignalfrom the Service boundary into every downstream adapter; readreferences/service-api-contracts.mdbefore implementation. - If the Service change concerns Make AI 助手 or Agent chat, first use
make-ai-assistantfor its current official package baseline and Agent Public API v1 contract; Service owns explicit routes, validation, runtime config, safe errors, logging, cancellation and tests. - Add or update Service tests for every changed route, adapter, validation path, and error path.
- Read only the needed reference files from the map below.
Topic reference map
| Task / topic | Read |
|---|---|
| Service route shapes and UI-Service response contracts | references/service-api-contracts.md |
Request cancellation, client disconnect handling, downstream AbortSignal propagation | references/service-api-contracts.md |
| Schema 缓存刷新、进行中请求复用与取消的组合场景 | references/service-api-contracts.md、references/testing-and-safety.md |
| Service folder structure, layering, logging, errors | references/service-layering.md |
Make Data API adapter rules, schema fields / createFields, records, files, lookup, candidates | references/make-data-adapter.md |
| Dashboards, charts, counts, sums, averages, grouped statistics / 聚合统计 | Aggregate statistics |
| 多来源统计、重复接口、慢页、聚合合并、请求预算与大数据验收 | 聚合查询规划;授权元数据复用另见 复用与失效 |
| Test requirements, contract checks, safety review | references/testing-and-safety.md |
| Single-app permission proxy, Make IAM principal permission, app-scope permission payloads | Use make-app-permission |
| Auth proxy, cookies, unified login, 401/403 behavior | Use make-app-auth |
Service build output, port 3000, dist/server.js, package scripts, publish readiness | Use make-app-runtime |
| UI layout, forms, detail display, visual states | Use makeui |
| Make field/table rendering in CanvasTable | Use canvas-table-integration |
| Record sorting, sortable capabilities, Preset sort, records sort | Use make-app-sort |
| Advanced filter package behavior and Preset filter | Use make-app-filter |
| Record grouping, groupable capabilities, Preset group, record-groups, groupFilter | Use make-app-group |
| Record action precheck, strict selection target, one-request batch update | Use make-app-actions |
| Make App AI 助手、SSE、文件图片、接口域名 | Use make-ai-assistant for /api/make/app/agent/v1/** and the 25 method/path/Target combinations; Service owns their bounded authenticated proxy |
Scope boundary
make-app-servicedefines Service-owned app APIs such as schema, records, candidates, lookup options, file proxy, and thin custom orchestration.- Every new Make App Service uses
make-app-observabilityfor the default request Trace ID: validate or create it at the boundary, returnX-Log-Id, carry safe context into logs, and forward only validated trace headers to Make Gateway. This Skill owns the route and adapter implementation, whilemake-app-observabilityowns the cross-boundary invariant and audit. - It may document route names, query/body shapes, response envelopes, and adapter behavior.
- It may define Service-side Make adapter config semantics and environment variable names used by Service source, such as
MAKE_APP_KEYandMAKE_API_BASE_URL, while leaving deployment injection to runtime/operations. - It must not decide authentication implementation or OAuth/session mechanics; those belong to
make-app-auth. It may still mount and document the App Service auth proxy path required by the host contract, normally/api/make/auth/**and/api/make/oauth/**for Make Deploy Service-fronted Apps that usegatewayBaseUrl: "/api/make". - It must not define single-app permission logic, IAM permission matching, route guards, operation buttons, or field editability; those belong to
make-app-permission. It should still provide the Service layering, logging, tests, and docs needed by that permission proxy. - It must not decide build output, Service port, Docker/K8s entrypoint, package scripts, workspace manifests, or publish readiness; those belong to
make-app-runtime. - It must not define business models, entities, field meanings, relations, or DSL YAML; those belong to
makedsl. - It must not decide UI layout, component choice, Drawer layout, or CanvasTable rendering; those belong to
makeuiandcanvas-table-integration. - It must not define Make AI 助手 SSE event semantics or capability negotiation; those belong to
make-ai-assistant. The current Make App AI adapter does not carry Artifact payloads. - It must not hard-code environment-to-domain mapping. Make API base URL, gateway routing, and secret injection come from runtime config, backend/operations, or Make tooling.
Default Service responsibilities
审批新建、bpmDefinitionKey、发起/撤回、我的审批任务查询/办理/继续提交、历史和状态传输使用 make-app-approval。Service 从 Workflow 独立查询对象绑定,保留记录系统状态/锁字段;审批新建的可写字段来自权威启动配置,普通新建仍用原 createFields/IAM 合同,已有记录编辑仍用原更新链路。不要让普通源字段交集二次裁掉审批授权,也不要信任客户端声明的审批模式。BPM 源字段基础信息及任务附件类型核验使用 对应 bpm-start-config、bpm-task、bpm-process GetResource 响应的 data.formMetadata;不另请求元数据;不从普通 entity 或权限过滤的 Schema 补源字段,不覆盖普通 Schema 缓存。任务动作及其 recordPatch 走 Workflow 接口合同,不经过普通记录 PATCH 或 Lookup 关系转换;任务附件按当前节点授权预上传。保留完整上游信封、业务错误与 Trace,不把任务办理改成普通 IAM 更新。
Generated or refactored Make App Service code should provide these capabilities when the UI needs them and the host project does not already have equivalent routes:
- public health/config:
/api/health,/api/configfor published UI access;/healthmay exist as local or k8s-probe compatibility - runtime schema:
/api/make/app/schema,/api/make/app/entities/:entityKey/fields - default single-app permissions:
/api/make/app/principal/permissionthroughmake-app-permission - Agent routes when requested: use
make-ai-assistant/references/service-operations.jsonfor 23 data-plane operations plus Agent Get/List. Allowlist method/path/X-Make-Target together; exclude the other 8 control-plane operations. Standard App entry uses restricted webchat List only, without an extra management Get. - records: list, get, create, update, delete, cell update
- record actions when the list is writable: row-write permission precheck and one-request batch field update through
make-app-actions - current-user Entity Preset: get and sparse filter/sort update when filtering or sorting is enabled
- lookup options and safe lookup relation updates
- user candidates and department candidates
- file upload/delete/download proxy
- thin custom orchestration when requested, for example OCR result creation
Keep route handlers small. Put Make/backend calls in adapter modules, cross-route business orchestration in services/, and pure schema/value helpers in utils/.
Hard rules
apps/docs/api.mdis the UI-Service contract source. Do not change Service route behavior without updating it.- For Make Deploy Service-fronted Apps that use
gatewayBaseUrl: "/api/make",apps/docs/api.mdmust document published browser paths under/api/make/**, for example/api/make/auth/**,/api/make/oauth/**, and/api/make/app/**. Do not document prefix-free/app/**as the published path unless the deploy HTTPRoute exposes it. Older/apiprojects may keep/api/auth/**and/api/app/**only as an explicit legacy contract. - New generated Make POC Services and non-trivial generated/refactored
apps/servicecode must use a layered, componentized source structure instead of flat route/adapter/helper files. For new Make POC Services, default to the platform tree:app.ts,server.ts,config.ts,logger.ts,make-client/for Make/backend adapters,services/for multi-step orchestration,utils/for pure helpers, and colocated tests. - A flat
apps/service/srctree is a readiness defect for generated POC work when it mixes route registration, Make request construction, schema normalization, lookup/file orchestration, config parsing, logging, and helpers side by side. Split it before reporting the Service as complete. - Route handlers in
app.tsorroutes/only validate input, call a service/adapter, map Service-owned preflight errors, log safe boundary context, and send the documented response. Ordinary direct Make proxies preserve completed HTTP status, Content-Type, and body for 2xx, 4xx, and 5xx; the selected Make AI assistant adapter instead follows its explicit safe-error contract. Do not put raw Make payload construction, schema variant parsing, record lookup orchestration, file proxy mapping, or custom workflow steps directly into route handlers. - A UI-facing aggregation route may use a documented normalized success shape only when
apps/docs/api.mdexplicitly marks it as non-proxy. Start from the default route-response-mode table inreferences/service-api-contracts.md, then document any host-specific exception and its migration. Ordinary completed Make errors remain unchanged; the selected Make AI assistant error contract is a separately documented exception. - Service route handlers validate query/body/path params before calling Make adapters and return 400 for invalid client input.
- Service adapters own Make request details such as
appKey,X-Make-Target, Make response code checks, pagination translation, file body mapping, and consuming a prepared login/session forwarding context. Auth/session mechanics and shared forwarding helpers belong tomake-app-auth; publish/runtime proxy header contracts belong tomake-app-runtime. - Parse successes by endpoint contract. Existing auth
current-contextconsumers followmake-app-auth/references/service-fronted-mode.md#current-context-consumption; do not reuse the Meta/Data envelope parser. - Make-backed record read APIs must call Make gateway Data API through the Service Make adapter. Published runtime uses k8s-internal
/make/data/v1/record; local preview withMAKE_APP_LOCAL_PREVIEW=trueusesmakecli configure resolve --target local-preview --output=jsonfieldmake_api_originplus/api/make/data/v1/record. This applies to record list, record detail, lookup target-record reads, and any custom Service route that reads Make records. - Service Make adapters must forward the incoming request's established login context to Make gateway for Make-backed data reads and writes. At minimum, preserve the browser
Cookiesession header when the host uses cookie/unified-login auth, preserve an existingAuthorizationheader only when the host contract already uses bearer auth, and apply the host gateway context headers such asX-Forwarded-HostandX-Forwarded-Protothrough the shared auth/runtime helper. Do not invent auth policy here; usemake-app-authfor auth mechanics, but do not drop the login context before calling gateway. - Published/runtime Service APIs must never use
makeclias a data source. Do not shell out tomakecli,npx makecli, local makecli config, or makecli JSON stdout to serve schema, records, candidates, lookup options, files, or custom API data. Online Service containers do not have makecli, so runtime data must come from Make gateway/API adapters. - Make-backed Service config must read its authoritative
appKeyfrom deployment-injectedMAKE_APP_KEY; generated production code must not invent, hard-code, or let UI input override that scope. A documented protocol route may carryappKeyin its query or body only when the Service validates exact equality withMAKE_APP_KEYbefore calling an adapter. - If
MAKE_APP_KEYis missing for a Service that calls Make Meta/Data APIs, config loading must fail with a clear non-secret error before the Service is reported ready. Local test fixtures may injectMAKE_APP_KEYexplicitly. - New generated Service code reads Make adapter runtime config from
apps/service/src/config.tsor the host equivalent.MAKE_API_BASE_URLis the preferred published gateway-origin env var;MAKE_SERVER_URLis a compatibility alias only. Local preview derives its public gateway origin frommakecli configure resolve --target local-preview --output=jsoninstead of deployment env. - If neither
MAKE_API_BASE_URLnorMAKE_SERVER_URLis configured for a Make-backed Service, config loading must fail with a clear non-secret error before the Service is reported ready. - Published
MAKE_API_BASE_URL/MAKE_SERVER_URLvalues are strict k8s gateway origins such ashttp://make-gateway.make-dev. New generated Service code must not put/make,/api/make,/meta,/data,/auth, or another service path scope in this env var. Local-preview resolve output must be consumed asmake_api_origin; if older makecli fallback returns or reads a path-scoped public/api/makeAPI base, normalize that only inside the local-preview adapter. - Make platform adapters own the service path scope. Generated Service code derives upstream URLs from an explicit runtime mode: local preview uses public gateway origin +
/api/make/**; published uses k8s gateway origin +/make/**, such ashttp://make-gateway.make-dev/make/meta/**andhttp://make-gateway.make-dev/make/data/**. - Agent Service contract follows
make-ai-assistant: browser/api/make/app/agent/v1/**; preview upstreammake_api_origin + /api/make/agent/v1/**; published upstream trusted Gateway origin +/make/agent/v1/**. No new Agent-only origin or token. Validate all POST Origin, deploy-owned App scope (never concatenate unparsed CEL; use the AI Skill restricted-filter policy or a trusted AST composer), content/query/body using the publicassertAgentRequestfrom the same exact package version as the UI, as defined by the Agent Skill. Preserve{code,msg,data,pagination?}, HTTP status, extensible reason, SSE and download bytes; sanitize malformed/private diagnostics. Multipart uses POST /content, not legacy chunks. Keep auth, Trace, forwarded Host/Proto and AbortSignal on the shared request chain. - If the same Service calls other gateway services, those adapters define their own explicit service scopes from the same gateway origin. Do not strip
/makeout ofMAKE_API_BASE_URL, and do not overload a path-scoped base URL to reach unrelated services. - Service-to-gateway calls inside the cluster must not use the browser-facing
/api/makeprefix./api/make/**belongs to same-origin browser access, Service ingress, and local-preview public gateway calls; published Service internal upstream URLs use gateway-origin plus/make. - Service source must not hard-code concrete Make dev/test/prod domains, infer namespace-local gateway addresses, or map deployment environments to domains.
- Runtime Service code must not require
apps/dsl/**,/dsl/**, or copied*.yamlfiles to start or serve schema/data in published Apps. - Schema APIs normalize backend schema variants before UI sees them. Handle known variants such as
entity.properties.fields,entity.fields, or the host-documented equivalent at the Service/API boundary, and preserve fieldcapabilities.sortable/capabilities.groupablefor sorting and grouping. - Permission-trimmed Schema normalization keeps
fieldsandcreateFieldsas separate collections. Normalize each collection independently; a missing or invalidcreateFieldsbecomes[]and never falls back tofields. Normalize and preserveeditableFieldsindependently for ordinary update;make-app-permissionowns its operation and field-state intersection. Missing is empty, without falling back to visible fields. Bulk uses its own field decision. - Schema caches and in-flight reuse must not share permission-trimmed entities across principals. Key by tenant, principal/session identity, App, and access generation (or use a request-local cache), and provide an invalidation/reload path that permission refresh can call before data refresh.
- Record list and detail are separate contracts. Do not implement detail by calling list and guessing the first row when a single-record Make call exists.
- Entity Preset GET/PATCH routes must use the Make Preset
/preset/v1/entityadapter withMakeService.GetResource/MakeService.UpdateResource, preserve the established login context, and update only submitted dimensions. Usemake-app-sort,make-app-filter, andmake-app-groupfor dimension semantics. - Preset sort and records sort must share shape validation and authoritatively validate fields against current runtime schema
capabilities.sortable === true. Reject invalid, duplicate, non-sortable, or more-than-five rules before Make calls. - Sparse Preset updates must preserve sibling dimensions; saving sort must not send filter/group, saving filter must not send sort/group, and saving group must not send filter/sort.
- User and department candidates come from Service routes such as
GET /api/make/app/usersandGET /api/make/app/departmentsor the host equivalent; do not use local demo arrays in generated Service. - Ordinary Lookup option APIs must resolve target object/field from permission-aware schema metadata and return
{ options, total }. BPM START/TASK instead follows node Lookup dependencies: recheck current start-field/task authorization, resolve node metadata, its embedded relations and the current Lookup’s targetFieldKey/targetFieldType (no ordinary relation/entity/Schema fallback), and preserve target read permissions. Task candidate details follow task candidates. Do not expose full target records to selector UIs by default. - File routes proxy upload/delete/download through Service. UI should not expose raw backend file URLs when a Service download proxy is available.
- Browser resource tags such as
<img src>cannot attachAuthorization. When Make file downloads require a bearer token, keep the URL browser-facing through a Service download proxy, verify the current App session first, and let only the Service adapter attach the deployment-injected token. Do not put Make tokens or raw/data/v1/download/**URLs in UI state, public config, JSX, or logs. - Add boundary logs at route/adapter entry, success, and failure. Redact tokens, cookies, Authorization, API keys, signed download query strings, and unnecessary personal data.
- For cancellable or supersedable work, a client disconnect must abort downstream work through a request-scoped
AbortSignal. Do not stop at ignoring a stale response, and do not treat an expectedAbortErroras a user-visible 5xx failure. - Tests are required for route contracts, invalid input, adapter payloads, direct Make response status/body passthrough, and any schema/value normalization added by this skill.
- Do not report a generated or refactored Make App Service complete without the default principal permission proxy from
make-app-permissionand its required tests. - For
record-write-permissionandrecords/bulk, followmake-app-actions: precheck the complete target with one Make/data/v1/permissioncall, parse the explicit-selection HTTP 200 / business-code20000032denial and itsnoPermissionRecordIdslosslessly from the raw response before JavaScriptNumbercoercion and generic Make error mapping, keep select-all 403 denial ID-less, reuse the target for one Make/data/v1/fieldcall, and never split diagnostics or loop single-record updates.
Default route baseline
For new Service-fronted Apps, use the browser-facing routes below. Ordinary business routes share /api/make/app/**; gatewayBaseUrl: "/api/make" lets the UI call the corresponding /app/** path through its shared auth.api adapter. Public health/config stay outside this namespace. Existing Apps keep their documented equivalent routes and matching adapter without an unrelated API migration.
GET /api/health
GET /health
GET /api/config
GET /api/make/app/principal/permission
GET /api/make/app/schema
GET /api/make/app/entities/:entityKey/fields
GET /api/make/app/entities/:entityKey/preset
PATCH /api/make/app/entities/:entityKey/preset
GET /api/make/app/entities/:entityKey/records
GET /api/make/app/entities/:entityKey/records/:recordID
POST /api/make/app/entities/:entityKey/records
POST /api/make/app/entities/:objectKey/record-write-permission
POST /api/make/app/entities/:objectKey/records/bulk
PATCH /api/make/app/entities/:entityKey/records/:recordID
DELETE /api/make/app/entities/:entityKey/records/:recordID
PATCH /api/make/app/entities/:entityKey/records/:recordID/cells/:fieldKey
GET /api/make/app/users
GET /api/make/app/departments
GET /api/make/app/lookup-options
POST /api/make/app/entities/:entityKey/records/:recordID/files/:fieldKey
DELETE /api/make/app/entities/:entityKey/records/:recordID/files/:fieldKey
GET /api/make/app/files/download/*
Lookup relation update routes are optional and should be generated only when the UI needs editable lookup relationships and the Service can preserve a full qfei_relation snapshot safely.
Collaboration rules
- With
makeui: this skill provides Service contracts and normalized API shapes;makeuidecides how UI renders them. - With
make-app-permission: this skill provides Service layering and tests;make-app-permissionowns the principal permission route, IAM upstream path, App scope payload, and frontend permission contract. - With
canvas-table-integration: this skill provides schema/records/candidate APIs and owns Service-side disconnect-to-downstream cancellation; table rendering, editing UI, and browser-side virtual-page scheduling stay in the canvas skill. - With
make-app-sort: this skill implements and tests Preset/records routes and Make adapters;make-app-sortowns sortable rules, draft/save timing, and header linkage. - With
make-app-filter: this skill implements and tests Preset/records routes and Make adapters;make-app-filterowns package filter behavior, hydration, and save timing. - With
make-app-group: this skill implements and tests Preset group, record-groups, records groupFilter, and Make adapters;make-app-groupowns groupable rules, groupFilter composition, grouped data timing, and CanvasTable grouped-flow coordination. - With
make-app-actions: this skill implements and testsrecord-write-permission,records/bulk, strict target parsing, Make adapters, and error mapping;make-app-actionsowns selection intent, action timing, permission-key choice, frozen snapshots, and UI feedback. - With
make-ai-assistant: implement the 25 App route/action combinations, proxy configuration, public request validation, safe logs/errors and executable route tests; the AI Skill/package owns discovery, Agent DTOs, state, stream and attachment semantics. - With
make-app-auth: this skill may preserve Service-fronted app route shape, but auth proxy and session behavior stay in auth. - With
make-app-runtime: this skill writes Service source and tests; runtime build/start/port checks stay in runtime.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/qfeius/make-platform-skills/make-app-service">View make-app-service on skillZs</a>