Stats
Actions
Tags
From browser-data-capture
Generate a draft OpenAPI 3.1 spec from an endpoints inventory produced by analyze-har, capture-via-proxy, or observe-tab. Reads endpoints.json + inferred schemas and emits openapi.yaml plus openapi.json. Use when the user wants to build a stable client against a captured surface — "make an OpenAPI spec from this", "generate a spec so I can build a client", "turn the capture into something I can codegen against".
How this skill is triggered — by the user, by Claude, or both
Slash command
/browser-data-capture:generate-openapiThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Promote a captured endpoint inventory into a draft OpenAPI 3.1 specification, suitable as a starting point for a client SDK or a documented integration contract.
Promote a captured endpoint inventory into a draft OpenAPI 3.1 specification, suitable as a starting point for a client SDK or a documented integration contract.
browser-data-capture run directory (containing endpoints.json + schemas/). If unspecified, list recent runs from ${CLAUDE_USER_DATA:-${XDG_DATA_HOME:-$HOME/.local/share}/claude-plugins}/browser-data-capture/data/ and ask which one.openapi.yaml — primary, hand-editable.openapi.json — same content, JSON form, for tooling that prefers JSON.notes.md — gaps the spec couldn't fill confidently: endpoints with too few samples to infer required fields, response variants that couldn't be reconciled, auth flows that need a human to describe.endpoints.json. For each endpoint:
paths.<path-template>.<method> entry.parameters: derive path parameters from {id} / {uuid} placeholders, query parameters from observed query keys, header parameters from interesting headers (skip auth — handled in securitySchemes).requestBody: if a request schema was inferred, reference components.schemas.responses: one entry per observed status code, content schema referenced from components.schemas.components.securitySchemes from the auth scheme detected in the inventory. Apply globally via security:.components.schemas from the per-endpoint inferred schemas. Deduplicate by content hash where possible.info.title, info.version, servers[0].url (most-contacted host).openapi-spec-validator is available, run it.notes.md with anything that couldn't be expressed cleanly.A draft spec inferred from observed traffic. Tell the user explicitly:
paths: for collapses that should be split.The spec is a starting point, not a finished artefact.
Searches MemPalace before answering questions about past work, people, projects, or prior decisions. Returns verbatim stored content instead of guessing from model memory.
Guides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.
Implements vector databases with Pinecone, Weaviate, Qdrant, Milvus, pgvector for semantic search, RAG, recommendations, and similarity systems. Optimizes embeddings, indexing, and hybrid search.
npx claudepluginhub danielrosehill/claude-code-plugins --plugin browser-data-capture