This skill dismantles AI-specific hollow writing styles, unnatural metaphors, and broken SVOCM (subject-predicate relations), and processes them into natural Japanese that humans can read without stumbling.
* If other agent skills intended for style adjustment or Japanese proofreading are enabled in the same environment, interference between instructions may disrupt the output. When using this skill, consider disabling similar skills.
1. Core Design Philosophy
Based on the latest academic research and a quantitative survey of 70,000 Qiita posts, the text is reconstructed according to the following principles. The top-priority rule of this skill is "Complete preservation of meaning (do not change the claim, weighting, strength of assertion, or function of the sentence)." Without changing what is being said, fix only the AI-ness (unnatural metaphors, empty embellishment, distorted syntax).
Top-Priority Rule: Preservation of Meaning
Before rewriting, check the following four points of the original sentence, and always keep them the same after rewriting. All other principles apply only within the range that does not change these four points.
- Claim (what is being said): Maintain the key points and logical relationships you want to convey. Do not replace points such as "essence" or "core" with a different concept such as "purpose," or change the point by arbitrarily adding verbs.
- Weighting (what is treated as most important and what is treated lightly): Do not turn something that was negated into a parallel item (B in addition to A), or arbitrarily change the ranking.
- Strength of assertion (definitive statement, conjecture, possibility): Keep what the original sentence asserts as an assertion, and write what is written as conjecture or possibility with that same strength (do not weaken it to "there is a risk" or raise "it could be said that" to a definitive statement).
- Function of the sentence (evaluation, explanation, request, plan, impression): Keep evaluation sentences as evaluations and explanations as explanations (do not turn evaluation/nature sentences such as "~ is important" or "the essence of ~ is" into goal/plan sentences such as "aims to ~" or "enhances ~").
Complete Restoration of SVOCM
Beyond merely paraphrasing words, clarify "who does what and how." However, do not arbitrarily invent and add agents, nouns, or actions that are not known from the original sentence or its context. Restoring demonstrative pronouns such as "this" or "one of them" to nouns is limited to cases where the referent is clear from the context.
Clarification of the agent and the action directed at it
Organize roles so that requests to the reader are phrased as "please do ~" and feature explanations as "you can ~." However, use these only when it is clear from the original sentence whether it is an instruction to the reader or an explanation of a feature, and do not arbitrarily change the function of a sentence (explanation or evaluation) into a request or a prediction.
Breaking down inanimate subjects (personification)
Do not give emotions or will to tools or concepts; return them to objective actions. However, do not arbitrarily fabricate an agent that is not in the original sentence.
Concretizing metaphorical verbs and changing them to everyday words
Rewrite AI-specific metaphorical expressions such as "defeat," "work," "dissolve," and "crush" into everyday words or precise words that fit the context. Do not repeatedly use overly stiff two-character kanji compounds such as "occurrence" and "guarantee" in unnecessary places (however, do not forcibly remove legitimate technical terminology such as "data integrity"). Always preserve the "connotation (direction of feeling or evaluation)" that a metaphor or turn of phrase carried.
- Examples of connotation: the carelessness of "accidentally," the feeling of having waited too long in "finally," the regret of "~te shimatta," the sense of something unobtrusive yet definitely present in "quietly."
- Metaphorical words may be rephrased. However, the connotation or reason that the word conveyed should be supplemented and expressed with other everyday words.
- Not only metaphorical verbs but also adverbs and introductory turns of phrase are treated the same way. In expressions like "breaks quietly," "breaks" used for data or systems is an AI-specific literal translation/metaphor. Concretize it into an objective, technical state such as "data integrity is lost" or "inconsistency arises" (do not weaken a sentence that asserts "breaks" into something like "there is a risk"; maintain the strength of the assertion). Also, vague expressions like "quietly" and "silently" should be written with the same range of not being noticed, as in "before anyone notices" or "without anyone knowing." Writing it as a matter of mechanism, such as "without producing an error" or "without notification," should be limited to cases where it is clear from the original sentence or context that no error or notification occurs. Keep only the literal "breaks" for physical objects such as clocks and machines, or for the body (such as having an upset stomach). Also, idioms established in everyday Japanese such as "takes effort," "is a handful," "the scales fall from one's eyes," and "wait with bated breath" should not be treated as AI-like metaphors and should be left as they are. In business specifications too, leave them if there is no risk of misunderstanding the meaning. When in doubt, the guideline is whether the expression is commonly seen in human writing from before AI became widespread; if it is, leave it.
Organizing self-labeling and negative contrast
When "what matters is" or "what is important is" carries the evaluation itself, do not delete the evaluation but move it into the predicate and keep it ("~ is important," "~ matters"). You may cut the preamble only when cutting it does not change the claim. For negative contrast (B rather than A), turn it into an affirmative sentence only when removing the negation does not change the claim. Negation that carries meaning or weight, such as restating as B something that tends to be thought of as A, should not be forced into affirmation; keep it as negation and only make the wording natural. Do not list the negated A as "in addition to A, B," or rank it as "B over A." When keeping the negation, do not add reason sentences that were not in the original.
Preserving meaning and not adding information (not adding)
Do not add agents, nouns, actions, causes, conditions, numbers, examples, or technical terms that cannot be known from the original sentence or its context. Do not arbitrarily replace vague words with narrower, more specific facts. When information is insufficient and you cannot write concretely, do not fill it in on your own in the body; present it at the end of the output as "points to confirm with the writer."
Sentence length suited to breathing and restraint of commas
Keep the average sentence length at 30 to 45 characters, and restrain commas to 0 to 2 per sentence to create a smooth reading experience.
Complete elimination of decorative symbols and unnecessary spaces
Completely eliminate emoji, sentence-ending colons, em dashes, parenthetical rephrasings that do not add information, and unnatural half-width spaces between Japanese and Western text.
2. Execution procedure
Step 1: Determining domain and mode
Determine the domain from the input text or instructions (such as "for technical articles" or "domain: tech").
tech(Technical articles): Technical blogs and design documents. Keep bullet points at 15% or less, and organize procedures within the scope of information in the original sentences or materials (do not arbitrarily create and add commands or code snippets that are not in the original).business(Business and specifications): PR descriptions and internal reports. While preserving the reasons for metaphors, revise to objective expressions, and clarify boundary conditions and responsible parties within the scope that can be understood from the original sentences.essay(Essays and personal publishing): note and personal journals. Avoid exaggerated moralizing, and preserve plain emotions and concrete experiences (do not invent sensory descriptions or people that are not in the original).
When there is no explicit specification, automatically determine it from the context.
Step 2: Executing syntactic transformation
references/gemini-syntax.md and domain-specific specifications, transform according to the following procedure.
Pre-start confirmation: Before rewriting, confirm the following four points of the original sentence: "claim," "weight," "strength of assertion," and "function of the sentence."
- Clarify the agent (subject) and object within the scope that can be understood from the original sentence (if unknown, do not add them on your own).
- Only when it can be understood from the original sentence whether it is an instruction to the reader or a functional explanation, organize it into "please do ~" or "can do ~" (do not change evaluative or explanatory sentences into requests or plans).
- Demonstrative pronouns (kore, katapou, etc.) are restored to concrete nouns only when the referent is clear from context.
- Metaphorical verbs and expressions are replaced not by lining up idioms but with ordinary words or precise words that fit the context (the feeling, direction of evaluation, and connotation the original word had, such as "ukkari," "youyaku," "~te shimatta," "jimi ni," are preserved with other ordinary words. For "kowareru" applied to abstractions such as "data ga kowareru," concretize it as "data no seigousei ga ushinawareru" or "fuseigou ga okiru," and maintain only the literal "kowareru" for physical objects such as clocks and machines or for the body. "Shizuka ni" and "damatte" are corrected while keeping the same range of unnoticeability, as in "kizukanai uchi ni" or "shiranai uchi ni." Established idioms such as "hone ga oreru" and "te wo yaku" are left as they are).
- Remove duplicate supplementary parentheses and eliminate extra half-width spaces before and after English words.
- When "juuyou na no wa" carries the evaluation, leave it in the predicate ("~ ga daiji desu"), and for negative contrast (B rather than A), if the negation carries meaning or weight, keep the negation while making the phrasing natural (do not change it to "A ni kuwaete B" or to a ranking).
- Eliminate emoji, sentence-ending colons, and dash symbols.
- Adjust the rhythm so that the same sentence ending does not occur three times in a row.
- Remove unnecessary bold and integrate bullet points into ordinary paragraphs.
Post-completion check: Check whether the rewritten sentences completely preserve the four points confirmed before starting (claim, weight, strength of assertion, function of the sentence) and the "connotation" of the original words. If there were points you actually hesitated over while writing the main text (points you wanted to supplement but did not), narrow them down to at most two and move them to "Points I want to confirm with the writer" (if there were no points of hesitation, omit this entire section).
Step 3: Mechanical inspection
When full mode is specified or when saving a file, run the bundled linter to perform static inspection.
# スキル配置先（${CLAUDE_SKILL_DIR}等）を基準にスクリプトの絶対パスを解決して実行
python3 <スキル配置ディレクトリ>/scripts/yomiyasu_lint.py <対象ファイル>
Detection results are positioned as candidates for mechanical review. For medicine, 体温, image processing, 解像度, chemistry, 触媒 , and so on, if they are contextually legitimate technical terms or factual descriptions, do not force rewording and retain them. Also, words that carry evaluation such as "daiji desu," and negations necessary for the claim (B rather than A), should not be forcibly removed even if the linter points them out; leave them as they are. Limit revision attempts to a maximum of two, preventing excessive rewording loops that only aim to eliminate warnings.
3. Output format
During dialogue rewriting, present in the following format. Do not use emoji or unnecessary parentheses.
### 脱臭・リライト結果
（自然な日本語に再構築された本文）
---
### 主な改善ポイント
- 意味の保持: 主張・比重・言い切りの強さ・文の働き・含みを維持
- （その回に実際に変更した点だけを簡潔に箇条書きで記載）
### 書き手に確かめたい点（※本文を書くときに実際に補うか迷った点がある場合のみ、最大2点まで記載。迷った点がなければこの見出しごと出さない）
- （補いたくなったけれど補わなかった前提や条件があれば、短く1〜2点だけ記載）