CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

branch-sync-and-push-safety

Use when changing local branch synchronization, custody recovery, post-review head binding, rebasing or rebase.strategy, private-mirror reconciliation, or force-push safety.

Quality

54%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/branch-sync-and-push-safety/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

This is a high-signal internal invariants map: every rule names its owning file/function and guarding regression tests, and the fail-closed validation posture is consistent and explicit. Its weaknesses are form, not substance — extremely dense run-on prose with inlined test-name lists, no followable workflow, and all detail living inline in SKILL.md instead of being split into per-topic reference files.

Suggestions

Split each bolded section (branchsync, push binding, force-push safety, rebase.strategy, private mirrors) into its own reference file, leaving SKILL.md as a one-screen index of invariants plus pointers — the body is ~22KB of dense material that belongs in progressively disclosed files.

Replace the long inline 'Regressions:' test-name lists with a single pointer to the owning test file (e.g. 'see internal/branchsync/recover_test.go') — the names are re-discoverable in the file and cost hundreds of tokens inline.

Break the multi-clause run-on bullets (some exceed 150 words) into short imperative rules, and add a short ordered 'when touching these files, check these invariants' checklist so the skill has a followable workflow shape.

DimensionReasoningScore

Conciseness

The body is a ~22KB wall of dense run-on bullets, with entire regression-test name lists inlined inline (e.g. 'Regressions: TestRefreshSlowSuccessfulLsRemoteDoesNotStealFetchBudget, TestRefreshSlowButSuccessfulLsRemoteAloneExceedsItsOwnBudgetReportsOffline, ...') that belong in the test files they name. It does not explain concepts Claude already knows (all facts are project-internal), so it is noticeably padded rather than anchor-1 'severely verbose with known-concept explanations'.

2 / 5

Actionability

Concrete, executable guidance throughout: exact git operations ('an atomic update-ref CAS plus read-tree -m -u, never check-then-act followed by reset --hard'), exact owners ('recoverAdoptPreserved owns the reasoning', 'Public guidance is owned by internal/skill/skill.go'), named config knobs with defaults ('Service.RemoteTimeout... default config.DefaultBranchSyncRemoteTimeout, 60s'), and explicit prohibitions ('do not unify the two prompts'). As an instruction-only skill the absence of code blocks is not penalized; minor gaps (no worked example of the relation matrix) keep it below 5.

4 / 5

Workflow Clarity

The skill is an invariants/reference document rather than a sequenced process, and no followable multi-step workflow is presented — sections describe rules and evidence shapes, not an ordered procedure. Validation/fail-closed behavior is stated emphatically ('rechecks... immediately before apply', 'fail closed with manual reconciliation'), so checkpoints exist conceptually, but the sequence itself is implicit, matching anchor 3 rather than 4.

3 / 5

Progressive Disclosure

There are clear bolded section headers and one-level-deep pointers into the repo ('The full relation matrix and fail-safe rules live in the Recover doc comment in internal/branchsync/sync.go', 'owned by docs/src/content/docs/concepts/gate-model.md'), and no bundle files exist to reference. However, the sheer bulk of dense per-subsystem material (~22KB inline) clearly belongs in split reference files, which caps it at anchor 3 ('content that should be separate is inline') rather than 4.

3 / 5

Total

12

/

20

Passed

Description

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

The description functions well as a precise 'when' trigger for an internal skill but completely omits the 'what' — it never states what the skill does or contains. Domain terms are specific and distinctive, though heavy on internal jargon and light on natural user phrasings. Adding a one-clause capability statement would lift completeness and specificity substantially.

Suggestions

Prepend a concrete capability clause, e.g. 'Holds the invariants and regression map for internal/branchsync, force-push, and gate reconciliation changes. Use when...' so both 'what' and 'when' are explicit.

Add natural trigger synonyms alongside the internal jargon (e.g. 'force push', 'git branch sync', 'push safety') so the description matches how users actually phrase these needs.

Trim internal-only vocabulary like 'post-review head binding' or pair each jargon term with a plain-language gloss so the trigger reads naturally rather than as a code-symbol list.

DimensionReasoningScore

Specificity

The description names specific domains ("local branch synchronization, custody recovery, post-review head binding, rebasing or rebase.strategy, private-mirror reconciliation, or force-push safety") but lists no concrete actions or capabilities — it is purely a trigger list with no 'what this skill does'. Matches anchor 2 (names the domain, minimal/generic actions); not 3 because zero concrete actions are stated, not 1 because the domains are specific rather than abstract filler.

2 / 5

Completeness

The description is a single "Use when changing..." clause — 'when' is explicit and detailed, but 'what the skill does' is entirely absent, matching anchor 2 (only 'when' present without 'what'). Not 3 because the 'what' is not even weakly implied by any capability statement; not 1 because the 'when' half is specific and explicit.

2 / 5

Trigger Term Quality

Includes some natural terms a maintainer would say ("rebasing", "force-push safety", "branch synchronization") but mixes in internal jargon ("custody recovery", "post-review head binding", "private-mirror reconciliation") and misses common variations/synonyms like "force push", "git sync", or "push safety". Fits anchor 3 (relevant keywords, missing common variations); not 4 because several natural phrasings are absent and much of the vocabulary is project-internal.

3 / 5

Distinctiveness Conflict Risk

Distinctive niche phrases like "rebase.strategy", "private-mirror reconciliation", and "post-review head binding" are unique to this project's domain, giving minimal conflict risk overall. Minor overlap remains with general git skills via broad terms like "rebasing" and "branch synchronization" — anchor 4 (mostly distinct, minor overlap with closely related skills); not 5 because those generic git terms could pull triggers away from a general git skill or vice versa.

4 / 5

Total

11

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

kunchenguid/no-mistakes

Path

.agents/skills/branch-sync-and-push-safety/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.