CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

label-issue

Use when classifying an OpenShell issue or pull request, correcting inaccurate area/topic labels, or migrating obsolete, retired, or malformed classification associations.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

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

An unusually disciplined skill body: terse, rule-dense, free of padding, with a clean one-level reference split and verification baked into the apply path. The two dims at 4 reflect that executable specifics and the explicit step sequence are delegated to the reference file rather than carried in the body, leaving the body's own workflow slightly implicit.

Suggestions

Make the top-level step sequence explicit in the body (e.g., a short numbered list: prepare → inspect evidence → choose labels → write result → preview → apply) so the workflow is legible without opening the reference.

Add one concrete example of a chosen/alternative label pair with confidence values to ground the ambiguity-recording rule, which is currently stated only abstractly.

DimensionReasoningScore

Conciseness

The body is lean and imperative with zero padding — every sentence carries a rule the model couldn't infer ("Membership IDs and digests are navigation, not statements", "Choose exactly one area and every supported topic", "Never post a classification or ambiguity comment") and no concepts Claude already knows are explained. This matches the level-5 anchor (lean, assumes competence, every token earns its place) with nothing to trim for level 4.

5 / 5

Actionability

Guidance is mostly concrete for an instruction-only skill: named files and fields ("Read `packet.json`", "Record meaningful alternatives and medium/low confidence in `ambiguity`"), a named policy script, and a Quick reference table mapping needs to actions, with executable commands delegated to the reference. It falls short of level 5 because several directives remain judgment-level ("Stop when further reading is unlikely to change classification", "Expand relevant evidence to distinguish boundaries") and the body itself contains no commands — level 5 requires copy-paste-ready specifics, which only the referenced file supplies.

4 / 5

Workflow Clarity

The prepare → inspect → choose → write result → preview → apply sequence is legible through section order and the Quick reference table, and verification is present ("preview exact differences", "report verified/partial/prerequisite outcome", stale inputs require re-preparation per the reference), so the destructive-write cap does not apply. It sits at level 4 rather than 5 because the explicit step ordering, validate/fix/retry loop, and exit-code handling live in the reference while the body leaves the sequence implicit — the level-5 anchor expects explicit validation steps and feedback loops within the content.

4 / 5

Progressive Disclosure

The body is a genuine overview that cleanly splits content: commands and the result contract live one level deep in the well-signaled link "[commands and result contract](references/result-contract.md)" (verified to exist), while classification decision policy stays inline. This matches the level-5 anchor (clear overview, well-signaled one-level-deep references, appropriate split); the two `../../../` paths (CONTRIBUTING.md, label_issue_policy.py) point outside the bundle to repo-root files and are not nested skill references.

5 / 5

Total

18

/

20

Passed

Description

92%Weight 40%Scale 1-5

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

A strong description: it states concrete actions (classify, correct, migrate) with an explicit 'Use when' trigger clause scoped to a clearly named niche (OpenShell issue/PR area-topic labeling). The only minor gap is missing common synonyms like 'tag', 'triage', or 'categorize' that users might naturally say.

DimensionReasoningScore

Specificity

Quotes three concrete, distinct actions — "classifying an OpenShell issue or pull request", "correcting inaccurate area/topic labels", and "migrating obsolete, retired, or malformed classification associations" — which comprehensively cover the skill's niche, matching the level-5 anchor of multiple specific concrete actions with comprehensive coverage. It exceeds level 4 because the actions enumerate the skill's full range (initial classification, correction, and migration) rather than leaving minor gaps.

5 / 5

Completeness

Explicitly answers both questions: what it does (classify, correct, and migrate classification labels on OpenShell issues/PRs) and when to use it, opening with "Use when classifying an OpenShell issue or pull request, correcting inaccurate area/topic labels, or migrating..." with concrete trigger phrases. It meets the level-5 anchor (clear what AND when with concrete triggers) and beats the level-4 example whose 'when' clause ('Use when working with PDF files') is generic by comparison.

5 / 5

Trigger Term Quality

Natural trigger words are present — "classifying", "issue or pull request", "labels", "area/topic labels" — giving good coverage of what a user would say, but common synonyms such as "tag", "triage", or "categorize" are absent, matching level 4 (good coverage, a few natural terms missing) rather than level 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The description names a clear niche — OpenShell repository issue/PR classification with an area/topic label taxonomy — so it would rarely trigger for an unrelated skill, matching level 5 (clear niche with distinct triggers, minimal conflict risk). It is far more scoped than the level-4 anchor's broad 'PDF and Word document files' overlap risk.

5 / 5

Total

19

/

20

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 — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

relative_links

Relative link issues: 2 suspicious

Warning

Total

13

/

16

Passed

Repository

NVIDIA/OpenShell

Path

.agents/skills/label-issue/SKILL.md

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.