firefrost-gaming/claude-skills-reference
3
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity
Files
3d9d1d2d926129c4e5da6b93a00bc1252d663d01
claude-skills-reference/engineering/mcp-server-builder/references/openapi-extraction-guide.md
Alireza Rezvani 3d9d1d2d92 Dev (#249) 
* docs: restructure README.md — 2,539 → 209 lines (#247)

- Cut from 2,539 lines / 73 sections to 209 lines / 18 sections
- Consolidated 4 install methods into one unified section
- Moved all skill details to domain-level READMEs (linked from table)
- Front-loaded value prop and keywords for SEO
- Added POWERFUL tier highlight section
- Added skill-security-auditor showcase section
- Removed stale Q4 2025 roadmap, outdated ROI claims, duplicate content
- Fixed all internal links
- Clean heading hierarchy (H2 for main sections only)

Closes #233

Co-authored-by: Leo <leo@openclaw.ai>

* fix: enhance 5 skills with scripts, references, and Anthropic best practices (#248)

* fix(skill): enhance git-worktree-manager with scripts, references, and Anthropic best practices

* fix(skill): enhance mcp-server-builder with scripts, references, and Anthropic best practices

* fix(skill): enhance changelog-generator with scripts, references, and Anthropic best practices

* fix(skill): enhance ci-cd-pipeline-builder with scripts, references, and Anthropic best practices

* fix(skill): enhance prompt-engineer-toolkit with scripts, references, and Anthropic best practices

* docs: update README, CHANGELOG, and plugin metadata

* fix: correct marketing plugin count, expand thin references

---------

Co-authored-by: Leo <leo@openclaw.ai>

---------

Co-authored-by: Leo <leo@openclaw.ai>
2026-03-04 08:38:06 +01:00

867 B
Raw Blame History

OpenAPI Extraction Guide

Goal

Turn stable API operations into stable MCP tools with clear names and reliable schemas.

Extraction Rules

  1. Prefer operationId as tool name.
  2. Fallback naming: <method>_<path> sanitized to snake_case.
  3. Pull summary for tool description; fallback to description.
  4. Merge path/query parameters into inputSchema.properties.
  5. Merge application/json request-body object properties when available.
  6. Preserve required fields from both parameters and request body.

Naming Guidance

Good names:

  • list_customers
  • create_invoice
  • archive_project

Avoid:

  • tool1
  • run
  • get__v1__customer___id

Schema Guidance

  • inputSchema.type must be object.
  • Every required key must exist in properties.
  • Include concise descriptions on high-risk fields (IDs, dates, money, destructive flags).
Reference in New Issue View Git Blame Copy Permalink