333 boosters for "context" — open source, verified from GitHub, ready to install
Heuristic scoring (no AI key configured).
Automates GitHub pull request analysis by gathering diffs, comments, related issues, and local code context to provide comprehensive reviews. Developers and code reviewers benefit from faster, more thorough PR evaluations.
"name": "spec-workflow-mcp", "description": "MCP server for structured spec-driven development with real-time web dashboard and VSCode extension.", "homepage": "https://github.com/Pimzino/spec-workflow-mcp",
"name": "arscontexta", "description": "Conversational derivation engine — generate agent-native memory architecture from natural conversation. 15 kernel primitives, 26 commands, 17 feature blocks, 3 presets.", "url": "https://arscontexta.org"
"description": "A Model Context Protocol (MCP) server for Grafana providing access to dashboards, datasources, and querying capabilities", "name": "Grafana Labs" "homepage": "https://github.com/grafana/mcp-grafana",
"name": "mcp-markdownify-server", "description": "MCP Markdownify Server - Model Context Protocol Server for Converting Almost Anything to Markdown", "author": "@zcaceres (@zachcaceres | zach.dev)",
This skill provides automated assistance for react context setup tasks within the Frontend Development domain. This skill activates automatically when you: 1. Provides step-by-step guidance for react context setup
This MCP booster enables AI assistants like Cursor and Windsurf to control Unreal Engine 5.5.4 through natural language commands, providing developers with guidelines for Python tool implementation and UE-specific best practices including coordinate systems and units.
Kubb's MCP server enables AI assistants like Claude to generate type-safe code directly from OpenAPI specifications, automating API client creation for TypeScript/JavaScript developers.
"name": "prompt-improver", "description": "Intelligent prompt optimization: injects the right context at the right moment so Claude lands a better first output. Clarifies vague prompts with research-based questions, plus targeted nudges for approach selection, plan readability, workflow routing, bac
"name": "actionbook", "description": "Actionbook MCP server for up-to-date browser automation. Get verified CSS/XPath selectors for any website directly into your agent context.", "name": "Actionbook"
Claude Code Workflow is a JSON-driven multi-agent development framework that orchestrates AI-powered CLI workflows across multiple LLM providers (Gemini, Qwen, Codex) for automated code development tasks. It benefits developers and teams seeking to automate complex development workflows with intelligent context management and multi-agent coordination.
"name": "token-optimizer", "description": "Audit, fix, and monitor Claude Code context window usage. Find the ghost tokens.", "name": "Alex Greenshpun",
MCP Remote is a proxy server that enables local-only AI clients to connect to remote Model Context Protocol servers using OAuth authentication. It's essential for developers building Claude integrations that need to bridge local and remote MCP server connections securely.
"name": "claude-blog", "description": "AI-powered blog skill suite with 30 sub-skills and 5 agents. FLOW framework integration (Find/Optimize/Win, 30 evidence-led prompts), semantic topic-cluster planning + execution, multilingual publishing (translate/localize/locale-audit), Google API integration
MongoDB Model Context Protocol Server
AGENTS.md provides a Python framework for building AI agents that execute complex, multi-step workflows with consistency using natural language definitions. Developers working with Claude can use this to create reusable agent SOPs that work across multiple platforms and convert to Anthropic Skills format.
Hyperbrowser MCP Server enables Claude to perform web scraping, crawling, and content extraction through the Model Context Protocol. Developers building AI applications that need to interact with web content will find this particularly valuable.
Analyzes ANY input to find, improve, or create the right skill. Start with least privilege (, , , , ). Only add higher-risk tools when explicitly required:
Review the most recent commit (or the commit specified in ) in a single pass, using FXA-specific knowledge. Use Read and Grep to examine the changed files and their surrounding context. Look at imports, callers, and related types to understand the full picture before judging. Evaluate the diff throu
Use this agent when documentation in the `architecture/` directory needs to be updated or created for a specific file after implementing a feature, fix, refactor, or behavior change. Launch one instance of this agent per file that needs updating. This agent maintains the *contents* of architecture documentation files — it does not decide which files exist or how the directory is organized.\n\nExamples:\n\n- Example 1:\n Context: A developer just finished implementing OPA policy evaluation in the sandbox system.\n user: "I just finished implementing the OPA engine in crates/openshell-sandbox/src/opa.rs. Update architecture/sandbox.md to reflect the new policy evaluation flow."\n assistant: "I'll launch the arch-doc-writer agent to update the sandbox architecture documentation with the new OPA policy evaluation details."\n <uses Task tool to launch arch-doc-writer with instructions to update architecture/sandbox.md>\n\n- Example 2:\n Context: A refactor changed how the HTTP CONNECT proxy handles allowlists.\n user: "The proxy allowlist logic was refactored. Please update architecture/proxy.md."\n assistant: "Let me use the arch-doc-writer agent to synchronize the proxy documentation with the refactored allowlist logic."\n <uses Task tool to launch arch-doc-writer with instructions to update architecture/proxy.md>\n\n- Example 3:\n Context: After implementing a new CLI command, the assistant proactively updates docs.\n user: "Add a --rego-policy flag to the CLI."\n assistant: "Here is the implementation of the --rego-policy flag."\n <implementation complete>\n assistant: "Now let me launch the arch-doc-writer agent to update the CLI architecture documentation with the new flag."\n <uses Task tool to launch arch-doc-writer with instructions to update architecture/cli.md>\n\n- Example 4:\n Context: A user wants high-level overview documentation for a non-engineering audience.\n user: "Update architecture/overview.md with a non-engineer-friendly explanation of the sandbox system."\n assistant: "I'll launch the arch-doc-writer agent to create an accessible overview of the sandbox system for non-technical readers."\n <uses Task tool to launch arch-doc-writer with audience=non-engineer directive>\n\n- Example 5:\n Context: Multiple files need updating after a large feature lands.\n user: "I just landed the network namespace isolation feature. Update architecture/sandbox.md and architecture/networking.md."\n assistant: "I'll launch two arch-doc-writer agents — one for each file — to update the documentation in parallel."\n <uses Task tool to launch arch-doc-writer for architecture/sandbox.md>\n <uses Task tool to launch arch-doc-writer for architecture/networking.md>
