원클릭으로 Manus에서 모든 스킬 실행

formio-api

스타6

포크3

업데이트2026년 7월 22일 17:29

Comprehensive Form.io API reference — every endpoint in the Form.io API Postman collection across platform admin, project admin, runtime/end-user, and PDF scopes. Use when the user asks to call, script, inspect, or document any Form.io REST endpoint: platform/project auth; projects, stages, tenants, teams; forms, resources, and revisions (create, list, update, import, export); actions; roles; end-user registration and login; submissions (submit, query, patch, delete); aggregation reports; PDF template uploads and submission downloads; health/status. Also for x-jwt-token auth questions and the base URL vs project URL distinction. Not for: building a whole application around Form.io (see formio-application); planning a data model (see formio-resource-planner); authoring Form.io JSON schemas (see formio-schema); calling the JavaScript SDK — `Formio.*` statics, `new Formio(...)` instances, `Utils.*` helpers (see formio-sdk).

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

formio

formio/ai

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Form.io API Skills

Single entry point for the full Form.io REST API surface. Detailed endpoint references live under ./references/ — one file per capability group.

Terminology

Two distinct endpoints exist. These references NEVER conflate them:

baseUrl / base_url → platform deployment endpoint → FORMIO_BASE_URL (the Postman {{baseUrl}} variable when used bare, without {{projectName}})
projectUrl / {{baseUrl}}/{{projectName}} → project endpoint → FORMIO_PROJECT_URL (a separate environment variable — not a computed sub-path)

Authentication

All endpoints (except Server API health/status) require an x-jwt-token header populated by the MCP server's browser-based portal-login flow. The MCP server attaches this header automatically via formioFetch. See references/runtime-auth.md or references/platform-auth.md for details.

MCP Tool Preference

Prefer first-party MCP tools (form_create, form_get, form_list, form_update, role_create, role_list, role_update, project_export, project_import) over raw HTTP when both paths exist. Each reference doc surfaces the preferred tool alongside its HTTP fallback in a mapping table. Authentication is implicit — any authenticated tool call triggers the portal-login flow on first use.

Scope map

Platform scope — `${FORMIO_BASE_URL}/`

platform-auth — platform-admin login, portal users, identity providers
platform-projects — project CRUD, export, import
platform-teams — teams, membership, project access
platform-staging — stages, version tagging, cross-stage deploys
platform-tenants — multi-tenant projects and tenant admins
server-status — liveness, health, version diagnostics

Project scope — `${FORMIO_PROJECT_URL}/`

project-auth — project-admin login, admin resource
project-roles — role CRUD
project-forms — form/resource CRUD, import, export
project-form-revisions — revision enablement, drafts, publish
project-actions — form action CRUD (email, webhook, role-assignment, etc.)

Runtime scope — `${FORMIO_PROJECT_URL}/`

runtime-auth — end-user registration and login on the built-in user resource
runtime-custom-users — custom user resources, custom roles, Login/Role-Assignment actions
runtime-access-control — "own" submission access, group permissions
runtime-reports — aggregation pipelines across submissions
runtime-submissions — submission CRUD, validate, patch, revisions

PDF scope — `${FORMIO_PROJECT_URL}/pdf-proxy/`

pdf-api — PDF template upload, PDF-backed forms, submission-to-PDF download

How to use this skill

When the user asks an API-oriented question, identify the scope (platform / project / runtime / PDF) and open the matching reference file under ./references/. Each reference documents:

Endpoints (method + path relative to the scope's root URL)
Request / response shapes
Related reference docs
MCP-tool mapping (where a first-party tool covers the operation)

Do not merge content across scopes — each reference names its own base URL and endpoint set.

이 저장소의 다른 Skills

같은 저장소

formio-actions

formio/ai

Deep reference for configuring Form.io actions — the server-side behavior layer that powers email notifications, authentication, webhooks, role assignment, and form-to-form saves. Use this skill whenever the user wants to add, configure, or troubleshoot an action on a form, choose the right action type for a use case, understand the action execution lifecycle, set up conditions or handler/method combinations, or wire up authentication flows. Also use when the user mentions action settings, action priorities, action conditions, email actions, login actions, webhook actions, role actions, save actions, or reset password actions — even if they don't say "action" explicitly (e.g., "send an email when someone submits", "add login to this form", "assign a role after registration"). Not for: auth architecture — SSO (OIDC/OAuth/SAML/LDAP), Token Swap, Custom JWT, JWT/session mechanics, 2FA, or RBAC tuning (see `formio-auth`); REST endpoint lookups (see `formio-api`).

2026-07-226

formio-angular-resources

formio/ai

Angular-explicit extension sub-skill for the Form.io skill library — adds, regenerates, or repairs one resource NgModule in an Angular workspace that already has `FormioAppConfig` wired into `AppModule`. Invoked either (a) via framework-explicit user phrasing that names Angular, or (b) via handoff from the parent `formio-angular` skill (which itself may have been invoked by `formio-application`). Claims ONLY Angular-explicit triggers — phrases that name Angular or `@formio/angular` verbatim. Example triggers this skill claims include "add an Angular module for X", "regenerate the Angular `Participant` resource module", "in my Angular app, wire `X`'s children to `Y`", "fix the Angular `ViewComponent` for `Orders`", "the Angular `Event` module is missing a route", "add a bidirectional Angular join between `Team` and `User`", and "regenerate the `FormioResourceRoutes()` for the Angular CRM app". Does NOT claim framework-agnostic extension phrasing (those route through `formio-application`, which decides whether

2026-07-226

formio-angular

formio/ai

Angular framework implementor for the Form.io skill library — turns an approved `template.json` plus a target Form.io project into a working Angular application using `@formio/angular`, via a five-phase gated flow (setup, bootstrap, config, auth, resources). Invoked as the handoff from `formio-application`, or directly when the user explicitly names Angular. Claims ONLY Angular-explicit triggers. Use when the user says "build it in Angular", "Angular front-end for this Form.io project", "use Angular", "use `@formio/angular`", "the Angular skill", or "wire up `FormioAppConfig`". Not for: framework-agnostic app requests (see `formio-application`); extending a running Angular app — which loads the nested `formio-angular-resources` sub-skill at `./resources/SKILL.md` (not a top-level skill); planning a data model (see `formio-resource-planner`); framework-agnostic embed/render-a-form requests (see `formio-form`); REST endpoint lookups (see `formio-api`).

2026-07-226

formio-application

formio/ai

Default "build me an app" orchestrator — builds a new application backed by a Form.io project from a plain-language idea, or extends an existing app with a new feature; the user never needs framework or Form.io terminology. The flow writes a `.mcp.json` in the workspace root and pauses for a Claude Code restart after that write. Use whenever the user wants to build, create, spin up, or stand up an app, tool, portal, dashboard, or tracker around data — "build me an app", "create a CRM", bare archetypes ("task manager", "help desk") — or extend one: "also track X", "add a way to see Y". Not for: Angular-explicit builds (see `formio-angular`) or extensions (see `formio-angular-resources`); planning a data model without building an app (see `formio-resource-planner`); embedding or rendering an existing form in a page — "embed this form" (see `formio-form`); creating a standalone single form (no data model or app around it — see `formio-form-builder`); REST endpoint lookups (see `formio-api`).

2026-07-226

formio-auth

formio/ai

Form.io authentication and authorization specialist — resource-backed login (Login plus Role Assignment Actions), role-based access control and group permissions, SSO via OIDC/OAuth/SAML/LDAP with provider role mapping, Token Swap, Custom JWT for Enterprise/on-prem (signed with `JWT_SECRET`), email-token (passwordless) auth, and JWT/session mechanics (the `x-jwt-token` header, `jti` Session ID, logout, 2FA, reCAPTCHA). Use when the user asks to configure how users authenticate — SSO, OIDC, OAuth, SAML, LDAP, Token Swap, Custom JWT, passwordless auth, JWT, sessions, roles, permissions, RBAC, group permissions, 2FA, or reCAPTCHA in Form.io. Not for: designing the resource map or data model (see `formio-resource-planner`); orchestrating an app build (see `formio-application`); adding a Login or Role Assignment Action to one form — per-form action settings, priorities, conditions (see `formio-actions`); REST endpoint lookups (see `formio-api`); wiring a login screen into Angular (see `formio-angular`).

2026-07-226

formio-form-builder

formio/ai

Default "build me a form" orchestrator — builds a single Form.io form end to end: determines the form type (webform, wizard, or PDF form), delegates schema authoring to `formio-schema`, saves the form via the MCP server, and optionally hands off to embedding. Use when the user asks to "build a form", "create a form", make a "multi-page form", or create a "survey", "contact form", "intake form", "registration form", "questionnaire", or "pdf form" — or to edit an existing form's fields: "add a phone field to my registration form". Boundary: "build a form to collect X" (a standalone form) belongs to this skill; "track X / manage X / build an app around X" (a data model, CRUD, resources) belongs to `formio-application` / `formio-resource-planner`. Not for: embedding an EXISTING form (see `formio-form`); building an app (see `formio-application`); designing resources or permissions (see `formio-resource-planner`); raw JSON schema lookups (see `formio-schema`); REST endpoint lookups (see `formio-api`).

2026-07-226

name

formio-api

description

Form.io API Skills

Single entry point for the full Form.io REST API surface. Detailed endpoint references live under ./references/ — one file per capability group.

Terminology

Two distinct endpoints exist. These references NEVER conflate them:

baseUrl / base_url → platform deployment endpoint → FORMIO_BASE_URL (the Postman {{baseUrl}} variable when used bare, without {{projectName}})
projectUrl / {{baseUrl}}/{{projectName}} → project endpoint → FORMIO_PROJECT_URL (a separate environment variable — not a computed sub-path)

Authentication

MCP Tool Preference

Scope map

Platform scope — `${FORMIO_BASE_URL}/`

platform-auth — platform-admin login, portal users, identity providers
platform-projects — project CRUD, export, import
platform-teams — teams, membership, project access
platform-staging — stages, version tagging, cross-stage deploys
platform-tenants — multi-tenant projects and tenant admins
server-status — liveness, health, version diagnostics

Project scope — `${FORMIO_PROJECT_URL}/`

project-auth — project-admin login, admin resource
project-roles — role CRUD
project-forms — form/resource CRUD, import, export
project-form-revisions — revision enablement, drafts, publish
project-actions — form action CRUD (email, webhook, role-assignment, etc.)

Runtime scope — `${FORMIO_PROJECT_URL}/`

runtime-auth — end-user registration and login on the built-in user resource
runtime-custom-users — custom user resources, custom roles, Login/Role-Assignment actions
runtime-access-control — "own" submission access, group permissions
runtime-reports — aggregation pipelines across submissions
runtime-submissions — submission CRUD, validate, patch, revisions

PDF scope — `${FORMIO_PROJECT_URL}/pdf-proxy/`

pdf-api — PDF template upload, PDF-backed forms, submission-to-PDF download

How to use this skill

When the user asks an API-oriented question, identify the scope (platform / project / runtime / PDF) and open the matching reference file under ./references/. Each reference documents:

Endpoints (method + path relative to the scope's root URL)
Request / response shapes
Related reference docs
MCP-tool mapping (where a first-party tool covers the operation)

Do not merge content across scopes — each reference names its own base URL and endpoint set.

formio-api

Form.io API Skills

Terminology

Authentication

MCP Tool Preference

Scope map

Platform scope — ${FORMIO_BASE_URL}/

Project scope — ${FORMIO_PROJECT_URL}/

Runtime scope — ${FORMIO_PROJECT_URL}/

PDF scope — ${FORMIO_PROJECT_URL}/pdf-proxy/

How to use this skill

이 저장소의 다른 Skills

이 저장소의 다른 Skills

Form.io API Skills

Terminology

Authentication

MCP Tool Preference

Scope map

Platform scope — ${FORMIO_BASE_URL}/

Project scope — ${FORMIO_PROJECT_URL}/

Runtime scope — ${FORMIO_PROJECT_URL}/

PDF scope — ${FORMIO_PROJECT_URL}/pdf-proxy/

How to use this skill

Platform scope — `${FORMIO_BASE_URL}/`

Project scope — `${FORMIO_PROJECT_URL}/`

Runtime scope — `${FORMIO_PROJECT_URL}/`

PDF scope — `${FORMIO_PROJECT_URL}/pdf-proxy/`

Platform scope — `${FORMIO_BASE_URL}/`

Project scope — `${FORMIO_PROJECT_URL}/`

Runtime scope — `${FORMIO_PROJECT_URL}/`

PDF scope — `${FORMIO_PROJECT_URL}/pdf-proxy/`