Content
55%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is admirably lean but underspecified: it names one tool call and then leaves Claude to guess what 'propose a solution' means — a comment, a patch, a plan? The silent-workflow instruction ('NEVER share any thinking process...') is a real behavioral constraint but arrives without context. Concrete output expectations and a defined final step would lift this from a hint to a workflow.
Suggestions
Specify the concrete invocation, e.g. "Call the get_issue tool with the issue number" — the current backtick phrasing ('Use the `get_issue`') is grammatically ambiguous about the tool's actual name.
Define what 'propose a solution' means concretely: the expected output format (e.g. diagnosis, root cause, and a fix plan or patch) and where it should be delivered.
Add minimal section headers (e.g. '## Process', '## Output') so the two instruction types — workflow steps and the silence constraint — are visually separated.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is three short sentences plus one behavioral constraint with no padding and no explanation of concepts Claude already knows — every token carries instruction weight. | 5 / 5 |
Actionability | "Use the `get_issue` to retrieve its details" is the only semi-concrete step (and even the tool name/arguments are ambiguous), while "Understand the issue and propose a solution to solve it" is a high-level hint with no specifics on what a proposal looks like or what to do with it. | 2 / 5 |
Workflow Clarity | A rough sequence exists (retrieve details → understand → propose) but steps are poorly defined — the terminal action 'propose a solution' has no defined form, output, or follow-up, and no checkpoints of any kind. The destructive/batch cap does not apply since this is neither. | 2 / 5 |
Progressive Disclosure | The skill is under 50 lines with no external references needed and all content appropriately inline, but it has no organizational structure at all — the simple-skill path to a 5 requires well-organized sections, and even one or two headers would help. | 4 / 5 |
Total | 13 / 20 Passed |