CtrlK
BlogDocsLog inGet started
Tessl Logo

load-issues

Load all open issues from GitHub and save them as markdown files

53

Quality

61%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./plugins/git/skills/load-issues/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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 clear commands and a well-defined output template. Its main weaknesses are the lack of validation/error handling steps (what if gh auth fails? what if an issue has special characters in the title that break kebab-case conversion?) and some minor verbosity. The workflow is clear but would benefit from explicit verification checkpoints.

Suggestions

Add a validation step to verify gh CLI authentication before starting (e.g., `gh auth status`) and handle the case where no open issues exist.

Add a verification step after writing files, such as counting created files and comparing against the issue list count.

Trim filler phrases like 'Extract all relevant metadata' and the final IMPORTANT note, which don't add actionable information.

DimensionReasoningScore

Conciseness

The skill is mostly efficient but includes some unnecessary verbosity. The 'IMPORTANT' note at the end is redundant, and phrases like 'Extract all relevant metadata' and 'ensure all issue data is properly formatted' are filler. The step-by-step structure is reasonable but could be tightened.

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 logical, but there are no validation checkpoints. There's no error handling for cases like gh CLI not being authenticated, no issues existing, or malformed issue data. No verification step to confirm files were written correctly.

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. The structure is appropriate for the task's complexity.

3 / 3

Total

10

/

12

Passed

Description

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), and occupies a distinct niche. 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. The trigger term coverage could also be broader to capture natural user phrasing variations.

Suggestions

Add a 'Use when...' clause such as 'Use when the user wants to export, download, or sync GitHub issues to local markdown files, or mentions backing up issues.'

Include additional trigger term variations like 'export issues', 'download issues', 'sync GitHub issues', 'backup issues', '.md files' to improve matching against natural user requests.

DimensionReasoningScore

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', 'markdown files', and 'open issues', 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

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.

Validation9 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

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
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.