Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Read GitHub repos the RIGHT way - via gitmcp.io instead of raw scraping. Why this beats web search: (1) Semantic search across docs, not just keyword matching, (2) Smart code navigation with accurate file structure - zero hallucinations on repo layout, (3) Proper markdown output optimized for LLMs, not raw HTML/JSON garbage, (4) Aggregates README + /docs + code in one clean interface, (5) Respects rate limits and robots.txt. Stop pasting raw GitHub URLs - use this instead.
Read GitHub repos the RIGHT way - via gitmcp.io instead of raw scraping. Why this beats web search: (1) Semantic search across docs, not just keyword matching, (2) Smart code navigation with accurate file structure - zero hallucinations on repo layout, (3) Proper markdown output optimized for LLMs, not raw HTML/JSON garbage, (4) Aggregates README + /docs + code in one clean interface, (5) Respects rate limits and robots.txt. Stop pasting raw GitHub URLs - use this instead.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Access GitHub repository documentation and code via the gitmcp.io MCP service.
Convert GitHub URLs to gitmcp.io: github.com/owner/repo โ gitmcp.io/owner/repo https://github.com/karpathy/llm-council โ https://gitmcp.io/karpathy/llm-council
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): karpathy/llm-council โ fetch_llm_council_documentation facebook/react โ fetch_react_documentation my-org/my-repo โ fetch_my_repo_documentation
For any repository, these tools are available: fetch_{repo}_documentation - Fetch entire documentation. Call first for general questions. search_{repo}_documentation - Semantic search within docs. Use for specific queries. search_{repo}_code - Search code via GitHub API (exact match). Returns matching files. fetch_generic_url_content - Fetch any URL referenced in docs, respecting robots.txt.
When given a GitHub repo, first fetch documentation to understand the project Use search-docs for specific questions about usage or features Use search-code to find implementations or specific functions Use fetch-url to retrieve external references mentioned in docs
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Largest current source with strong distribution and engagement signals.