Content
42%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a product README or marketing document than an actionable agent skill. It has a reasonable workflow structure but lacks concrete, executable guidance—most phases describe what to analyze rather than providing specific commands, API calls, or code to do so. The content is padded with unnecessary promotional language and sections that don't help Claude perform the task.
Suggestions
Replace the 'Quick Start' example prompts section with actual executable commands or code snippets that Claude can run, such as specific `gh api` calls for trending repos and detailed `gh issue list` invocations with filtering.
Add concrete output templates or JSON schemas for the Phase 4 dossier so Claude knows exactly what format to produce.
Remove marketing fluff ('precision skill', 'top-tier contributor', 'Contributing to the Matrix', 'Powered by OpenClaw') and the 'When to Use' section, which restates what the description already covers.
Add validation steps between phases—e.g., verify repo meets star/activity thresholds before proceeding to issue extraction, and verify issues are still open and unassigned before analysis.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains significant unnecessary padding: the intro paragraph explains what the skill does in marketing language ('precision skill', 'top-tier contributor'), the 'When to Use' section restates the obvious, 'Quick Start' provides example prompts rather than actionable instructions, and the 'Contributing to the Matrix' section is irrelevant filler. Much of this is fluff that doesn't help Claude execute the task. | 2 / 5 |
Actionability | There is one concrete executable command (`gh issue list`), but most guidance is high-level and descriptive rather than executable. Phase 3 and Phase 4 describe what to do conceptually but lack concrete code, specific API calls, or copy-paste ready commands. The feasibility analysis criteria are listed but not operationalized with specific steps or tools. | 3 / 5 |
Workflow Clarity | The four-phase workflow provides a reasonable sequence, but there are no validation checkpoints or feedback loops. There's no step to verify that discovered repos actually meet criteria, no error handling if `gh` commands fail, and no verification that the dossier output is complete or accurate before presenting to the user. The phases are more descriptive than prescriptive. | 3 / 5 |
Progressive Disclosure | The content is structured with clear section headers and phases, which is good. However, there are no bundle files or referenced documents for deeper content (e.g., detailed heuristics for Phase 3, dossier templates, or example outputs). Everything is inlined in a single file at a medium level of detail—not deep enough to be fully useful, but not organized to point to supplementary materials either. | 3 / 5 |
Total | 11 / 20 Passed |