- Home
- Skills
- Workflow Automation
- OpenAPI Spec Linter
OpenAPI Spec Linter
Separate OpenAPI specification defects from optional API governance rules and propose traceable corrections.
$1
Works with the AI Agents you already use
OpenAPI Spec Linter
Example session with this skill installed
An OpenAPI path /items/{id} declares id as optional; the team also prefers plural resource names.
- Read your context and instructions
- Compiled the openapi spec linter
Specification finding: a path parameter must be required; point to the exact parameter location and propose required: true. Plural naming is a separate team policy review. No validator run or live endpoint response check is claimed from this fixture.
Scope: synthetic worked example of the skill’s expected response pattern. No command, provider request, test run, profiling session, publication or production change is claimed by this example. On a real task, state exactly what evidence was inspected, what was generated, and what verification actually ran. Missing runtime, versions or permissions remain explicit rather than being replaced with invented outcomes.
Connects securely to your tools. The creator never sees your data.
About this skill
Separate OpenAPI specification defects from optional API governance rules and propose traceable corrections.
This original instruction-based skill adds an evidence-led workflow, input checklist, failure handling, reviewable output contract and a synthetic worked example. It is designed for compatible agent hosts; it does not bundle an external scanner, profiler, service, SDK or autonomous bot.
Required inputs: OpenAPI document/version, referenced files, intended governance rules and validator/version if available.
Limits: Not every REST preference is a normative OpenAPI rule. No live endpoint validation, automatic external-ref fetch or universal-version certification.
The package is MIT licensed, version 1.0.0. Documentation references were checked during authoring on 2026-10-28 where applicable; the skill requires installed-version/current-source checks when needed. Static/package validation and selected scenario exercises are not a claim of live integration testing, certification or guaranteed business results. Optional runtimes/services may have separate requirements and costs; they are not provisioned by this purchase.
Not every REST preference is a normative OpenAPI rule. No live endpoint validation, automatic external-ref fetch or universal-version certification. Instruction-only workflow; synthetic examples are not executed customer results.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 19 days ago
Permissions
Use supplied or authorized inputs only. No external endpoint, account, privileged credential or outbound messaging is required by the packaged example. Any optional live tool/network/external mutation must follow the user’s authorized task and destination. Do not transmit secrets or private data to referenced sites automatically.