CtrlK
BlogDocsLog inGet started
Tessl Logo

sync-upstream

Update a stale session branch by rebasing onto the latest origin. Use when the upstream has moved significantly and the session needs to catch up, resolving conflicts by preserving upstream changes and adapting session work to fit.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

A concise, actionable single-purpose skill with executable git commands, a clear multi-step workflow including conflict-resolution and validation checkpoints, and well-organized sections. It assumes Claude's competence and adds only what is needed.

DimensionReasoningScore

Conciseness

Lean ~25-line body with no concept explanations of git/rebase; assumes Claude's competence and lets every line earn its place.

3 / 3

Actionability

Provides copy-paste-ready, executable commands ('git fetch origin', 'git rebase origin/main', 'git add', 'git rebase --continue'); conflict-resolution prose is necessarily contextual but the commands are concrete.

3 / 3

Workflow Clarity

Clear sequenced workflow (commit uncommitted changes → fetch & rebase → resolve conflicts → validate) with an explicit conflict-resolution loop and a Validation checkpoint; not capped at 2 because validation is present for this risky rebase operation.

3 / 3

Progressive Disclosure

Under 50 lines with no need for external references, organized into clearly labeled sections (Workflow, Conflict Resolution, Validation), matching the simple-skills allowance for a top score.

3 / 3

Total

12

/

12

Passed

Description

100%

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 well-crafted description using third-person voice that clearly pairs concrete actions with an explicit 'Use when' trigger and natural terminology. It is specific, complete, and distinct without padding or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'rebasing onto the latest origin', 'resolving conflicts by preserving upstream changes', and 'adapting session work to fit' — rather than vague language.

3 / 3

Completeness

Clearly states both what it does ('Update a stale session branch by rebasing onto the latest origin...') and when to use it via an explicit 'Use when' clause; not 2 because the trigger is explicit rather than implied.

3 / 3

Trigger Term Quality

Covers natural user phrasing such as 'stale session branch', 'catch up', 'upstream has moved', and 'rebasing', which a developer would plausibly say when needing this skill.

3 / 3

Distinctiveness Conflict Risk

Carves a distinct sync/rebase niche tied to stale session branches catching up to upstream, unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
posit-dev/positron
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.