read-github
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
90
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-structured description with excellent trigger coverage and clear 'when to use' guidance. The main weakness is the somewhat generic capability statement - 'read and search' could be more specific about what types of content can be accessed (README, wiki, code files, etc.).
Suggestions
Expand the opening sentence to list more specific actions, e.g., 'Read README files, browse wiki pages, search code and documentation within GitHub repositories via gitmcp.io MCP service.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (GitHub documentation) and some actions ('Read and search'), but lacks comprehensive concrete actions like 'browse README files, search code, navigate wiki pages'. | 2 / 3 |
Completeness | Clearly answers both what (read and search GitHub repo documentation) and when (explicit 'WHEN TO USE' section with multiple trigger scenarios including URL patterns and natural language queries). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'GitHub URL', 'owner/repo format', 'what does this repo do', 'read the docs', 'search code or docs'. These are realistic user phrases. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on GitHub repository documentation via gitmcp.io. The GitHub URL and owner/repo format triggers are distinct and unlikely to conflict with general documentation or code skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that efficiently documents the gitmcp.io integration with concrete, executable CLI commands. The content is appropriately concise and highly actionable. The main weakness is the workflow section, which could benefit from error handling guidance or validation steps when commands fail.
Suggestions
Add error handling guidance to the workflow section (e.g., what to do if fetch-docs returns empty or search yields no results)
Include a brief note on expected output format or success indicators for the CLI commands
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only necessary information without explaining concepts Claude already knows. Every section serves a clear purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | All CLI commands are copy-paste ready with clear syntax and examples. The URL conversion examples are concrete, and tool naming conventions are explained with specific examples. | 3 / 3 |
Workflow Clarity | The workflow section provides a logical sequence but lacks validation checkpoints or error handling guidance. No feedback loops for when commands fail or return unexpected results. | 2 / 3 |
Progressive Disclosure | For a skill of this size (~80 lines), the content is well-organized with clear sections. No external references are needed, and the structure allows easy navigation from URL conversion to CLI usage to workflow. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.