CtrlK
BlogDocsLog inGet started
Tessl Logo

pensieve-sync-to-main

Sync Pensieve's Chinese development/release branch into the English main branch. Use in the Pensieve repository when the user asks to sync zh or experimental to main, publish the English branch, translate Pensieve README/tool specs/templates/SKILL.md, or run the zh-to-main release flow. Do not use for ordinary project localization or generic i18n.

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 well-crafted maintainer-workflow skill: lean, fully actionable with executable commands, a clearly sequenced workflow with validation checkpoints and error-recovery fallbacks, and clean section organization. It aligns with the good-example patterns and avoids the common padding and vague-direction pitfalls.

DimensionReasoningScore

Conciseness

The body is lean and action-dense with no tutorializing of git or translation concepts Claude already knows — e.g. 'git merge kingkongshot/<source-branch> -X theirs --no-edit' and 'Translate all Chinese prose into English.' are stated directly. The brief intro framing earns its place rather than padding, matching the lean-and-efficient anchor.

3 / 3

Actionability

Fully executable commands with flags and clearly marked placeholders — 'git checkout -b sync/zh-to-main-<date>[-topic]', "rg -n --pcre2 '\p{Han}' README.md SKILL.md .src docs", 'gh pr create --repo kingkongshot/Pensieve --base main --head ...'. Copy-paste ready, matching the top anchor.

3 / 3

Workflow Clarity

A clearly sequenced four-step workflow (Confirm scope, Create sync branch, Translate, Validate/commit/PR) with explicit validation checkpoints (the \p{Han} check, 'git diff --check', 'report them before switching branches') and Failure Fallback feedback loops such as 'Push rejected: fetch, rebase the sync branch onto latest kingkongshot/main, then retry.' Validation is present for destructive/batch operations, so workflow_clarity is not capped at 2.

3 / 3

Progressive Disclosure

Self-contained with no bundle files present; the body is organized into clear, navigable sections (Hard Rules, Branch Strategy, Translation Scope, Workflow, Failure Fallback) with no nested references. For a focused single-workflow skill, keeping it in one well-sectioned file is appropriate organization rather than a monolithic wall of text.

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 high-quality description: concrete actions, explicit 'Use when ...' triggers tied to natural maintainer phrasings, and a clear negative-scope clause that reduces conflict risk. It closely follows the good-example pattern of capability list plus explicit trigger guidance.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'sync ... branch into the English main branch', 'publish the English branch', 'translate Pensieve README/tool specs/templates/SKILL.md', 'run the zh-to-main release flow' — matching the anchor for multiple specific concrete actions, not merely naming a domain.

3 / 3

Completeness

'Sync Pensieve's Chinese development/release branch into the English main branch' states what; 'Use in the Pensieve repository when the user asks to sync zh or experimental to main, publish the English branch, translate ...' gives explicit when-triggers, satisfying both halves at the top anchor rather than leaving 'when' implied.

3 / 3

Trigger Term Quality

Covers natural maintainer phrasings a user would actually say — 'sync zh or experimental to main', 'publish the English branch', 'translate ... README/tool specs/templates/SKILL.md' — with good variation rather than a single keyword, matching the top anchor.

3 / 3

Distinctiveness Conflict Risk

'Use in the Pensieve repository' plus the explicit exclusion 'Do not use for ordinary project localization or generic i18n' carve a clear niche unlikely to fire for the wrong skill. Voice is third person throughout ('Sync', 'Use', 'Do not use'), so no voice penalty applies.

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
kingkongshot/Pensieve
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.