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

701 Technologies Openapi

by jabrena in jabrena/plinth

A skill your agent uses when you need framework-agnostic OpenAPI 3.x guidance — spec structure, metadata and versioning, paths and operations, reusable schemas, security schemes, examples…

Apache-2.0Auto-check passedBackend & APIs

Install 701 Technologies Openapi

skills CLI
$ npx skills add jabrena/plinth --skill 701-technologies-openapi -a claude-code

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

GitHub CLI
$ gh skill install jabrena/plinth 701-technologies-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/jabrena/plinth.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/701-technologies-openapi .claude/skills/701-technologies-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
701-technologies-openapi
GitHub stars
446
Used in
1 other repo
Token cost
~870 tokens
SKILL.md length
359 words
Files
2 (incl. references)
Skills in repo
124
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when you need framework-agnostic OpenAPI 3.x guidance — spec structure, metadata and versioning, paths and operations, reusable schemas, security schemes, examples…

  • You need framework-agnostic OpenAPI 3.x guidance — spec structure
  • SKILL.md covers Constraints, When to use this skill, Workflow and Reference
  • Calls mvn
  • Metadata and versioning

What it does

701 Technologies Openapi is an agent skill from jabrena/plinth. Use when you need framework-agnostic OpenAPI 3.x guidance — spec structure, metadata and versioning, paths and operations, reusable schemas, security schemes, examples, documentation quality, contract validation (e.g. Spectral), breaking-change awareness, and handoffs to codegen — without choosing Spring Boot, Quarkus, or Micronaut. This should trigger for requests such as Review an OpenAPI; Improve an OpenAPI; Improve API contract; Improve API schema design. Part of Plinth Toolkit

Its SKILL.md is about 870 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/701-technologies-openapi.md`).

It sits in Backend & APIs, covering OpenAPI specifications. It works with OpenAPI and Spring Boot. The repository describes itself as: Plinth is an AI-native engineering toolkit for modern Java enterprise SDLC, built around reusable Commands, Agents, Skills, and MCP Servers. The licence is Apache-2.0.

When your agent uses it

  • You need framework-agnostic OpenAPI 3.x guidance — spec structure
  • Metadata and versioning
  • Paths and operations
  • Reusable schemas

Example prompts

  • “/701-technologies-openapi”

What it can do on your machine

Read from SKILL.md and the folder at commit dca88dc. 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:

    • mvn

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

  • Network

    No URLs in SKILL.md.

    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

701 Technologies Openapi loads about 870 tokens when it runs, and up to ~5.4k if it reads all its reference files. Until then it costs about 128 tokens; SKILL.md has 359 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~128
When it runs · the whole SKILL.md, loaded when a task matches
~870
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.4k

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 jabrena/plinth at commit dca88dc, republished under its Apache-2.0 licence (© jabrena). 359 words, ~870 tokens.

Download SKILL.mdSave it as .claude/skills/701-technologies-openapi/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
701-technologies-openapi
description
Use when you need framework-agnostic OpenAPI 3.x guidance — spec structure, metadata and versioning, paths and operations, reusable schemas, security schemes, examples, documentation quality, contract validation (e.g. Spectral), breaking-change awareness, and handoffs to codegen — without choosing Spring Boot, Quarkus, or Micronaut. This should trigger for requests such as Review an OpenAPI; Improve an OpenAPI; Improve API contract; Improve API schema design. Part of Plinth Toolkit
license
Apache-2.0
metadata.author
Juan Antonio Breña Moral
metadata.version
0.19.0

OpenAPI 3.x best practices

Help teams produce maintainable OpenAPI 3.x contracts that stay aligned with HTTP semantics and consumer needs.

What is covered in this Skill?

  • Document structure: openapi, info, servers, tags, and consistent resource grouping
  • Path and operation design: parameters, request bodies, response matrices, operationId, status codes
  • Reusable components (schemas, parameters, responses, security schemes) and examples
  • Validation and CI: spec linting, breaking-change checks, pre-codegen gates
  • Security modeling in the contract (schemes, scopes, global vs operation security)
  • Clear boundaries between contract-first design and runtime implementation concerns

Scope: Contract-first quality only. Focus this skill on OpenAPI design, quality, and governance guidance.

Constraints

Keep recommendations at the OpenAPI layer unless the user explicitly asks for Java framework integration. After editing this repository's XML sources, regenerate skills and verify the build.

  • MANDATORY: Run ./mvnw compile or mvn compile before proposing Java or Maven changes in the same change set
  • FRAMEWORK: Keep guidance contract-centric; do not prescribe framework-specific controller wiring or runtime exposure details
  • FUZZING: Keep fuzzing guidance high-level and contract-focused without linking to external skill identifiers
  • VERIFY: Run ./mvnw clean verify or mvn clean verify before promoting changes
  • EDGE CASE: If the user goal is ambiguous, stop and ask a clarifying question before editing files or running project-wide commands
  • EDGE CASE: If required context, files, credentials, or tools are missing, report the blocker explicitly and ask whether to proceed with setup or fallback guidance
  • EDGE CASE: If requested changes conflict with project constraints or safety boundaries, explain the conflict and ask for user confirmation on the preferred trade-off
Show full SKILL.md (104 more words)Show less

When to use this skill

  • Review an OpenAPI
  • Improve an OpenAPI
  • Improve API contract
  • Improve API schema design
  • Validate an OpenAPI spec

Workflow

  1. Read reference and assess project context

Read references/701-technologies-openapi.md and inspect current API/context artifacts before proposing changes.

  1. Gather scope and decide target improvements

Identify requested outcomes, constraints, and the minimum safe set of changes to apply.

  1. Apply technology-aligned changes

Implement or refactor artifacts following the reference patterns and project conventions.

  1. Run verification and report results

Execute appropriate checks and summarize what changed, what was verified, and any follow-up actions.

Reference

For detailed guidance, examples, and constraints, see references/701-technologies-openapi.md.

© jabrena, Apache-2.0. 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 1 other file (references) in skills/701-technologies-openapi of jabrena/plinth.

  • SKILL.md
  • references/701-technologies-openapi.md

Open the folder on GitHubat commit dca88dc

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in jabrena/plinth, which our catalogue first saw on October 7, 2026.

Compare with similar skills

701 Technologies 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.

701 Technologies Openapi compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
701 Technologies Openapi this skilljabrena/plinth4461 repos~870Automated safety check: PassApache-2.0
Oryxos Initoryx-labs/oryxos186—~1.6kAutomated safety check: PassApache-2.0
Openapi Firstrrezartprebreza/spring-boot-skills2981 repos~1.3kAutomated safety check: PassMIT
Springboot Init Skilljiushiwon/wg-skills112—~2.2kAutomated safety check: NotesApache-2.0
Spring Boot Openapi Documentationgiuseppe-trisciuoglio/developer-kit3551 repos~2.6kAutomated safety check: NotesMIT
Detecting Debug Endpointsjeremylongshore/tons-of-skills-marketplace2.8k—~2kAutomated safety check: PassMIT

Similar skills

  • Oryxos Init

    oryx-labs/oryxos

    初始化 OryxOS（或同类 JDK 21 + Spring Boot 3.x 企业级单体）的工程地基：Maven 多模块骨架、 结构化日志、Actuator + Prometheus 监控、Spring MVC + 虚拟线程、springdoc OpenAPI、 统一响应体与全局异常/错误码、Google 格式 + 阿里编码规约（Spotless + 阿里 P3C +…

    186 GitHub stars~1.6k tokensUpdated today
    Backend & APIsAuto-check passed

  • Openapi First

    rrezartprebreza/spring-boot-skills

    A skill your agent uses when the project follows API-first / OpenAPI-first approach: generating controller interfaces, DTOs, and clients from an OpenAPI spec.

    298 GitHub starsUsed in 1 repo~1.3k tokens
    Backend & APIsAuto-check passed

  • Springboot Init Skill

    jiushiwon/wg-skills

    Spring Boot 项目一键初始化技能。面向零基础小白，提供环境探测、自动安装、完整 Web 骨架生成、SSE 流式框架、JWT 鉴权、统一响应封装、文件上传接口、一键启动/重启脚本、Swagger 文档，内置 MySQL（默认）/ PostgreSQL / MongoDB 数据库选择。用户只需说"帮我搭一个 Spring Boot…

    112 GitHub stars~2.2k tokensUpdated yesterday
    Backend & APIsAuto-check: notes

  • Spring Boot Openapi Documentation

    giuseppe-trisciuoglio/developer-kit

    Provides patterns to generate comprehensive REST API documentation using SpringDoc OpenAPI 3.0 and Swagger UI in Spring Boot 3.x applications.

    355 GitHub starsUsed in 1 repo~2.6k tokens
    Backend & APIsAuto-check: notes

  • Detecting Debug Endpoints

    jeremylongshore/tons-of-skills-marketplace

    Probe a target for accidentally-public admin / debug / introspection endpoints — Spring Boot Actuator, Apache server-status, Prometheus metrics, GraphQL playground, Swagger UI, phpMyAdmin…

    2.8k GitHub stars~2k tokensUpdated today
    Backend & APIsAuto-check passed

  • 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

More from jabrena/plinth

All 124 skills in this repo

  • 703 Technologies Fuzzing Testing

    jabrena/plinth

    A skill your agent uses when you need to add or review fuzz testing for Java APIs with CATS — including contract-driven negative testing, malformed payload validation, boundary input exploration, CI…

    446 GitHub stars~874 tokensUpdated today
    Auto-check passed

  • 033 Architecture Diagrams

    jabrena/plinth

    A skill your agent uses when you need to generate Java project diagrams — including UML sequence diagrams, UML class diagrams, C4 model diagrams, UML state machine diagrams, UML Deployment Diagrams…

    446 GitHub stars~3.1k tokensUpdated today
    Auto-check passed

  • 112 Java Maven Plugins

    jabrena/plinth

    A skill your agent uses when you need to add or configure Maven plugins in your pom.xml — including quality tools (enforcer, surefire, failsafe, jacoco, pitest, spotbugs, pmd), security scanning…

    446 GitHub stars~3.2k tokensUpdated today
    Auto-check passed

  • 151 Java Performance Jmeter

    jabrena/plinth

    A skill your agent uses when you need to set up JMeter performance testing for a Java project — including creating the run-jmeter.sh script from the exact template, configuring load tests with…

    446 GitHub stars~842 tokensUpdated today
    Auto-check passed

  • 161 Java Profiling Detect

    jabrena/plinth

    A skill your agent uses when you need to set up Java application profiling to detect and measure performance issues — including trusted preinstalled async-profiler v4.x setup, problem-driven…

    446 GitHub stars~903 tokensUpdated today
    Auto-check passed

  • 001 Commands Inventory

    jabrena/plinth

    A skill your agent uses when you need to generate a checklist document with embedded commands inventory, following the embedded template exactly and producing INVENTORY-COMMANDS-JAVA.md in the…

    446 GitHub stars~697 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about 701 Technologies Openapi

What does 701 Technologies Openapi do?

A skill your agent uses when you need framework-agnostic OpenAPI 3.x guidance — spec structure, metadata and versioning, paths and operations, reusable schemas, security schemes, examples…. 701 Technologies Openapi is an agent skill from jabrena/plinth.g.

When should I use 701 Technologies Openapi?

701 Technologies Openapi fits situations like: you need framework-agnostic OpenAPI 3.x guidance — spec structure; metadata and versioning; paths and operations; reusable schemas.

How do I install 701 Technologies Openapi in Claude Code?

Run `npx skills add jabrena/plinth --skill 701-technologies-openapi -a claude-code`. Or copy the skill folder (skills/701-technologies-openapi in jabrena/plinth) into .claude/skills/701-technologies-openapi in your project. Claude Code loads it when a task matches its description.

How do I install 701 Technologies Openapi in Codex?

Run `npx skills add jabrena/plinth --skill 701-technologies-openapi -a codex`. Or copy the skill folder (skills/701-technologies-openapi in jabrena/plinth) into .agents/skills/701-technologies-openapi in your project. Codex loads it when a task matches its description.

Can I use 701 Technologies 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 jabrena/plinth --skill 701-technologies-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/701-technologies-openapi, .gemini/skills/701-technologies-openapi, .github/skills/701-technologies-openapi and .opencode/skills/701-technologies-openapi in your project.

What does 701 Technologies Openapi need to run?

Going by SKILL.md and its folder, 701 Technologies Openapi needs the command-line tools its instructions call (mvn).

Does 701 Technologies Openapi access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is 701 Technologies 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 701 Technologies Openapi use?

701 Technologies Openapi is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does 701 Technologies Openapi use?

About 870 tokens (SKILL.md is roughly 3.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.5k tokens, read only when the agent opens those files.

What are the alternatives to 701 Technologies Openapi?

Skills that share tags, products or a category with 701 Technologies Openapi: Oryxos Init (oryx-labs/oryxos, 186 stars), Openapi First (rrezartprebreza/spring-boot-skills, 298 stars), Springboot Init Skill (jiushiwon/wg-skills, 112 stars) and Spring Boot Openapi Documentation (giuseppe-trisciuoglio/developer-kit, 355 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains 701 Technologies Openapi?

jabrena (a GitHub user) maintains it in jabrena/plinth, which has 446 GitHub stars. The repository holds 124 skills in this directory. The repository was last updated on October 7, 2026.

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