CtrlK
BlogDocsLog inGet started
Tessl Logo

agentic-labeler

Labels issues and pull requests in the dotnet/maui repository with `area-*` and `platform/*` labels ONLY, based on technical content and platform-file conventions. Used by the gh-aw agentic-labeler workflow and available for batch evaluation and interactive Copilot CLI usage.

58

Quality

66%

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

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/agentic-labeler/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

The body is a thorough, highly actionable rulebook with concrete label mappings and tie-breaking heuristics, well suited to its instruction-only purpose. It is held back by repetition (Tizen, scope prohibitions) and the absence of a sequenced workflow with a verification step for batch labeling.

Suggestions

Consolidate the Tizen exclusion and the 'do not apply other labels' prohibition into one authoritative section and reference it elsewhere instead of restating 4+ times.

Add a short numbered labeling workflow ending in a verification step (e.g. confirm applied labels via get_label) to support batch usage and lift workflow clarity.

Move the long area-* taxonomy and platform file-pattern table into a separate reference file, keeping SKILL.md as a concise overview with a one-level-deep pointer.

DimensionReasoningScore

Conciseness

Most of the body is dense repo-specific taxonomy Claude genuinely lacks, but the Tizen exclusion is repeated 4+ times and the 'What NOT to do' section largely restates the top 'Scope' section, so it is mostly efficient with some unnecessary repetition rather than fully lean.

2 / 3

Actionability

It gives concrete label names, a file-pattern-to-platform mapping table, and worked examples (e.g. 'CollectionView -> area-controls-collectionview'); for an instruction-only skill this is specific, copy-applicable guidance rather than the abstract or pseudocode level.

3 / 3

Workflow Clarity

Rules and some checkpoints exist (verify with get_label before adding, the noop decision), but the content is a rulebook rather than a sequenced workflow, and batch labeling has no explicit verification of applied labels, which caps workflow clarity at 2 per the batch-operations guideline.

2 / 3

Progressive Disclosure

The single file is well-organized with clear sections and avoids nested references, but it is a ~120-line monolith where the detailed label taxonomy and platform table could be split into a one-level-deep reference file; no progressive disclosure is actually employed.

2 / 3

Total

9

/

12

Passed

Description

67%

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 and distinctive, clearly scoping the skill to labeling dotnet/maui issues and PRs with area-* and platform/* labels. Its main weakness is the absence of an explicit 'Use when...' trigger, leaving the activation condition only implied.

Suggestions

Add an explicit 'Use when...' clause naming natural user triggers, e.g. 'Use when labeling or triaging issues and PRs in dotnet/maui, or when the user asks to apply area/platform labels.'

Trim the mechanism jargon in the second sentence ('gh-aw agentic-labeler workflow', 'Copilot CLI') in favor of plain trigger terms a user would actually say.

DimensionReasoningScore

Specificity

The description lists concrete actions ('Labels issues and pull requests...with `area-*` and `platform/*` labels ONLY, based on technical content and platform-file conventions') on a clearly named domain, matching the multiple-specific-actions anchor rather than the single-action level 2.

3 / 3

Completeness

The 'what' is explicit, but the 'when' is only implied via consumption context ('Used by the gh-aw agentic-labeler workflow and available for batch evaluation and interactive Copilot CLI usage') with no 'Use when...' trigger clause, which per the guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

It includes relevant natural terms ('issues', 'pull requests', 'labels'), but the second sentence leans on mechanism jargon ('gh-aw agentic-labeler workflow', 'batch evaluation', 'Copilot CLI') rather than common user-facing variations, so it sits at 'some relevant keywords but missing common variations'.

2 / 3

Distinctiveness Conflict Risk

It is tightly scoped to the dotnet/maui repository and two specific label families, giving it a clear niche unlikely to trigger for the wrong skill; it does not sit at the 'could still overlap' level 2.

3 / 3

Total

10

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
dotnet/maui
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.