CtrlK
BlogDocsLog inGet started
Tessl Logo

update-from-upstream-main

Update the current Remotion branch with the latest canonical main branch. Use when asked to update or sync from upstream main, merge the latest main into a feature branch, fast-forward local main, or bring a pull request branch up to date without rewriting published history.

76

Quality

95%

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

An exemplary single-purpose git workflow skill: concise, fully executable, with explicit validation checkpoints and feedback loops for the destructive merge/stash operations. Structure is appropriately self-contained for a short, single-task skill with no need for external references.

DimensionReasoningScore

Conciseness

Lean throughout: each step pairs a single intent with one executable git command and a tight constraint ('Do not rebase, reset, or force-push', 'Never force-push'); assumes Claude's competence with no padding or background explanation.

5 / 5

Actionability

Every step supplies concrete, executable git commands (git stash push --include-untracked, git fetch <canonical-remote> main, git merge --ff-only, rg -n conflict markers, git stash apply --index, bun run build) covering the common cases copy-paste ready; placeholders are explicitly justified.

5 / 5

Workflow Clarity

A clearly sequenced 9-step process with explicit validation checkpoints (stop if merge in progress, rg conflict-marker check before staging, git diff --check / --cached --check, bun build & stylecheck) and error-recovery feedback loops (resolve conflicts deliberately then git commit --no-edit; reapply stash before reporting success even on failure).

5 / 5

Progressive Disclosure

No bundle files exist; the skill is under 50 lines and well-organized into numbered workflow steps with clear section headers, satisfying the simple-skill exception for a top score without external references.

5 / 5

Total

20

/

20

Passed

Description

90%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, concrete description with explicit what-and-when structure and rich natural trigger phrases tightly scoped to the upstream-sync task. Slightly less exhaustive in listing actions than a model 5 for specificity, but otherwise excellent.

DimensionReasoningScore

Specificity

Names several concrete actions ('merge the latest main into a feature branch', 'fast-forward local main', 'bring a pull request branch up to date'), with minor gaps such as the canonical-remote selection and stash handling not surfaced; comprehensive but slightly short of the full anchor 5 list.

4 / 5

Completeness

Explicitly answers 'what' ('Update the current Remotion branch with the latest canonical main branch') and 'when' via a concrete 'Use when...' clause enumerating multiple trigger scenarios.

5 / 5

Trigger Term Quality

Covers natural phrases users say — 'update or sync from upstream main', 'merge the latest main into a feature branch', 'fast-forward local main', 'bring a pull request branch up to date' — with synonyms and specific git terms comprehensively represented.

5 / 5

Distinctiveness Conflict Risk

Clear narrow niche (syncing from remotion-dev/remotion upstream main without rewriting history) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

19

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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