How do I install the 701 Technologies Openapi skill?

Run npx skillmds@latest add gabrielmoreira/701-technologies-openapi 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 701 Technologies Openapi safe to use?

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

Which AI agents work with 701 Technologies Openapi?

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

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published 701 Technologies Openapi?

gabrielmoreira (@gabrielmoreira) published this skill. Their other Agent Skills are listed on their SkillMD profile.

701 Technologies Openapi by gabrielmoreira

Name: 701 Technologies Openapi
Rating: 4.5 (4 reviews)
Author: gabrielmoreira

701 Technologies Openapi

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

gabrielmoreira Updated Sep 9, 2026 17 repo stars

File contents

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

When to use this skill

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

Workflow

Read reference and assess project context

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

Gather scope and decide target improvements

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

Apply technology-aligned changes

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

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.

---name: 701-technologies-openapidescription: 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 Toolkitlicense: Apache-2.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 ## 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. 2. **Gather scope and decide target improvements** Identify requested outcomes, constraints, and the minimum safe set of changes to apply. 3. **Apply technology-aligned changes** Implement or refactor artifacts following the reference patterns and project conventions. 4. **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](references/701-technologies-openapi.md).

Frequently asked questions