CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

release-plugin

Prepare and execute a new release for the flutter-intellij plugin, including updating dependencies, compatibility bounds, changelogs, and verification.

Quality

75%

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 ./.agents/skills/release-plugin/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 body is a well-structured, actionable release runbook with concrete commands and validation checkpoints, scoring consistently strong across dimensions with only minor gaps in feedback-loop explicitness and a couple of trimming opportunities.

Suggestions

Add explicit feedback loops after each validation command (e.g. 'If testClasses fails, fix compile errors before proceeding') to lift workflow clarity.

De-duplicate the './gradlew testClasses' instruction between sections 2 and 4 to tighten conciseness.

Consider extracting the manual-testing checklist into a references file and linking to it from the body to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is mostly lean and assumes Claude's competence, using concrete commands rather than explaining concepts, but contains minor redundancy (e.g. './gradlew testClasses' appears in both section 2 and section 4) and some padded parentheticals that could be trimmed.

4 / 5

Actionability

Provides concrete, executable commands (curl|jq for version lookup, specific ./gradlew tasks, ./tool/update_baselines.sh) and a copy-ready changelog template, but the Google Drive upload step is manual/vague ('Manually upload... to the team's Google Drive folder'), leaving a minor gap.

4 / 5

Workflow Clarity

A clear 5-step sequence with explicit validation checkpoints (testClasses, verifyPluginStructure, test) and a manual-testing checklist, but it lacks explicit feedback loops ('if validation fails, fix and re-run') for the release's batch/destructive operations.

4 / 5

Progressive Disclosure

Content is well-organized into clearly headed sections and is appropriately self-contained for a release runbook with no bundle files present, though the manual-testing checklist and changelog template could arguably live in separate reference files.

4 / 5

Total

16

/

20

Passed

Description

62%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 clearly conveys what the skill does and is well-scoped to a specific plugin, but it omits any explicit 'Use when...' trigger guidance, which caps its completeness and weakens trigger-term quality.

Suggestions

Append an explicit trigger clause, e.g. 'Use when releasing a new version of the flutter-intellij plugin or when the user asks to cut a plugin release.'

Add natural synonyms users might say (e.g. 'cut a release', 'bump plugin version', 'publish plugin') to improve trigger-term coverage.

Mention the build-artifact and manual-testing outcomes to lift specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions — 'updating dependencies, compatibility bounds, changelogs, and verification' — but the actions are somewhat high-level and omit build-artifact/manual-testing steps, so it falls short of comprehensive (5).

4 / 5

Completeness

Provides a clear 'what' (prepare and execute a release with dependency/compatibility/changelog/verification updates) but no 'when' clause; per the judging guideline, a missing 'Use when...' trigger caps completeness at 3.

3 / 5

Trigger Term Quality

Contains relevant terms like 'release' and 'new release' for the flutter-intellij plugin, but lacks common synonyms or variations and has no explicit 'Use when...' trigger phrasing, leaving natural keyword coverage incomplete.

3 / 5

Distinctiveness Conflict Risk

Scoped to a named product ('flutter-intellij plugin') with release-specific triggers, giving it a clear niche with minimal overlap risk against other skills.

5 / 5

Total

15

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

flutter/flutter-intellij

Path

.agents/skills/release-plugin/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.