Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From openapi-tools
This skill should be used when the user wants to list or show API endpoints or routes for a running service. Trigger phrases: "list endpoints", "show endpoints", "what endpoints are available", "list API routes", "show API".
How this skill is triggered — by the user, by Claude, or both
Slash command
/openapi-tools:openapi-listThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Fetch the OpenAPI spec from a running service and list all endpoints with their HTTP methods and summaries.
Fetch the OpenAPI spec from a running service and list all endpoints with their HTTP methods and summaries.
http://localhost:8000.{host} with the resolved host:curl -s {host}/openapi.json | jq -r '.paths | to_entries[] | .key as $path | .value | to_entries[] | "\(.key | ascii_upcase) \($path) \(.value.summary // "")"'
npx claudepluginhub alex-kopylov/zweihander --plugin openapi-toolsGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.