CtrlK
BlogDocsLog inGet started
Tessl Logo

major-version-mode

Context for working on the next AI SDK major release. Only use when explicitly invoked by the user (e.g. via '/major-version-mode'). Do NOT trigger autonomously based on task content.

64

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/major-version-mode/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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.

The content is a well-structured, token-efficient policy skill with concrete file references, a real code example, and explicit user-check gates on the riskiest decisions. It assumes Claude's competence and avoids padding throughout.

DimensionReasoningScore

Conciseness

The body is lean and gives rules without re-explaining concepts Claude knows, citing exact file paths; a few explanatory clauses (e.g. why content-part.ts retains old shapes) could be trimmed.

4 / 5

Actionability

It provides a concrete deprecated-alias code snippet and exact files/locations (provider-utils types, content-part.ts, migration-guide dir); much guidance is conditional policy, but it stays specific and actionable with only minor gaps.

4 / 5

Workflow Clarity

The modified-message-types flow is a clear 3-step sequence and "check with the user first" acts as explicit gating checkpoints; it lacks formal validate->fix->retry feedback loops but those don't fit this policy skill.

4 / 5

Progressive Disclosure

The body is self-contained (~50 lines) with no bundle files present and no need for external references; sections are clearly headed and well-organized, meeting the simple-skill exception.

5 / 5

Total

17

/

20

Passed

Description

77%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.

The description is highly clear about when to invoke (explicit-only, via /major-version-mode) and distinct from other skills, but it frames itself as context rather than concrete capabilities, leaving the action list implicit. Strengthening specificity would round it out.

DimensionReasoningScore

Specificity

It names the domain ("next AI SDK major release") but describes a mode/context rather than listing concrete capability actions; the concrete actions live in the body, not the description.

2 / 5

Completeness

It explicitly answers both what ("context for working on the next AI SDK major release; breaking changes acceptable") and when ("only use when explicitly invoked by the user; do NOT trigger autonomously") with a concrete trigger.

5 / 5

Trigger Term Quality

It surfaces the natural trigger phrase "explicitly invoked by the user (e.g. via '/major-version-mode')", which is exactly how a user would invoke this; a few synonyms are absent.

4 / 5

Distinctiveness Conflict Risk

The skill is explicitly gated to manual invocation and forbids autonomous triggering, giving it a clear niche with minimal conflict risk.

5 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation — 14 / 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

Total

14

/

16

Passed

Repository
vercel/ai
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.