write-openapi
Author, configure, structure, and troubleshoot OpenAPI/Swagger API reference documentation in GitBook. Use this whenever a task involves a GitBook OpenAPI…
Find an Agent Skill for your task. Read the guide and copy the install command.
Updated 11-18 00:15
41,687 results
Author, configure, structure, and troubleshoot OpenAPI/Swagger API reference documentation in GitBook. Use this whenever a task involves a GitBook OpenAPI…
Review a proposal for structural flaws in reflection mode, focusing on path planning, module responsibilities, extensibility, decision selection, and project pollution; provide a minimal alternative design and rule continue / continue with conditions / pause. Use when the user asks to review a proposal, stress-test a design, or asks "what structural problems does this proposal have".
PagBank/PagSeguro integration guide for REST APIs, OAuth Connect, checkout (redirect and transparent), split payments, webhooks, mTLS transfers, PCI…
Create a new Quarkus project (Maven or Gradle) with the Quarkus CLI, code.quarkus.io API or Maven plugin, choose extensions, and run it in dev mode. Use when…
USE FOR: understanding an unfamiliar repository and how it got that way — its layout, where a behaviour is implemented, and when and why a particular function…
USE FOR: handing a piece of work to the Copilot coding agent — judging whether an issue is scoped tightly enough to delegate, launching it, and asking for an…
USE FOR: filing one clear bug report or feature request — checking it is not already reported, choosing its type and fields, breaking it into sub-issues, and…
USE FOR: triaging a backlog of open GitHub issues — judging which are actionable, labelling and typing them, linking duplicates and parents, and closing what…
USE FOR: examining someone else's pull request and delivering a verdict — reading the diff in context, leaving line-anchored comments as a batch, and approving…
USE FOR: working through review feedback left on a pull request — reading each unresolved thread, deciding what to change, replying to the reviewer, and…
USE FOR: changing what a repository holds or whether it exists at all — opening a working branch, committing files remotely, deleting what should go, and…
USE FOR: finding a library, tool or organisation you cannot yet name, judging whether a candidate project is worth depending on, and keeping a starred…
Prepare reusable repository-guidance improvements from selected Hub feedback findings when the user requests proposals or solutions after a review. Present…
Create and wire Replica prototype controls. Use when asked to add or change dropdowns, sliders, input fields, toggles or action buttons that configure…
Provides capability to convert functional specifications into executable and trackable tasks. Use when needing to transform a spec from…
Provides guided task implementation capability for executing specific tasks from a task list generated by spec-to-tasks. Use when implementing a specific task…
Hand a written brief to an ACP agent that works in its own git worktree and herdr workspace, then check its work before anyone merges it. Writes a dated…
Research technical approaches, execute a bounded comparison, and deliver reusable integration-quality code with a reproducible experiment. Use when the user…
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js…
IDA Pro reverse engineering and binary analysis. Use when writing IDAPython scripts, using IDA Domain API or idalib, analyzing binaries with IDA Pro…
Use when user wants to analyze a resume/CV file (PDF or text) for software engineering, test development, or frontend development candidates. Triggers: "分析简历",…
Fetch the latest Claude Code changelog. Trigger words: claude changelog, what CC updated, claude code update, latest version, what's new in claude code
Analyze git commits within a specified time range and generate a work retrospective report. Trigger words: retrospective, review commits, git review, what did I do today, work summary, daily review, retrospective
Go backend requirements analysis: functional boundaries, acceptance criteria, domain model, API contracts, data consistency rules, non-functional requirements, delivery risks. Use before technical design or coding.