Loading...
Loading...
Found 653 Skills
Use when the user asks to write specs before code, define acceptance criteria, plan features before implementation, generate tests from specifications, or follow spec-first development practices.
ABC Medical Cloud API Document Query Tool. Reads and queries the OpenAPI specification documents of ABC API (4209 interfaces), supports searching by module, path, and method, and automatically resolves $ref references. Usage scenarios: (1) Query API interface definitions (2) Search for interfaces with specific functions (3) Export interface document summaries (4) View interface statistics
This skill should be used when implementing DDD tactical design patterns in Go, including Entities, Value Objects, Aggregates, Repositories, Domain Services, Domain Events, Factories, and Specifications.
General Architecture Specification for CS-RAG Project, unifies global architecture cognition and architecture design constraints, provides entry points for layered inspection, impact analysis, interface contracts, dependency injection and pluggable governance.
Hub skill for requirements elicitation. Provides technique selection, orchestration guidance, LLMREI patterns, and autonomy level configuration. Use when gathering requirements from stakeholders, conducting elicitation sessions, or preparing requirements for specification.
Generate client SDKs in multiple languages from OpenAPI specifications. Use when generating client libraries for API consumption. Trigger with phrases like "generate SDK", "create client library", or "build API SDK".
Use when working with AI agent protocols, standards, and interoperability specifications. Covers MCP, A2A, ACP, Agent Skills, AGENTS.md, ADL, x402, AP2, MCP Apps, and cagent. USE FOR: agent protocol selection, comparing MCP vs A2A vs ACP, understanding agent standards ecosystem, choosing payment protocols DO NOT USE FOR: specific protocol implementation details (use the sub-skills: mcp, a2a, acp, x402, etc.)
Local Microsoft Open Specifications corpus navigator for Windows protocols. Use this skill when the user asks protocol-level questions, needs message/structure details, wants section-by-section summaries, or needs cross-references across related specifications.
Use this skill when crafting, reviewing, or improving prompts for LLM pipelines — including task prompts, system prompts, and LLM-as-Judge prompts. Triggers include: requests to write or refine a prompt, diagnose why an LLM produces inconsistent or incorrect outputs, bridge the gap between intent and model behavior, reduce ambiguity in instructions, add few-shot examples, structure complex prompts, or improve output formatting. Also use when the user needs help distinguishing specification failures (unclear instructions) from generalization failures (model limitations), or when iterating on prompts based on observed failure modes. Do NOT use for general coding tasks, document creation, or non-LLM writing.
Create semantic git commits following best practices and Conventional Commits specification.
Create a git commit following the Conventional Commits specification.
Gate 2 sub-skill - validates uncertain mappings from Gate 1 and confirms all field specifications through testing.