pick-copilot-tag

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

Quality

78%

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

100%

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

The content is concise, actionable, and well-structured, with concrete executable commands, a clear two-step workflow, and appropriate one-level-deep references to real bundle files. It is a strong, well-disclosed skill body.

Dimension	Reasoning	Score
Conciseness	The body is lean — terse flag listings, no padding with concepts Claude already knows, and explanatory detail correctly pushed to the reference file — so every token earns its place.	3 / 3
Actionability	Provides fully executable, copy-paste-ready invocations with concrete flags such as --app /Applications/Positron.app, --positron-version 2026.03.0, and --tag-series v0.37, plus combinations.	3 / 3
Workflow Clarity	A clear two-step sequence (run the check, report results) with the script's OK/BAD output serving as the explicit validation feedback loop; being a read-only diagnostic, no destructive-operation cap applies.	3 / 3
Progressive Disclosure	Well-organized sections with one-level-deep references to a real scripts/check-proposals.sh and a real references/proposal-compatibility.md that holds the deeper reasoning, matching the actual bundle structure.	3 / 3
	Total	12 / 12 Passed

Description

57%

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 but is missing an explicit "Use when..." trigger clause and lists only a single action, leaving trigger coverage and completeness at the midpoint. Adding trigger conditions and a second concrete action would raise it.

Suggestions

Append a 'Use when...' clause listing 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.'

Name an additional concrete action, e.g. '...and report which proposals changed and the latest compatible tag.'

Include common trigger term variants (copilot-chat tag, API proposals not compatible, merge copilot-chat).

Dimension	Reasoning	Score
Specificity	Quotes "Determine which vscode-copilot-chat release tag to use" and "for a Positron build" — names the domain and one concrete action, but lists only a single action rather than multiple specific actions, so it falls short of level 3.	2 / 3
Completeness	Answers "what" (determine which release tag to use) but provides no "Use when..." trigger clause, so per the guidelines completeness is capped at 2.	2 / 3
Trigger Term Quality	"vscode-copilot-chat release tag" and "Positron build" are natural terms a user would say, but coverage of common variations (copilot-chat, API proposals, not compatible, merge, upgrade) is incomplete.	2 / 3
Distinctiveness Conflict Risk	The niche of coupling a specific Positron build to a specific vscode-copilot-chat tag is clear and unlikely to trigger for unrelated skills.	3 / 3
	Total	9 / 12 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: b87c504

Reviewed: 2 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.