CtrlK
BlogDocsLog inGet started
Tessl Logo

shogun-readme-sync

README.md(英語)とREADME_ja.md(日本語)の同期を確認・実行するスキル。README変更時に両言語版を必ず同時更新するために使用。「README更新」「README同期」「readme sync」で起動。

67

Quality

80%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/shogun-readme-sync/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%

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

This is a well-structured, project-specific skill for synchronizing bilingual README files with a clear 4-step workflow and useful translation glossary. Its main weakness is that the actionability relies on descriptive instructions rather than concrete tool calls or executable commands—the 'Read' pseudo-commands and diff detection are conceptual rather than implementable. The workflow clarity and organization are strong points.

Suggestions

Replace the pseudo-commands ('Read README.md') with actual tool invocations or concrete algorithmic steps for detecting section mismatches (e.g., grep/regex patterns for counting ### headers).

Add a concrete example showing a before/after of a sync operation on a small README snippet to make the translation and numbering fix process more actionable.

DimensionReasoningScore

Conciseness

The content is mostly efficient and project-specific, but the translation glossary table and some of the checklist items feel like they could be tighter. The workflow steps are reasonably lean but include some redundancy between Step 1's check items and Step 4's final check.

2 / 3

Actionability

The skill provides a clear structured process with specific check items and a translation glossary, but lacks executable code or commands—the 'Read README.md' pseudo-commands aren't real tool invocations. The diff detection and sync steps describe what to do conceptually rather than providing concrete, copy-paste-ready implementations.

2 / 3

Workflow Clarity

The four-step workflow is clearly sequenced: detect diffs → report → sync → validate. Step 4 serves as an explicit validation checkpoint after modifications, and the report format in Step 2 provides a clear intermediate output. The process has a logical feedback structure for a non-destructive document editing task.

3 / 3

Progressive Disclosure

For a self-contained skill under 100 lines with no need for external references, the content is well-organized with clear sections (Overview, When to Use, Instructions with numbered steps, Guidelines). The structure is appropriate for the skill's complexity.

3 / 3

Total

10

/

12

Passed

Description

89%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a well-crafted skill description that clearly defines its narrow purpose (bilingual README synchronization), provides explicit trigger terms in both languages, and answers both what and when. The main weakness is that the specific actions could be more detailed (e.g., does it translate content, diff files, update sections?).

Suggestions

Add more specific concrete actions such as 'translates content changes', 'diffs sections between files', or 'updates headers and links' to improve specificity.

DimensionReasoningScore

Specificity

Names the domain (README synchronization between English and Japanese) and describes the core action (confirm and execute sync), but doesn't list multiple specific concrete actions beyond 'confirm' and 'execute sync'.

2 / 3

Completeness

Clearly answers both 'what' (confirms and executes synchronization between README.md and README_ja.md) and 'when' (when README changes occur, with explicit trigger terms listed). The trigger guidance is explicit.

3 / 3

Trigger Term Quality

Includes natural trigger terms in both Japanese and English: 'README更新', 'README同期', 'readme sync'. These are terms users would naturally say when needing this skill. Also mentions specific filenames (README.md, README_ja.md).

3 / 3

Distinctiveness Conflict Risk

Very specific niche: bilingual README synchronization between English and Japanese versions. Unlikely to conflict with other skills due to the narrow, well-defined scope and specific file references.

3 / 3

Total

11

/

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
yohey-w/multi-agent-shogun
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.