shogun-readme-sync

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

Quality

76%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/shogun-readme-sync/SKILL.md

Quality

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 solid, focused skill description that clearly identifies its niche (bilingual README synchronization) and provides explicit trigger terms in both languages. Its main weakness is that the specific actions performed could be more detailed (e.g., does it translate, diff, or just copy structure?). Overall it performs well for skill selection purposes.

Suggestions

Add more specific concrete actions to improve specificity, e.g., 'Compares diffs between README.md and README_ja.md, translates changed sections, and ensures structural parity between both files.'

Dimension	Reasoning	Score
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'. It mentions simultaneous updating but lacks detail on what specific operations are performed (e.g., diff comparison, translation, section mapping).	2 / 3
Completeness	Clearly answers both 'what' (synchronize README.md and README_ja.md between English and Japanese) and 'when' (when README changes occur, explicitly listing trigger terms 'README更新', 'README同期', 'readme sync'). 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 functionality. Coverage of bilingual triggers is a strength.	3 / 3
Distinctiveness Conflict Risk	Very specific niche: bilingual README synchronization between README.md (English) and README_ja.md (Japanese). This is unlikely to conflict with other skills due to the highly specific file names and bilingual sync focus.	3 / 3
	Total	11 / 12 Passed

Implementation

62%

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 with a clear four-step workflow and good validation checkpoints. Its main weaknesses are the lack of truly executable/actionable commands (the diff detection is described conceptually rather than with concrete tool calls) and some verbosity in the translation tables that could be externalized. The workflow clarity is the strongest dimension, with explicit sequencing and a final validation step.

Suggestions

Replace the pseudo-command 'Read README.md' with concrete tool invocations or grep/diff commands that actually detect section mismatches programmatically.

Consider extracting the translation glossary table into a separate reference file (e.g., GLOSSARY.md) and referencing it from the main skill to improve progressive disclosure and reduce inline bulk.

Dimension	Reasoning	Score
Conciseness	The skill 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 content is relevant and doesn't over-explain general concepts, but there's moderate room for tightening.	2 / 3
Actionability	The skill provides a clear 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 report is a good example output, but the actual detection and modification steps are described rather than scripted.	2 / 3
Workflow Clarity	The four-step workflow is clearly sequenced: detect diffs → report → sync → final validation. Step 4 provides an explicit validation checklist after modifications, creating a proper feedback loop for this non-destructive document editing task.	3 / 3
Progressive Disclosure	The content is well-structured with clear sections and tables, but everything is in a single file with no bundle files or references to external resources. The translation glossary and guidelines could potentially be split out, though for a skill of this size (~90 lines) it's borderline acceptable.	2 / 3
	Total	9 / 12 Passed

Validation

100%

Warnings & errors only

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.

Repository: yohey-w/multi-agent-shogun
Commit: bb19915

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.