oas-generator SKILL.md skillA
oas-generator from pactflow/pactflow-agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add pactflow/pactflow-agent-skills/oas-generator@git:20261001.92aa387Pins git:20261001.92aa387 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- pactflow/pactflow-agent-skills
- Path
plugins/swagger-contract-testing/skills/oas-generator/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261001.92aa387, committed Oct 1, 2026
- First version recorded
- Sep 21, 2026
- Size
- 8,217 bytes
- Repository stars
- 7
- License
- MIT
Generates an OpenAPI 3.x YAML spec from a provider codebase using ripwire when no spec exists. Invoke this skill whenever the user needs an OpenAPI spec for a service that doesn't have one published — phrases like "generate an openapi spec from the code", "there's no oas for this service", "create a spec from the codebase", "the provider doesn't have a spec", or any time a pact-coverage or contract testing workflow is blocked because the provider spec is missing. Uses ripwire to extract HTTP…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# OAS Generator Generates an OpenAPI 3.x YAML spec by statically analysing a provider codebase with ripwire. The spec may be incomplete (stubs for unresolvable schemas), but it will always be valid OAS and immediately usable for path-coverage testing. **Prerequisites:** `ripwire` on PATH. If absent, check `pact-coverage/references/install-ripwire.md`. --- ## Step 1 — Identify the framework Run ripwire to get oriented, then infer the framework from the ranked output and config files: ```bash ripwire <provider-root> --for="HTTP route definitions and request handlers" ``` Also check for framework config files in the project root: - `Gemfile` with `sinatra` or `rails` → Ruby - `package.json` with `express`, `fastify`, `koa`, or `hapi` → Node.js - `pyproject.toml` / `requirements.txt` with `flask` or `fastapi` → Python If the framework is still ambiguous after these checks, ask the user. --- ## Step 2 — Extract all routes Use framework-specific patterns to find every route registration. Run all applicable patterns and deduplicate results. Use `--regex=` for these patterns: `--grep=` is a literal match, so alternation (`a|b`) silently returns zero hits. ### Ruby — Rails …
Read the whole file at its exact version.
How to install
mdr add pactflow/pactflow-agent-skills/oas-generator@sha256:4de9e782215465f6The line at the top of this page pins the label git:20261001.92aa387, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_hvxwrfpljm243nhu)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Sep 21, 2026 and Oct 1, 2026, about one every 10 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261001.92aa387 latest | 2026-10-01 | 92aa387 | 8,217 B | A | view · diff |
| git:20260921.602eee1 | 2026-09-21 | 602eee1 | 8,117 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8217 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
pactflow/pactflow-agent-skills · 7 stars · license MIT · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hvxwrfpljm243nhu GET https://markdownregistry.com/api/v1/resolve?ref=pactflow/pactflow-agent-skills/oas-generator GET https://markdownregistry.com/api/v1/blob/4de9e782215465f62a68178af1b08346176128ef10f58850b49d89562b9868c9
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.