agent-browser
A fast Rust-based headless browser automation CLI with Node.js fallback that enables AI agents to navigate, click, type, and…
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
$ npx -y skills add am-will/codex-skills --skill read-github --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/read-githubContext preview
The summary Claude sees to decide when to auto-load this skill.
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
name: read-github description: | 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
Access GitHub repository documentation and code via the gitmcp.io MCP service.
Convert GitHub URLs to gitmcp.io:
The `scripts/gitmcp.py` script provides CLI access to repository docs.
python3 scripts/gitmcp.py list-tools owner/repo
Retrieves the full documentation file (README, docs, etc.):
python3 scripts/gitmcp.py fetch-docs owner/repo
Semantic search within repository documentation:
python3 scripts/gitmcp.py search-docs owner/repo "query"
Search code using GitHub Search API (exact match):
python3 scripts/gitmcp.py search-code owner/repo "function_name"
Fetch content from URLs mentioned in documentation:
python3 scripts/gitmcp.py fetch-url owner/repo "https://example.com/doc"
Call any MCP tool directly:
python3 scripts/gitmcp.py call owner/repo tool_name '{"arg": "value"}'Tool names are dynamically prefixed with the repo name (underscored):
For any repository, these tools are available:
1. **fetch_{repo}_documentation** - Fetch entire documentation. Call first for general questions. 2. **search_{repo}_documentation** - Semantic search within docs. Use for specific queries. 3. **search_{repo}_code** - Search code via GitHub API (exact match). Returns matching files. 4. **fetch_generic_url_content** - Fetch any URL referenced in docs, respecting robots.txt.
1. When given a GitHub repo, first fetch documentation to understand the project 2. Use search-docs for specific questions about usage or features 3. Use search-code to find implementations or specific functions 4. Use fetch-url to retrieve external references mentioned in docs
A collection of Codex/agent skills for planning, documentation access, frontend development, and browser automation.
A fast Rust-based headless browser automation CLI with Node.js fallback that enables AI agents to navigate, click, type, and…
Create or update Codex hooks for global or project scope by asking for scope and hook type when ambiguous, then writing the hook…
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web…
Build responsive, mobile-first layouts using fluid containers, flexible units, media queries, and touch-friendly design that…
Build and run Gemini 2.5 Computer Use browser-control agents with Playwright. Use when a user wants to automate web browser tasks…
Build, transform, audit, and migrate prompts for GPT-5.6 Sol using outcome-first contracts, explicit success criteria, evidence…