How do I install the Geti Openapi Sync skill?

Run npx skillmds@latest add open-edge-platform/geti-openapi-sync in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Geti Openapi Sync safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Geti Openapi Sync?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Geti Openapi Sync free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Geti Openapi Sync?

open-edge-platform (@open-edge-platform) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Geti Openapi Sync by open-edge-platform

Name: Geti Openapi Sync
Author: open-edge-platform

Geti Openapi Sync

Regenerate and validate the OpenAPI contract between `application/backend/` and `application/ui/`. Use when backend endpoints, schemas, request or response models, or API surface change, or when `application/ui/src/api/openapi-spec.json` or `openapi-spec.d.ts` is stale. Handles backend spec generation, UI spec placement, TypeScript type regeneration, and the smallest backend and UI checks needed to confirm the contract still matches.

File contents

Geti OpenAPI Sync

Goal

Keep backend OpenAPI output and UI generated API types in sync.
Prefer regeneration over manual edits to generated JSON or .d.ts files.

Preferred Workflow

If the backend is not already running, generate the spec from application/backend/ with just gen-api-spec --output-path ../ui/src/api/openapi-spec.json on Unix-like shells, or just gen-api-spec --output-path ..\\ui\\src\\api\\openapi-spec.json on Windows.
If the backend is already running on https://localhost:7860, work from application/ui/ and run npm run update-spec (it fetches over TLS with --insecure, since the backend serves a self-signed certificate).
If only the JSON spec changed locally, run npm run build:api from application/ui/ to regenerate src/api/openapi-spec.d.ts.
Run npm run format:check and npm run type-check in application/ui/, then the narrowest backend or UI tests affected by the contract change.

When to Use Each Path

Use direct backend generation when working offline, in CI-like flows, or before the server is runnable.
Use npm run update-spec when actively iterating with a local backend server.
Use $geti-backend-dev for backend fixes if generation exposes schema problems.
Use $geti-ui-dev for UI changes that consume the regenerated types.

Guardrails

Commit the generated spec and .d.ts together when the contract change is intentional.
Do not manually edit application/ui/src/api/openapi-spec.d.ts.
If generation fails, fix the backend route or schema definitions instead of patching the generated output.

---name: geti-openapi-syncdescription: Regenerate and validate the OpenAPI contract between `application/backend/` and `application/ui/`. Use when backend endpoints, schemas, request or response models, or API surface change, or when `application/ui/src/api/openapi-spec.json` or `openapi-spec.d.ts` is stale. Handles backend spec generation, UI spec placement, TypeScript type regeneration, and the smallest backend and UI checks needed to confirm the contract still matches.---# Geti OpenAPI Sync## Goal- Keep backend OpenAPI output and UI generated API types in sync.- Prefer regeneration over manual edits to generated JSON or `.d.ts` files.## Preferred Workflow1. If the backend is not already running, generate the spec from `application/backend/` with `just gen-api-spec --output-path ../ui/src/api/openapi-spec.json` on Unix-like shells, or `just gen-api-spec --output-path ..\\ui\\src\\api\\openapi-spec.json` on Windows.2. If the backend is already running on `https://localhost:7860`, work from `application/ui/` and run `npm run update-spec` (it fetches over TLS with `--insecure`, since the backend serves a self-signed certificate).3. If only the JSON spec changed locally, run `npm run build:api` from `application/ui/` to regenerate `src/api/openapi-spec.d.ts`.4. Run `npm run format:check` and `npm run type-check` in `application/ui/`, then the narrowest backend or UI tests affected by the contract change.## When to Use Each Path- Use direct backend generation when working offline, in CI-like flows, or before the server is runnable.- Use `npm run update-spec` when actively iterating with a local backend server.- Use `$geti-backend-dev` for backend fixes if generation exposes schema problems.- Use `$geti-ui-dev` for UI changes that consume the regenerated types.## Guardrails- Commit the generated spec and `.d.ts` together when the contract change is intentional.- Do not manually edit `application/ui/src/api/openapi-spec.d.ts`.- If generation fails, fix the backend route or schema definitions instead of patching the generated output.

Frequently asked questions