Skills Directory
Claude Skills by tools-only
github.com/tools-onlyComplete guide to the `/melt` skill for autonomous task execution with optional Agent Teams planning and completion validation. (`/build` is a legacy alias.)
Complete guide to the `/melt` skill for autonomous task execution with optional Agent Teams planning and completion validation. (`/build` is a legacy alias.)
Reference for identifying and resolving common failure patterns in web applications.
When running multiple agents in parallel, each agent should use its own **git worktree** to avoid conflicts on git operations, checkpoint files, and version tracking.
Consolidated patterns from `/deslop` (25 patterns) and `/qa` (6 dimensions) for the `/burndown` skill.
Complete setup instructions for the Maestro MCP server. This guide covers the forked Maestro with gRPC fixes required for reliable Android emulator connectivity.
Complete setup instructions for the Maestro MCP server. This guide covers the forked Maestro with gRPC fixes required for reliable Android emulator connectivity.
Defines the artifact schema for Maestro E2E test verification. The stop hook validates these artifacts exist and tests passed.
Defines the artifact schema for Maestro E2E test verification. The stop hook validates these artifacts exist and tests passed.
Three new skills for the `beagle-elixir` plugin covering Elixir documentation writing, ExDoc configuration, and documentation review.
Fetch review comments from a PR and evaluate with receive-feedback skill
Fetch review comments from a PR and evaluate with receive-feedback skill
A well-documented module tells the reader four things: what it does, when to use it, how to use it, and how to configure it.
Admonitions are callout boxes rendered by ExDoc. They use blockquote syntax with a special heading:
ExDoc auto-links identifiers written in backtick-delimited code spans. This reference covers every linking syntax available.
Go does not need a DI framework. The language's interfaces, structs, and constructor functions provide everything necessary for clean dependency injection.
`golang.org/x/time/rate` implements a token bucket rate limiter:
Standard `http.HandlerFunc` has no return value, forcing each handler to write its own error responses. The `AppHandler` pattern lets handlers return errors, with a single centralized function mapping errors to HTTP responses.
The `go-playground/validator` package uses struct tags to declare constraints. Here are the most frequently used tags for web APIs.
**Date:** 2026-02-10 **System:** macOS Darwin 25.2.0, Apple Silicon (ARM64) **ffmpeg:** 8.0.1 (Homebrew, with libx264/libx265/videotoolbox/audiotoolbox) ---
*Complete reference for all yaraQA automated checks. Use these to validate rules before deployment.* > yaraQA detects issues that are syntactically correct but dysfunctional — rules that never match, perform poorly, or use problematic patterns. ---
This guide demonstrates how to register and use an Amazon Bedrock AgentCore Gateway as an MCP server through the MCP Gateway Registry.
MCP Gateway Registry provides comprehensive audit logging for compliance, security monitoring, and operational visibility. All API requests and MCP server access events are logged to MongoDB/DocumentDB with automatic retention management. 
The MCP Gateway Registry provides authentication and authorization using industry-standard OAuth 2.0 flows with fine-grained access control.
The MCP Gateway Registry provides enterprise-ready authentication and authorization using industry-standard OAuth 2.0 flows with fine-grained access control.
This guide describes the three deployment modes available for MCP Gateway Registry on AWS ECS.
The MCP Gateway & Registry provides a powerful **Dynamic Tool Discovery and Invocation** feature that enables AI agents to autonomously discover and execute tools beyond their initial capabilities. This feature uses advanced semantic search with FAISS indexing and sentence transformers to intelligently match natural language queries to the most relevant MCP tools across all registered servers.
This document provides comprehensive guidance for implementing Keycloak authentication in the MCP Gateway, including design aspects, operational procedures, configuration parameters, and management scripts.
This document provides comprehensive technical documentation for the MCP Gateway Registry's authentication and authorization system. While the main [auth.md](./auth.md) covers the overall system architecture, this document focuses specifically on the **registry application's internal authentication mechanisms**, UI-based authentication flows, and technical implementation details.
This document provides comprehensive technical documentation for the MCP Gateway Registry's internal authentication and authorization system, focusing on the UI-based authentication flows and technical implementation details.
This document provides comprehensive technical documentation for the MCP Gateway Registry's internal authentication and authorization system, focusing on the UI-based authentication flows and technical implementation details.
This document provides a comprehensive overview of all API endpoints available in the MCP Gateway Registry service.
This document describes the scope configuration file format used by the MCP Gateway Registry for fine-grained access control.
> **Note**: While this document discusses Fine-Grained Access Control (FGAC) in the context of Amazon Cognito, the concepts and implementation apply to any Identity Provider (IdP). The same scope-based authorization model can be used with other OAuth2/OIDC providers by adapting the group mapping and token validation mechanisms. This document provides comprehensive documentation for the fine-grained access control system in the MCP Gateway Registry, explaining how the scope-based authorization...
> **Note**: While this document discusses Fine-Grained Access Control (FGAC) in the context of Amazon Cognito, the concepts and implementation apply to any Identity Provider (IdP). The same scope-based authorization model can be used with other OAuth2/OIDC providers by adapting the group mapping and token validation mechanisms. This document provides comprehensive documentation for the fine-grained access control system in the MCP Gateway Registry, explaining how the scope-based authorization...
This guide covers the operational workflows for managing multiple versions of MCP servers in the gateway registry. For the technical design and architecture details, see [Server Versioning Design](design/server-versioning.md). The following shows the version badges on server cards (both the MCP server-reported version and the user-provided routing version) and the version swap workflow using the Version Selector Modal:  ---
**October 28, 2025** ---
**November 2025** ---
This guide documents the Agent-to-Agent (A2A) protocol implementation in the MCP Gateway Registry. Rather than a specification, this is a practical guide to understanding how the system works today, how agents register themselves, how discovery works, and how access control is enforced across the entire stack.
This guide documents the Agent-to-Agent (A2A) protocol implementation in the MCP Gateway Registry. Rather than a specification, this is a practical guide to understanding how the system works today, how agents register themselves, how discovery works, and how access control is enforced across the entire stack.
This document describes the architecture and data model for the Agent Skills feature in MCP Gateway Registry.
> **Note**: The Anthropic API version (v0.1) is defined as a constant `ANTHROPIC_API_VERSION` in `registry/constants.py`. All code references this constant rather than hardcoding the version string. ---
This document discusses two potential architectures that were considered during the design phase of this solution: a **reverse proxy architecture** and an alternative **tools gateway architecture**. We analyze both approaches from multiple perspectives: performance, security, long-term maintainability, scaling, and operational complexity, and explain why the reverse proxy approach was selected.
This document explains the design decisions behind the session cookie security implementation in the MCP Gateway Registry, particularly regarding the use of domain cookies for cross-subdomain authentication.
**Version:** 1.0 **Last Updated:** 2026-01-18
**Date**: 2026-01-29 **Status**: Implemented **Issue**: [#370](https://github.com/agentic-community/mcp-gateway-registry/issues/370) ---
Flexible, vendor-agnostic embeddings generation for MCP Gateway Registry's semantic search functionality.
Quick reference for commonly used VS Code APIs.
Complete API reference for Cloudflare DNS operations.
[English README](README.md) 这是一个主要用于为 CS2 生成 signatures/offsets，并通过 Agent SKILLS 与 MCP Calls 更新 HL2SDK_CS2 C++ 头文件的项目。 该项目的设计目标是在**完全无需人工参与**的情况下更新 signatures/offsets/cpp headers。 目前，本项目已可自动更新 **CounterStrikeSharp** 和 **CS2Fixes** 的全部 signatures/offsets。 * 欢迎通过 PR 贡献你的 SKILL！[如何创建SKILL? 见这里](https://github.com/hzqst/CS2_VibeSignatures/issues?q=is%3Aissue%20state%3Aclosed) - `TODO: Add skill support for XXXXXXX`