pick-copilot-tag

Determine which vscode-copilot-chat release tag to use for a Positron build

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/pick-copilot-tag/SKILL.md

Quality

Content

96%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 concise, highly actionable, and presents a clear two-step workflow with validation baked into the script, supported by a concrete example. The only gap is that the bundled reference doc explaining proposal compatibility is not linked from the overview.

Suggestions

Add a one-line pointer to references/proposal-compatibility.md (e.g. under a 'Background' note) so the bundled explanation is discoverable from the overview.

Optionally note what to report when no compatible tag is found, to round out the 'Report Results' step for the failure case.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-organized with no over-explanation of concepts Claude already knows; sections (When to Use, Prerequisites, Workflow, Example Output) each earn their place and the prose only describes what the script does. It matches the lean-and-efficient anchor rather than the minor-over-explanation anchor below.	5 / 5
Actionability	It provides copy-paste-ready executable commands with multiple flag combinations and a concrete example output, covering the common cases. This matches the fully-executable anchor; it is above score 4 because the examples are complete rather than having minor gaps.	5 / 5
Workflow Clarity	The two-step sequence (run the check, then report results) is unambiguous, and the script itself emits per-tag OK/BAD validation with specific mismatches, so validation is built into the tool. As a simple single-purpose diagnostic skill, this meets the simple-skill exception; it is not a destructive/batch operation requiring a fix-retry loop.	5 / 5
Progressive Disclosure	Structure is good: the script path is clearly signaled and invoked inline, and the body is a concise overview. However the bundled references/proposal-compatibility.md (which explains the compatibility mechanism in depth) is not linked from the body, a minor organization gap that keeps it below the well-signaled-references anchor of 5.	4 / 5
	Total	19 / 20 Passed

Description

57%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 specific and clearly distinct, naming a precise niche and a concrete action, but it lacks any explicit 'when to use' trigger guidance and offers only one action. Adding a 'Use when...' clause with natural trigger phrases would lift completeness and trigger-term quality.

Suggestions

Add a 'Use when...' clause naming concrete triggers, e.g. 'Use when a Positron release rejects copilot-chat with API proposals not compatible, or when upgrading copilot-chat after a Code OSS update.'

Include natural synonyms users would say, such as 'copilot tag' or 'copilot-chat version', alongside 'release tag'.

Optionally list a second concrete action (e.g. 'identifies which API proposals changed') to broaden the specificity coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (vscode-copilot-chat release tag for a Positron build) and one concrete action ("Determine which...release tag to use"), but lists only a single action rather than several. It is above score 2 (not minimal/generic) but below 4 (no list of several specific actions).	3 / 5
Completeness	It clearly answers 'what' (determine which release tag to use) but provides no 'Use when...' clause or explicit trigger guidance in the description, so per the missing-trigger cap it cannot exceed 3. The 'when' is only weakly implied.	3 / 5
Trigger Term Quality	Relevant keywords like "vscode-copilot-chat", "release tag", and "Positron build" are present and natural for this niche, but common variations/synonyms (e.g. "copilot version", "copilot tag") are missing. It fits the 'some relevant keywords but missing variations' anchor better than the sparse/generic anchor below.	3 / 5
Distinctiveness Conflict Risk	The phrase "vscode-copilot-chat release tag to use for a Positron build" carves out a highly specific niche with distinct triggers and minimal overlap with other skills, matching the clear-niche anchor.	5 / 5
	Total	14 / 20 Passed

Validation

100%

Warnings & errors only

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: posit-dev/positron
Path: .claude/skills/pick-copilot-tag/SKILL.md
Commit: 75a1182

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.