Content
65%Weight 40%Scale 1-3Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A highly actionable command catalog with concrete, copy-paste-ready examples and clear sectioning. Its weaknesses are a missing validation step in the merge workflow and a monolithic inline structure that would benefit from splitting the API reference into a bundled file.
Suggestions
Add a validation checkpoint to the workflow before merging, e.g. 'Run get_pull_request_status and confirm CI passes before merge_pull_request.'
Move the per-tool command catalog into a references file (e.g. references/github-tools.md) and keep SKILL.md as a concise overview pointing to it, improving progressive disclosure.
Replace the per-section one-line descriptions with a compact table and use placeholder owner/repo (e.g. <owner>/<repo>) so examples generalize instead of repeating the same hardcoded repository.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly lean, executable command blocks with little concept explanation, but the repeated one-line descriptions ('List PRs in a repository:') duplicate the tool headings and every example hardcodes the same owner/repo, so it could be tightened. | 2 / 3 |
Actionability | Nearly every operation is shown as a concrete, copy-paste-ready 'mcporter call mcp-github.<tool>' command with real arguments, fully executable rather than pseudocode. | 3 / 3 |
Workflow Clarity | The 'Typical Workflow' lists a 5-step sequence but lacks validation checkpoints (e.g. check CI status / mergeability before merging); since merging is destructive, the missing feedback loop caps workflow clarity at 2. | 2 / 3 |
Progressive Disclosure | No bundle files exist and the full API reference (~400 lines) lives inline in SKILL.md; sections are well-organized, but reference content that could be split into a separate file is kept inline with no signaled external references. | 2 / 3 |
Total | 9 / 12 Passed |