CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

positron-pull-vscode-server

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

Quality

90%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A dense, highly actionable skill body: executable commands and templates for every step, explicit validation with feedback loops, and purely repo-specific knowledge with no filler. The main improvement opportunities are moving the Step-5 PR-body formatting rules to a reference file and tightening the repeated baseline-merge guidance.

DimensionReasoningScore

Conciseness

Nearly every passage carries non-obvious domain knowledge (PWB marker rules, version/distro baseline parity, `gh repo set-default` failure mode, watch-client daemon behavior) and assumes Claude's competence. Not 5 because a few passages run long — the QA-tag routing paragraph and the baseline-merge guidance repeated across Steps 1 and 1b could be tightened.

4 / 5

Actionability

Copy-paste-ready commands throughout: remote setup with `git remote set-url --push upstream DISABLE`, `enumerate-upstream.sh <baseline-sha>`, `git rev-parse upstream/main`, build/verify commands, a commit-message template, a PR-body table template, and a `gh pr list` fallback for when the script can't reach gh. Templates cover the common cases completely.

5 / 5

Workflow Clarity

Steps 1–6 are explicitly sequenced with an explicit validation checkpoint in Step 4 (build-ps, build-check, precommit) plus error-recovery loops: start daemons before trusting build-check, ignore pre-existing errors in untouched files, and drop unrelated churn with `git checkout -- <file>`. The batch triage in Step 1b includes checkpoints and a user-confirmation gate before scoping.

5 / 5

Progressive Disclosure

Good structure: both scripts are referenced by full path and exist in the bundle, references are one level deep and clearly signaled, and PR creation is delegated to the positron-pr-helper skill. Not 5 because the ~155-line body inlines the PR-body formatting and reference rules (~30 lines used only in Step 5) that could live in a references/ file, and no reference split exists.

4 / 5

Total

18

/

20

Passed

Description

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

A strong description: concrete gerund-phrase actions, an explicit 'Use when' trigger naming both repositories, and a distinct niche. The only gaps are missing synonym variations (port/sync) and unmentioned later workflow stages (verification, PR creation).

DimensionReasoningScore

Specificity

"fetching upstream, triaging commits, and applying diffs" lists three concrete, specific actions. Not 5 because the workflow also encompasses build verification and PR creation, which the description omits — minor coverage gaps rather than comprehensive.

4 / 5

Completeness

Explicitly answers both: the what ("fetching upstream, triaging commits, and applying diffs") and a concrete when-trigger ("Use when pulling changes from rstudio/vscode-server into Positron"), matching the anchor-5 pattern of actions plus a specific 'Use when' clause.

5 / 5

Trigger Term Quality

"pulling changes", "upstream", and the concrete repo names "rstudio/vscode-server" and "Positron" are natural phrases a user would say. Not 5 because common synonyms like "port", "sync", or "upstream merge" are absent.

4 / 5

Distinctiveness Conflict Risk

Naming both repos ("rstudio/vscode-server", "Positron") carves out a clear niche with distinct triggers; virtually no overlap risk with other skills.

5 / 5

Total

18

/

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

posit-dev/positron

Path

.claude/skills/positron-pull-vscode-server/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.