README.md(英語)とREADME_ja.md(日本語)の同期を確認・実行するスキル。README変更時に両言語版を必ず同時更新するために使用。「README更新」「README同期」「readme sync」で起動。
84
80%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/shogun-readme-sync/SKILL.mdQuality
Discovery
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 description for a narrow, specific skill. It clearly identifies the target files, the synchronization task, when to use it, and provides explicit trigger terms in both languages. The only minor weakness is that the specific actions could be slightly more detailed (e.g., does it translate content, copy structure, validate links?).
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (README files in English and Japanese) and the core actions (confirm/execute synchronization, simultaneous updates), but doesn't list multiple granular actions beyond 'confirm and execute sync'. | 2 / 3 |
Completeness | Clearly answers both 'what' (synchronize README.md and README_ja.md bilingual versions) and 'when' (when README is changed, both language versions need simultaneous updates), with explicit trigger terms listed. | 3 / 3 |
Trigger Term Quality | Includes natural trigger terms in both Japanese and English: 'README更新', 'README同期', 'readme sync', plus mentions specific filenames 'README.md' and 'README_ja.md'. These are terms users would naturally say when needing this skill. | 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 scope targeting specific files (README.md and README_ja.md). | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
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. Its strengths are the clear 4-step workflow with validation, the concrete translation glossary, and the example diff report output. Its main weakness is that the actual execution steps are more descriptive than executable—there are no real scripts or commands to run, just instructions for Claude to manually compare files.
Suggestions
Make Step 1 more actionable by providing a concrete algorithm or heuristic for diff detection (e.g., 'count lines matching ^### in each file and compare counts') rather than just listing check items
Consider providing a concrete example of a before/after sync edit to make Step 3 more actionable beyond the glossary table
| Dimension | Reasoning | Score |
|---|---|---|
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 more compact. The skill doesn't over-explain concepts Claude knows, but the formatting adds some bulk. | 2 / 3 |
Actionability | The workflow steps are clear and the translation glossary provides concrete mappings, but there's no executable code—just pseudo-instructions like 'Read README.md'. The diff detection relies on Claude's judgment rather than concrete commands or scripts. The example diff report is helpful but the actual execution steps are vague. | 2 / 3 |
Workflow Clarity | The 4-step workflow is clearly sequenced: detect diffs → report → sync → final validation. Step 4 provides an explicit validation checklist, and the process includes a feedback loop where you verify after making changes. The sequence is logical and complete for this type of task. | 3 / 3 |
Progressive Disclosure | For a skill under 50 lines of core content with no need for external references, the content is well-organized with clear sections (Overview, When to Use, Instructions with numbered steps, Guidelines). No bundle files are needed for this straightforward synchronization task. | 3 / 3 |
Total | 10 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
4ee1377
Table of Contents
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.