sync

Sync the current session branch with its upstream branch, or publish the current session branch to a remote. Use when the user asks to sync a branch, pull latest changes, rebase onto upstream, push current branch, publish branch, or set upstream.

Quality

91%

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

Quality

Content

92%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 well-structured, actionable skill body with concrete git commands, explicit validation checkpoints, and clear error-recovery feedback loops. The only notable blemish is a duplicated description line and a template HTML comment that slightly reduce conciseness.

Suggestions

Remove the verbatim duplicate of the frontmatter description in the opening body paragraph (line 9) to save tokens and avoid redundancy.

Delete the leftover "Customize this skill and select save to override its behavior..." HTML comment template artifact.

Consider collapsing the four separate Guidelines bullets into the Workflow steps where they apply (e.g. the force-push approval gates), to tighten the document further.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes git competence (no concept explanations), but the opening paragraph duplicates the frontmatter description verbatim and a leftover "Customize this skill" HTML comment adds noise; efficient yet trimmable, so a 4 rather than 5.	4 / 5
Actionability	Every step gives copy-paste-ready commands with explicit placeholders (e.g. `git rebase @{u}`, `git push -u <remote> HEAD`, `git rev-list --left-right --count HEAD...@{u}`) covering the common sync and publish cases, matching the fully-executable top anchor.	5 / 5
Workflow Clarity	A clearly numbered workflow with an explicit Validation section (clean tree, 0/0 ahead-behind, upstream configured) and feedback loops for conflict recovery (resolve -> continue, or --abort); despite destructive rebase/push steps, validation is present so the destructive-cap does not apply.	5 / 5
Progressive Disclosure	Content is self-contained with no external references needed and is well organized into Guidelines, Workflow, and Validation sections; per the simple-skill exception, a self-contained skill with no need for external files and clear sectioning scores at the top.	5 / 5
	Total	19 / 20 Passed

Description

91%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, third-person description that clearly states what the skill does and when to use it, with natural trigger phrases. It is comprehensive on triggers and completeness, with only minor room for improvement on specificity and distinctiveness.

Dimension	Reasoning	Score
Specificity	"Sync the current session branch with its upstream branch, or publish the current session branch to a remote" names the domain plus several concrete actions (sync, pull, rebase, push, publish, set upstream), with only minor coverage gaps; not a 5 because the actions cluster around two main operations rather than a broad comprehensive list.	4 / 5
Completeness	It explicitly answers both what ("Sync ... or publish ... to a remote") and when ("Use when the user asks to sync a branch, pull latest changes...") with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	"sync a branch, pull latest changes, rebase onto upstream, push current branch, publish branch, or set upstream" provides comprehensive natural phrases with synonyms users would actually say; not below 5 since common variations are well covered.	5 / 5
Distinctiveness Conflict Risk	The "session branch / upstream branch" framing carves a clear git-workflow niche with minimal conflict risk, though it could overlap slightly with a generic git skill; not a 5 because the trigger set is git-generic enough to risk minor overlap.	4 / 5
	Total	18 / 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: src/vs/sessions/skills/sync/SKILL.md
Commit: 9bb0f27

Reviewed: about 21 hours 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.