CtrlK
BlogDocsLog inGet started
Tessl Logo

assign-label

Assign GitHub issue labels based on content analysis. Use when: (1) A new issue is created and needs categorization, (2) An issue needs relabeling after content changes, (3) Analyzing issue content to determine appropriate labels. Intelligently preserves template-assigned and user-applied labels while updating skill-assigned labels based on current content.

72

Quality

88%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-structured, actionable skill with clear workflow steps and excellent example scenarios that cover important edge cases. Its main weakness is moderate verbosity—the Notes section largely duplicates earlier rules, and the examples, while valuable, make the file quite long. The skill could benefit from extracting examples into a separate file and trimming redundant guidance.

Suggestions

Extract the three example scenarios into a separate EXAMPLES.md file and reference it from the main skill to improve progressive disclosure and reduce token usage.

Remove or consolidate the Notes section, as most points (respect user intent, conservative labeling, template timing) are already covered in Label Selection Rules and Label Classification.

DimensionReasoningScore

Conciseness

The skill is reasonably efficient but includes some redundancy—the Notes section repeats rules already stated in Label Selection Rules and Label Classification sections. The example scenarios, while useful, are quite lengthy and could be more compact.

2 / 3

Actionability

Provides concrete, executable gh CLI commands for fetching label history and labels. The process is specific with clear classification criteria (e.g., 5-second window for template labels, actor-based classification), and the examples show exact input/output states.

3 / 3

Workflow Clarity

The 8-step process is clearly sequenced with explicit classification logic (template vs user vs skill labels), clear decision rules for keep/add/remove, and a structured report format that serves as a verification checkpoint. The examples demonstrate the workflow applied to edge cases.

3 / 3

Progressive Disclosure

The content is a single monolithic file with no references to external files. The three detailed example scenarios could be split into a separate EXAMPLES.md to keep the main skill leaner. However, for a skill of this complexity, the inline structure is still navigable with clear section headers.

2 / 3

Total

10

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is an excellent skill description that clearly communicates its purpose, provides explicit trigger conditions, and uses natural language that would help Claude select it appropriately. It uses third person voice consistently, lists concrete actions, and differentiates itself well with its specific focus on GitHub issue label management.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: assigning labels based on content analysis, preserving template-assigned and user-applied labels, updating skill-assigned labels based on current content. These are specific, actionable capabilities.

3 / 3

Completeness

Clearly answers both 'what' (assign GitHub issue labels based on content analysis, preserve template/user labels) and 'when' with an explicit 'Use when:' clause listing three specific trigger scenarios.

3 / 3

Trigger Term Quality

Includes strong natural trigger terms: 'GitHub issue labels', 'categorization', 'relabeling', 'issue content', 'labels'. These are terms users would naturally use when needing this functionality.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with a clear niche: GitHub issue label assignment specifically. The focus on label categorization, preservation of different label types, and content-based analysis makes it unlikely to conflict with other skills.

3 / 3

Total

12

/

12

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
netwrix/docs
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.