CtrlK
BlogDocsLog inGet started
Tessl Logo

label-core-bugs

Review open mastra-ai/mastra GitHub issues, identify direct @mastra/core bugs, and apply the @mastra/core label. Use when auditing issues for core ownership, labeling direct core bugs, or periodically reconciling the @mastra/core issue label.

77

Quality

96%

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

100%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 excellent, tightly written SKILL.md body: executable commands, a clearly sequenced workflow with validation checkpoints appropriate for a batch/mutating GitHub operation, and clean section structure. No meaningful weaknesses to address.

DimensionReasoningScore

Conciseness

Lean and efficient with no padding or explanation of concepts Claude already knows; every line is actionable guidance or an executable command that earns its place.

5 / 5

Actionability

Fully executable, copy-paste-ready `gh` commands with jq verification cover the common cases (auth check, label create/list, issue view, label add, label verification).

5 / 5

Workflow Clarity

A clear five-step sequence with explicit validation checkpoints — dry-run must not mutate state, verify the label was applied, stale-claim detection, and report false positives / fixed-awaiting-closure — providing feedback loops for this destructive/batch operation.

5 / 5

Progressive Disclosure

A compact single-purpose skill under 50 lines with no external bundle files; its well-organized Inputs/Classification/Workflow/Output sections satisfy the simple-skill exception for progressive disclosure.

5 / 5

Total

20

/

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, specific description that concretely states what it does and when to use it, with minimal conflict risk. The only minor gap is trigger-term variety, which leans on project-specific jargon rather than broader natural synonyms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Review open mastra-ai/mastra GitHub issues', 'identify direct @mastra/core bugs', and 'apply the @mastra/core label' — with comprehensive coverage of the skill's scope.

5 / 5

Completeness

Clearly answers 'what' (review, identify, label) and explicitly answers 'when' via a concrete 'Use when auditing issues for core ownership, labeling direct core bugs, or periodically reconciling...' clause.

5 / 5

Trigger Term Quality

Natural phrases like 'auditing issues for core ownership', 'labeling direct core bugs', and 'reconciling the @mastra/core issue label' are present, but the terms lean on the specialized '@mastra/core' jargon and miss a few common synonyms a user might say.

4 / 5

Distinctiveness Conflict Risk

Targets a narrow, well-defined niche (mastra-ai/mastra core bug labeling) with distinct triggers, so it is unlikely to fire for the wrong skill.

5 / 5

Total

19

/

20

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
mastra-ai/mastra
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.