Loading...
Loading...
Found 42 Skills
Compare OpenAI Codex GPT-5.3 and code-searcher responses for comprehensive dual-AI code analysis. Use when you need multiple AI perspectives on code questions.
Read and search GitHub repository documentation via gitmcp.io MCP service. **WHEN TO USE:** - User provides a GitHub URL - User mentions a specific repo in owner/repo format - User asks "what does this repo do?", "read the docs for X repo", or similar - User wants to search code or docs within a repo
Provide the ability to search, inspect, and read source code from all public GitHub repositories and their associated documentation.
box a git repo, clone it locally and search the real source, with a tracked manifest. Delegates repo work to subagents when available, runs in the main thread otherwise. Triggers: a VCS URL (GitHub, GitLab, Bitbucket), a previously cloned repo name, or a request to clone/search/explore a repo. Flags: --persist, --update, --list, --no-subagents.
Reference for all GrepAI MCP tools. Use this skill to understand available MCP tools and their parameters.
Use with root `twg` for code search, repositories using an API/package, implementation and reverse-dependency discovery, PR status and reviews, repo contributors, hot areas, and issue-to-PR lookups.
Configure search result boosting in GrepAI. Use this skill to prioritize certain paths and penalize others.
In-game (programmable block, aka PB) script development for Space Engineers version 1. Search script code for examples and patterns.
Free AI search via Exa MCP. Web search for news/info, code search for docs/examples from GitHub/StackOverflow, company research for business intel. No API key needed.
AST-based code search and refactoring via ast-grep MCP
Enhanced code search with custom ripgrep binary supporting ES module extensions and advanced patterns.
Performs fast text search with one-shot patterns that minimize iterations by getting files, lines, and context in a single call. Use this skill when searching for text patterns, finding specific code locations, or getting context around matches