positron-pull-vscode-server

Use when pulling changes from rstudio/vscode-server into Positron — fetching upstream, triaging commits, and applying diffs

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

85%

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

A well-structured, highly actionable porting workflow with strong sequencing and validation checkpoints, and bundle scripts correctly referenced one level deep. The only weakness is moderate verbosity in the PR-body formatting and baseline-parity sections.

Suggestions

Tighten the Step 5 PR-body reference rules: the ul/li-in-table guidance and fully-qualified-reference rules could be condensed into a compact checklist.

The version/distro parity explanation in Step 1 is thorough but lengthy; consider moving the extended rationale into a brief rule plus a one-line example.

Dimension	Reasoning	Score
Conciseness	The body is information-dense and never explains concepts Claude already knows, but the Step 5 PR-body reference rules and the version/distro parity explanation are elaborate and could be tightened without losing clarity, placing it at the mostly-efficient-but-could-be-tighter anchor rather than 3.	2 / 3
Actionability	It provides copy-paste-ready executable commands throughout — script invocations, `git rev-parse upstream/main`, `npm run build-ps`, `git show <upstream-SHA>`, a full `git commit -m` template, and a concrete `gh pr list` command — fully actionable.	3 / 3
Workflow Clarity	A clearly numbered Step 1→6 sequence with explicit validation checkpoints (`build-check`, `precommit`, "verify the files you ported compile clean"), error-recovery guidance (start daemons, fix only touched lines), and a Common Mistakes table — satisfying the explicit-validation anchor.	3 / 3
Progressive Disclosure	SKILL.md is an overview that signals one-level-deep external helpers — `scripts/enumerate-upstream.sh` and `scripts/check-backlog.sh` — both of which exist in the bundle at the referenced paths, with no nested references.	3 / 3
	Total	11 / 12 Passed

Description

85%

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 concise, well-scoped description with an explicit Use-when trigger and concrete named actions. Its only gap is narrow trigger-term coverage — a single phrase with no common synonyms a user might say.

Suggestions

Broaden trigger coverage with natural synonyms a user might actually say, e.g. "Use when porting or syncing upstream vscode-server changes into Positron".

Keep the action list but consider mirroring the trigger phrasing users tend to use ("pull", "port", "sync") so model invocation matches more query variants.

Dimension	Reasoning	Score
Specificity	Lists three concrete actions — "fetching upstream, triaging commits, and applying diffs" — rather than vague abstractions, matching the multi-action anchor.	3 / 3
Completeness	Explicitly answers both what ("fetching upstream, triaging commits, and applying diffs") and when ("Use when pulling changes from rstudio/vscode-server into Positron") via an explicit "Use when" clause.	3 / 3
Trigger Term Quality	The single trigger "Use when pulling changes from rstudio/vscode-server into Positron" is natural, but there is essentially one trigger phrase with no common variations (e.g. "port", "sync", "merge upstream"), so it sits at the some-keywords-but-missing-variations anchor rather than 3.	2 / 3
Distinctiveness Conflict Risk	The niche is sharply scoped to porting rstudio/vscode-server commits into Positron, a distinct trigger unlikely to fire for any other skill.	3 / 3
	Total	11 / 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/positron-pull-vscode-server/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.