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.

65

Quality

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

57%

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

The body is well-organized and actionable for most steps but carries redundancy and omits the concrete apply-labels command and a validation/verification checkpoint around the destructive write. Tightening Notes and adding the gh label-set command plus a verify step would lift the weaker dimensions.

Suggestions

Replace the final "Apply label changes" step with the specific gh command (e.g., gh issue edit <issue> --add-label ... --remove-label ...) so the write action is copy-paste ready.

Add a validation/verification checkpoint before or after applying (confirm kept/added/removed sets are disjoint and target labels exist in the repo) since label mutation is a destructive batch operation.

Trim the "Notes" section to remove restatements of Label Selection Rules and template timing already covered, improving token efficiency.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete commands, but the "Notes" section restates Label Selection Rules already covered (label timing, respecting user intent, under-label guidance), adding redundant tokens.

2 / 3

Actionability

Provides concrete executable guidance (gh api event-history command, gh label list, classification thresholds) but the actual "Apply label changes" step lacks the specific gh command to set issue labels, leaving the final write action underspecified.

2 / 3

Workflow Clarity

An 8-step numbered Process gives a clear sequence, but label mutation is a destructive/batch operation and the workflow has no pre-apply validation or post-apply verification checkpoint, capping it per the rubric.

2 / 3

Progressive Disclosure

A single self-contained file (no bundle files present) with clean, well-organized sections (Input Variables, Task, Classification, Process, Report Format, Examples) that earns the simple-skill exception.

3 / 3

Total

9

/

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.

The description is specific, uses third person, and clearly states both capability and explicit use-when triggers with a distinct niche. It is a strong, conflict-resistant description.

DimensionReasoningScore

Specificity

Lists multiple concrete actions including "Assign GitHub issue labels based on content analysis", "preserves template-assigned and user-applied labels", and "updating skill-assigned labels based on current content", matching the multiple-specific-actions anchor.

3 / 3

Completeness

Explicitly answers both what (assign/preserve/update labels) and when via a numbered "Use when: (1)... (2)... (3)..." clause, the canonical complete pattern.

3 / 3

Trigger Term Quality

Covers natural terms a user would say ("issue is created and needs categorization", "relabeling after content changes", "labels") with good variation rather than jargon.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (GitHub issue label triage with label-preservation semantics) with distinct triggers unlikely to collide with other skills.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

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.