Run any Skill in Manus with one click

$pwd:

api-module

Name: Api Module
Author: modrinth

// Add a new API endpoint module to packages/api-client from an OpenAPI schema. Use when adding new backend endpoints, creating API client modules, or when an openapi.yml is provided.

Run Skill in Manus

$ git log --oneline --stat

stars:2,126

forks:465

updated:March 16, 2026 at 17:30

SKILL.md

readonly

name	api-module
description	Add a new API endpoint module to packages/api-client from an OpenAPI schema. Use when adding new backend endpoints, creating API client modules, or when an openapi.yml is provided.
argument-hint	<path-to-openapi.yml>

Refer to the standard: @standards/frontend/ADDING_API_MODULES.md

Steps

Read the OpenAPI schema at $ARGUMENTS — identify the endpoints, request/response shapes, and path parameters.
Read the standard above for naming conventions, type rules, and the module registration pattern.
Determine the service and version — the URL path prefix tells you which service directory and version namespace to use (e.g. /v3/projects → labrinth/v3/).
Define types in types.ts — types must match the API response 1:1. Use the OpenAPI schema as the source of truth. Do not reshape or rename fields.
Create the module class — extend BaseModule, implement each endpoint as a method. Use the correct HTTP verb and request options pattern from the standard.
Register in MODULE_REGISTRY — add the module entry so it's auto-instantiated on the client.
Export types from the service's barrel index.ts.
Verify — check that the module compiles and the types are accessible from @modrinth/api-client.

related-skills.json

same repository

cross-platform-pages.md

from "modrinth/code"

Convert a page to the cross-platform page system so it works in both the website and the desktop app. Use when moving a page into packages/ui/src/layouts/, creating shared or wrapped layouts, or setting up DI contracts for platform abstraction.

2026-04-182.1k

review-changelog.md

from "modrinth/code"

Review the latest changelog entry in packages/blog/changelog.ts against the project's changelog style guide and flag bullets that need rewriting. Use when checking a freshly added changelog entry before opening a PR, or when the user asks to review/lint the latest changelog.

2026-04-152.1k

figma-mcp.md

from "modrinth/code"

Use the Figma MCP server to translate a Figma design into a Vue page or component layout. Use when the user provides a Figma URL, asks to implement a design, or wants to draft a page layout from Figma.

2026-03-162.1k

i18n-pass.md

from "modrinth/code"

Perform an i18n localization pass on changed files or a pull request, converting hard-coded English strings to the @modrinth/ui i18n system. Use when internationalizing a set of changes, reviewing a PR for untranslated strings, or converting a specific component.

2026-03-162.1k

tanstack-query.md

from "modrinth/code"

Convert a page or component from useAsyncData/manual ref patterns to TanStack Query for server state management. Use when migrating data fetching to useQuery/useMutation, adding cache invalidation, or replacing useAsyncData with TanStack Query.

2026-03-162.1k

package.json

"author": "modrinth"

"repository": "modrinth/code"

View GitHub Repository View Creator Repositories

$ install --global

$ download --local

Run Skill in Manus

$ useful --forSOC

Software DevelopersComputer and Mathematical Occupations15-1252L4

name	api-module
description	Add a new API endpoint module to packages/api-client from an OpenAPI schema. Use when adding new backend endpoints, creating API client modules, or when an openapi.yml is provided.
argument-hint	<path-to-openapi.yml>

Refer to the standard: @standards/frontend/ADDING_API_MODULES.md

Steps

Read the OpenAPI schema at $ARGUMENTS — identify the endpoints, request/response shapes, and path parameters.
Read the standard above for naming conventions, type rules, and the module registration pattern.
Determine the service and version — the URL path prefix tells you which service directory and version namespace to use (e.g. /v3/projects → labrinth/v3/).
Define types in types.ts — types must match the API response 1:1. Use the OpenAPI schema as the source of truth. Do not reshape or rename fields.
Create the module class — extend BaseModule, implement each endpoint as a method. Use the correct HTTP verb and request options pattern from the standard.
Register in MODULE_REGISTRY — add the module entry so it's auto-instantiated on the client.
Export types from the service's barrel index.ts.
Verify — check that the module compiles and the types are accessible from @modrinth/api-client.

api-module

Steps

More from this repository

More from this repository

Steps