New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

API Spec Openapi

by fmflurry in fmflurry/settings-opencode

Generate OpenAPI 3.1 specs that follow the Zalando RESTful API Guidelines (kebab-case naming, cursor pagination, RFC 9457 problem+json errors, URL versioning, idempotency), one YAML file per bounded…

MITAuto-check passedBackend & APIs

Install API Spec Openapi

skills CLI
$ npx skills add fmflurry/settings-opencode --skill api-spec-openapi -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install fmflurry/settings-opencode api-spec-openapi --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/fmflurry/settings-opencode.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/api-spec-openapi .claude/skills/api-spec-openapi && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
api-spec-openapi
GitHub stars
171
Token cost
~3.8k tokens
SKILL.md length
681 words
Files
6
Skills in repo
20
Repo updated
First seen
Licence
MIT

At a glance

Generate OpenAPI 3.1 specs that follow the Zalando RESTful API Guidelines (kebab-case naming, cursor pagination, RFC 9457 problem+json errors, URL versioning, idempotency), one YAML file per bounded…

  • Reviewing an OpenAPI/Swagger specification
  • SKILL.md covers When to Activate, Core Rules Digest…, OpenAPI 3.1 Minimal Skeleton and Error Model: RFC 9457…, plus 2 more sections
  • Calls npx
  • Preparing specs to push to SmartBear SwaggerHub

What it does

API Spec Openapi is an agent skill from fmflurry/settings-opencode. Generate OpenAPI 3.1 specs that follow the Zalando RESTful API Guidelines (kebab-case naming, cursor pagination, RFC 9457 problem+json errors, URL versioning, idempotency), one YAML file per bounded context/domain. Use when authoring, updating, or reviewing an OpenAPI/Swagger specification, or when preparing specs to push to SmartBear SwaggerHub.

Its SKILL.md is about 3.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files (for example `bounded-context-mapping.md`, `openapi-3.1-template.md` and `problem-json.md`).

It sits in Backend & APIs, covering OpenAPI specifications. It works with OpenAPI. The repository describes itself as: Custom OpenCode settings. The licence is MIT.

When your agent uses it

  • Reviewing an OpenAPI/Swagger specification
  • Preparing specs to push to SmartBear SwaggerHub

Example prompts

  • “/api-spec-openapi”

What it can do on your machine

Read from SKILL.md and the folder at commit 0e6c33c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

API Spec Openapi loads about 3.8k tokens when it runs. Until then it costs about 91 tokens; SKILL.md has 681 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~91
When it runs · the whole SKILL.md, loaded when a task matches
~3.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from fmflurry/settings-opencode at commit 0e6c33c, republished under its MIT licence (© fmflurry). 681 words, ~3,752 tokens.

Download SKILL.mdSave it as .claude/skills/api-spec-openapi/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
api-spec-openapi
description
Generate OpenAPI 3.1 specs that follow the Zalando RESTful API Guidelines (kebab-case naming, cursor pagination, RFC 9457 problem+json errors, URL versioning, idempotency), one YAML file per bounded context/domain. Use when authoring, updating, or reviewing an OpenAPI/Swagger specification, or when preparing specs to push to SmartBear SwaggerHub.

OpenAPI 3.1 + Zalando REST API Guidelines Skill

When to Activate

  • Authoring a new OpenAPI 3.1 specification from domain models
  • Updating an existing OpenAPI spec to align with Zalando conventions
  • Reviewing specs for API naming, error handling, pagination, versioning, or idempotency compliance
  • Preparing specs for publication to SmartBear SwaggerHub
  • Designing API contracts for a bounded context or microservice

Core Rules Digest (Zalando-Derived)

The highest-value Zalando rules are embedded below. Full checklist with verifiable YAML snippets: zalando-checklist.md.

Naming
  • Paths: kebab-case, lowercase, plural resource nouns, no trailing slash.
    yaml
    /v1/users
/v1/market-searches/{id}
/v1/order-items
  • JSON properties: snake_case (not camelCase).
    yaml
    user_id: string
created_at: string
is_active: boolean
  • Identifiers MUST be English — all path segments, property names, enum values, operationIds, and schema names MUST be English (e.g., /customers/{id}/invoices, not /clients/{id}/factures). See zalando-checklist.md § English-only identifiers.
HTTP Semantics
  • GET: retrieve (200 OK or 404).
  • POST: create new resource (201 Created, Location header with URI).
  • PUT: replace entire resource, idempotent (200 or 204).
  • DELETE: remove resource, idempotent (204 No Content).
  • PATCH: partial update (not recommended; use PUT or POST instead).
  • Status codes: Use 200/201/202/204/207/400/401/403/404/409/412/422/429/500. See zalando-checklist.md § HTTP Status Codes for mappings.
Pagination (Cursor-Based, No Offset)
  • Cursor pagination: ?cursor=<opaque-value>&limit=<int> (default limit 20, max 100).
  • Forbid ?offset= and ?page= — they are inefficient at scale.
  • Response envelope includes _links.next / _links.prev for navigation.
    yaml
    items: [...]
_links:
  next: { href: "https://api.example.com/v1/users?cursor=abc123&limit=20" }
  prev: { href: "https://api.example.com/v1/users?cursor=xyz789&limit=20" }
Errors: RFC 9457 Problem+JSON
  • All 4xx/5xx responses use application/problem+json (RFC 9457 / RFC 7807).
  • Single reusable Problem schema across all endpoints.
    yaml
    type: string        # URI identifying problem type (e.g., "https://api.example.com/problems/user-not-found")
title: string       # Human-readable summary
status: integer     # HTTP status code
detail: string      # Details specific to this occurrence
instance: string    # URI to affected resource
Versioning (URL Major Only)
  • Major versions encoded in URL: /v1/, /v2/.
  • Preferred within-version evolution: Additive only (no breaking changes within /v1).
  • Alternative: Media-type versioning (content negotiation Accept: application/vnd.example.v1+json); see openapi-3.1-template.md.
  • MUST NOT break existing clients mid-version; bump major version if backward-incompatible.
Idempotency
  • POST (create): Require Idempotency-Key header (UUID or user-provided).
  • PUT / DELETE: Inherently idempotent; safe to retry.
  • Server returns same response if the same Idempotency-Key is submitted.
Filtering & Sorting
  • Filtering: Query parameters per resource (?user_id=123, ?status=active).
  • Searching: ?q=<query> for free-text search.
  • Sorting: ?sort=field,-field (ascending by default, - prefix for descending).
  • Include _links object in responses for navigation (cursor pagination, related resources, actions).
  • Standard link relations: self, next, prev, first, last.
Headers & Content Types
  • Default: application/json.
  • Errors: application/problem+json.
  • Concurrency: ETag / If-Match for optimistic locking.
  • Retry: Retry-After on 429 (rate limit) and 503 (service unavailable).
Deprecation
  • Use Deprecation: true header in responses.
  • Use Sunset header with a date when the endpoint will be removed.
  • Mark deprecated fields in schema with deprecated: true.
Show full SKILL.md (302 more words)Show less
Security
  • Define securitySchemes (e.g., OAuth2, Bearer token).
  • Apply security per operation (not globally) for granular control.
  • Never include secrets or credentials in examples or default values.
Tags (One Per Bounded Context)
  • Assign one Title-Case English tag per bounded context.
  • Group operations under their originating BC's tag for clear domain organization.
  • Example tags: "User Accounts", "Billing", "Order Fulfillment".
  • See zalando-checklist.md § Tags.
One File Per Bounded Context (or Consolidate if Needed)
  • Default: Split the API specification by domain/bounded context.
  • Naming: <bounded-context>.openapi.yaml in api-specs/ folder (kebab-case).
  • Each BC spec is independently publishable to SwaggerHub; minimize cross-file $ref.
  • Alternative: Consolidate multiple BCs into a single API file; use tags to denote BC boundaries.
  • See bounded-context-mapping.md.

OpenAPI 3.1 Minimal Skeleton

yaml
openapi: 3.1.0
info:
  title: "<Bounded Context> API"
  version: "1.0.0"
  description: |
    RESTful API for <bounded context description>.
    Follows Zalando RESTful API Guidelines and RFC 9457 for error responses.
  contact:
    name: "API Support"
    email: "api-support@example.com"
  license:
    name: "MIT"

servers:
  - url: "https://api.example.com"
    description: "Production"

tags:
  - name: "Users"
    description: "User management"
  - name: "Orders"
    description: "Order lifecycle"

paths:
  /v1/users:
    get:
      summary: "List users"
      operationId: "listUsers"
      tags: ["Users"]
      parameters:
        - $ref: "#/components/parameters/CursorParam"
        - $ref: "#/components/parameters/LimitParam"
      responses:
        "200":
          description: "Users list"
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/UserPage"
        "400":
          $ref: "#/components/responses/Problem400"
        "500":
          $ref: "#/components/responses/Problem500"
      security:
        - bearerAuth: []

    post:
      summary: "Create user"
      operationId: "createUser"
      tags: ["Users"]
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: "#/components/schemas/CreateUserRequest"
      parameters:
        - $ref: "#/components/parameters/IdempotencyKeyParam"
      responses:
        "201":
          description: "User created"
          headers:
            Location:
              schema:
                type: string
              description: "URI of created resource"
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/UserResponse"
        "400":
          $ref: "#/components/responses/Problem400"
        "409":
          $ref: "#/components/responses/Problem409"
        "422":
          $ref: "#/components/responses/Problem422"
        "500":
          $ref: "#/components/responses/Problem500"
      security:
        - bearerAuth: []

components:
  parameters:
    CursorParam:
      name: cursor
      in: query
      description: "Cursor for pagination"
      schema:
        type: string
      required: false

    LimitParam:
      name: limit
      in: query
      description: "Maximum items per page (default 20, max 100)"
      schema:
        type: integer
        minimum: 1
        maximum: 100
        default: 20
      required: false

    IdempotencyKeyParam:
      name: Idempotency-Key
      in: header
      description: "Unique key for idempotent requests (UUID)"
      schema:
        type: string
        format: uuid
      required: true

  responses:
    Problem400:
      description: "Bad Request"
      content:
        application/problem+json:
          schema:
            $ref: "#/components/schemas/Problem"

    Problem401:
      description: "Unauthorized"
      content:
        application/problem+json:
          schema:
            $ref: "#/components/schemas/Problem"

    Problem403:
      description: "Forbidden"
      content:
        application/problem+json:
          schema:
            $ref: "#/components/schemas/Problem"

    Problem404:
      description: "Not Found"
      content:
        application/problem+json:
          schema:
            $ref: "#/components/schemas/Problem"

    Problem409:
      description: "Conflict"
      content:
        application/problem+json:
          schema:
            $ref: "#/components/schemas/Problem"

    Problem422:
      description: "Unprocessable Entity"
      content:
        application/problem+json:
          schema:
            $ref: "#/components/schemas/Problem"

    Problem429:
      description: "Too Many Requests"
      content:
        application/problem+json:
          schema:
            $ref: "#/components/schemas/Problem"
      headers:
        Retry-After:
          schema:
            type: integer
          description: "Seconds to wait before retrying"

    Problem500:
      description: "Internal Server Error"
      content:
        application/problem+json:
          schema:
            $ref: "#/components/schemas/Problem"


    Problem412:
      description: "Precondition Failed"
      content:
        application/problem+json:
          schema:
            $ref: "#/components/schemas/Problem"

    Problem503:
      description: "Service Unavailable"
      headers:
        Retry-After:
          schema:
            type: integer
      content:
        application/problem+json:
          schema:
            $ref: "#/components/schemas/Problem"
  schemas:
    Problem:
      type: object
      required:
        - type
        - title
        - status
      properties:
        type:
          type: string
          description: "URI identifying problem type"
          example: "https://api.example.com/problems/user-not-found"
        title:
          type: string
          description: "Human-readable problem summary"
          example: "User Not Found"
        status:
          type: integer
          description: "HTTP status code"
          example: 404
        detail:
          type: string
          description: "Details specific to this occurrence"
          example: "User with ID 'user-123' does not exist"
        instance:
          type: string
          description: "URI to the affected resource"
          example: "https://api.example.com/v1/users/user-123"

    CursorPage:
      type: object
      required:
        - items
      properties:
        items:
          type: array
          description: "List of items"
        _links:
          type: object
          properties:
            self:
              type: object
              properties:
                href:
                  type: string
            next:
              type: object
              properties:
                href:
                  type: string
            prev:
              type: object
              properties:
                href:
                  type: string

    CreateUserRequest:
      type: object
      required:
        - email
        - name
      properties:
        email:
          type: string
          format: email
        name:
          type: string
        is_active:
          type: boolean
          default: true

    UserResponse:
      type: object
      required:
        - id
        - email
        - name
        - created_at
      properties:
        id:
          type: string
        email:
          type: string
          format: email
        name:
          type: string
        is_active:
          type: boolean
        created_at:
          type: string
          format: date-time
        updated_at:
          type: string
          format: date-time
        _links:
          type: object
          properties:
            self:
              type: object
              properties:
                href:
                  type: string

    UserPage:
      allOf:
        - $ref: "#/components/schemas/CursorPage"
        - type: object
          properties:
            items:
              type: array
              items:
                $ref: "#/components/schemas/UserResponse"

  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: "Bearer token (JWT)"

See openapi-3.1-template.md for full 3.1 idioms (JSON Schema 2020-12, examples, webhooks) and 3.0 migration notes.

Error Model: RFC 9457 Problem+JSON

Every API response with status 4xx or 5xx MUST use application/problem+json (RFC 9457 / RFC 7807). No ad-hoc error shapes.

  • Reusable Problem schema (shown above) covers all error responses.
  • Extensions: add custom fields as siblings to type, title, status, detail, instance.

See problem-json.md for full RFC 9457 model, .NET ProblemDetails mapping, and extension patterns.

Validation Gate (MUST Run Before Done)

Validators (Spectral, Redocly) MUST pass before the spec is declared done.

bash
# Spectral (recommended for Zalando ruleset)
npx @stoplight/spectral-cli lint api-specs/*.openapi.yaml --ruleset path/to/zalando-ruleset.yaml

# Redocly (OpenAPI 3.1 aware)
npx @redocly/cli lint api-specs/*.openapi.yaml

If no validator runs, report it. See validation.md for setup, fallback options, and invocation patterns.

References

Key Takeaway: Zalando specs are predictable, discoverable, and client-friendly. Kebab-case paths, snake_case JSON, cursor pagination, problem+json errors, URL versioning, and idempotency form a cohesive contract. One file per BC keeps specs independently publishable and reviewable.

© fmflurry, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files in skills/api-spec-openapi of fmflurry/settings-opencode.

  • SKILL.md
  • bounded-context-mapping.md
  • openapi-3.1-template.md
  • problem-json.md
  • validation.md
  • zalando-checklist.md

Open the folder on GitHubat commit 0e6c33c

Compare with similar skills

API Spec Openapi next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

API Spec Openapi compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
API Spec Openapi this skillfmflurry/settings-opencode171—~3.8kAutomated safety check: PassMIT
ToolJet Marketplace Plugin BuilderToolJet/ToolJet41k—~2.1kAutomated safety check: PassAGPL-3.0
Step Partsearthtojake/text-to-cad19k1 repos~1.5kAutomated safety check: PassMIT
OpenAPI to MCP Servermcp-use/mcp-use11k—~5.2kAutomated safety check: PassApache-2.0
Use Yaakmountain-loop/yaak19k—~1.9kAutomated safety check: PassMIT
API DesignerJeffallan/claude-skills12k1 repos~2kAutomated safety check: PassMIT

Similar skills

  • ToolJet Marketplace Plugin Builder

    ToolJet/ToolJet

    Turns an API description, such as an OpenAPI file or a Postman collection, into a connector plugin for ToolJet's marketplace and checks it with the repo's validator.

    41k GitHub stars~2.1k tokensUpdated today
    Backend & APIsAuto-check passed

  • Step Parts

    earthtojake/text-to-cad

    Find, evaluate, and download common purchasable CAD parts from step.parts, including named off-the-shelf actuators, servos, motors, electronics boards, connectors, screws, bolts, nuts, washers…

    19k GitHub starsUsed in 1 repo~1.5k tokens
    Backend & APIsAuto-check passed

  • OpenAPI to MCP Server

    mcp-use/mcp-use

    Turns an OpenAPI or Swagger spec into an MCP server with the mcp-use TypeScript SDK, mapping each operation to a tool, wiring auth, testing and deploying.

    11k GitHub stars~5.2k tokensUpdated today
    Backend & APIsAuto-check passed

  • Use Yaak

    mountain-loop/yaak

    A skill your agent uses when the user mentions Yaak, a Yaak workspace, or the yaak command, or asks to call, hit, or smoke test HTTP/REST endpoints, save or organize API requests for reuse or manual…

    19k GitHub stars~1.9k tokensUpdated 2 days ago
    Backend & APIsAuto-check passed

  • API Designer

    Jeffallan/claude-skills

    Designs REST and GraphQL APIs from resource modeling to an OpenAPI 3.1 contract, with versioning, pagination and RFC 7807 error handling.

    12k GitHub starsUsed in 1 repo~2k tokens
    Backend & APIsAuto-check passed

  • CLI Creator

    huangruiteng/CS-Notes

    Build a composable CLI for Codex from API docs, an OpenAPI spec, existing curl examples, an SDK, a web app, an admin tool, or a local script.

    4k GitHub starsUsed in 2 repos~2.7k tokens
    Backend & APIsAuto-check passed

More from fmflurry/settings-opencode

All 20 skills in this repo

  • Show Your Work

    fmflurry/settings-opencode

    Keep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why, evidence, result).

    171 GitHub stars~1.8k tokensUpdated 2 days ago
    Auto-check passed

  • Playwright E2E Authoring

    fmflurry/settings-opencode

    Scaffold and extend Playwright E2E tests for the gc.platform suite (tests/playwright), wiring every artifact to the real frontend (localhost:4200) + real .NET backend — never mocks.

    171 GitHub stars~2.4k tokensUpdated 2 days ago
    Auto-check passed

  • Why

    fmflurry/settings-opencode

    A skill your agent uses for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds.

    171 GitHub stars~2k tokensUpdated 2 days ago
    Auto-check passed

  • Angular Accessibility

    fmflurry/settings-opencode

    Audit and fix common accessibility issues in Angular templates and Angular Material components.

    171 GitHub stars~2.7k tokensUpdated 2 days ago
    Auto-check passed

  • Angular Clean Architecture

    fmflurry/settings-opencode

    Scaffolds and extends Angular standalone feature MODULES under src/app/modules/{name} using Clean Architecture layering (presentation/application/core/infrastructure), a self-registering module…

    171 GitHub stars~3.6k tokensUpdated 2 days ago
    Auto-check passed

  • Angular Cop

    fmflurry/settings-opencode

    Pre-merge code review for Angular + TypeScript pull requests.

    171 GitHub stars~1.4k tokensUpdated 2 days ago
    Auto-check passed

Works with

Categories

Questions about API Spec Openapi

What does API Spec Openapi do?

Generate OpenAPI 3.1 specs that follow the Zalando RESTful API Guidelines (kebab-case naming, cursor pagination, RFC 9457 problem+json errors, URL versioning, idempotency), one YAML file per bounded…. API Spec Openapi is an agent skill from fmflurry/settings-opencode.1 specs that follow the Zalando RESTful API Guidelines (kebab-case naming, cursor pagination, RFC 9457 problem+json errors, URL versioning, idempotency), one YAML file per bounded context/domain.

When should I use API Spec Openapi?

API Spec Openapi fits situations like: reviewing an OpenAPI/Swagger specification; preparing specs to push to SmartBear SwaggerHub.

How do I install API Spec Openapi in Claude Code?

Run `npx skills add fmflurry/settings-opencode --skill api-spec-openapi -a claude-code`. Or copy the skill folder (skills/api-spec-openapi in fmflurry/settings-opencode) into .claude/skills/api-spec-openapi in your project. Claude Code loads it when a task matches its description.

How do I install API Spec Openapi in Codex?

Run `npx skills add fmflurry/settings-opencode --skill api-spec-openapi -a codex`. Or copy the skill folder (skills/api-spec-openapi in fmflurry/settings-opencode) into .agents/skills/api-spec-openapi in your project. Codex loads it when a task matches its description.

Can I use API Spec Openapi in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add fmflurry/settings-opencode --skill api-spec-openapi -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/api-spec-openapi, .gemini/skills/api-spec-openapi, .github/skills/api-spec-openapi and .opencode/skills/api-spec-openapi in your project.

What does API Spec Openapi need to run?

Going by SKILL.md and its folder, API Spec Openapi needs the command-line tools its instructions call (npx).

Does API Spec Openapi access the network?

SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is API Spec Openapi safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does API Spec Openapi use?

API Spec Openapi is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does API Spec Openapi use?

About 3.8k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to API Spec Openapi?

Skills that share tags, products or a category with API Spec Openapi: ToolJet Marketplace Plugin Builder (ToolJet/ToolJet, 41k stars), Step Parts (earthtojake/text-to-cad, 19k stars), OpenAPI to MCP Server (mcp-use/mcp-use, 11k stars) and Use Yaak (mountain-loop/yaak, 19k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains API Spec Openapi?

fmflurry (a GitHub user) maintains it in fmflurry/settings-opencode, which has 171 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on October 7, 2026.

Source: fmflurry/settings-opencode on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.