load-issues
Load all open issues from GitHub and save them as markdown files
67
61%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/git/skills/load-issues/SKILL.mdQuality
Discovery
50%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description clearly states what the skill does with specific actions (loading GitHub issues and saving as markdown), giving it good specificity and distinctiveness. However, it completely lacks a 'Use when...' clause, which is critical for Claude to know when to select this skill from a pool of many. Adding trigger guidance and more keyword variations would significantly improve its effectiveness.
Suggestions
Add a 'Use when...' clause such as 'Use when the user wants to export, download, or sync GitHub issues to local markdown files'.
Include additional trigger term variations like 'export issues', 'download issues', 'sync issues', 'bug reports', '.md files', or 'backup issues'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists specific concrete actions: 'Load all open issues from GitHub' and 'save them as markdown files'. These are clear, actionable operations. | 3 / 3 |
Completeness | The description answers 'what does this do' but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and since the 'when' is entirely absent, this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes natural keywords like 'GitHub', 'issues', and 'markdown files', but misses common variations users might say such as 'export issues', 'download issues', 'sync issues', 'bug reports', or '.md files'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of GitHub issues + saving as markdown files is a very specific niche. It's unlikely to conflict with other skills due to the narrow, well-defined scope. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with specific CLI commands, a clear markdown template, and a concrete file naming convention. Its main weakness is the lack of validation/error handling steps for what is essentially a batch file-creation operation—there's no guidance on handling failed API calls or verifying output. Minor verbosity could also be trimmed.
Suggestions
Add validation steps: verify gh CLI authentication, check that each issue was fetched successfully before writing, and confirm file count matches issue count after completion.
Add error handling guidance: what to do if gh issue view fails for a specific issue (skip and report, retry, etc.).
Trim unnecessary prose like 'Follow these steps:', 'IMPORTANT: Execute all steps in the correct order', and 'Extract all relevant metadata' which don't add actionable information.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary verbosity like 'Follow these steps' and the final 'IMPORTANT' reminder which doesn't add value. The template and steps are reasonably tight but could be more concise—e.g., the gh CLI commands and markdown template are useful, but the surrounding prose could be trimmed. | 2 / 3 |
Actionability | Provides specific, executable CLI commands (gh issue list, gh issue view with exact JSON fields), a concrete file naming convention with example, and a complete markdown template. Claude can follow this without ambiguity. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced and numbered, but there are no validation checkpoints—no error handling for failed gh commands, no verification that files were written correctly, and no feedback loop if an issue fetch fails. For a batch file-creation operation, this is a notable gap. | 2 / 3 |
Progressive Disclosure | This is a simple, single-purpose skill under 50 lines with no need for external references. The content is well-organized with numbered steps and a clear template section, which is appropriate for its scope. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- NeoLabHQ/context-engineering-kit
- Commit
dedca19
- 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.