Loading...
Loading...
Found 57 Skills
Systematically reduces AI detection rate and adds human touch through three-pass proofreading (content, style, details). Use when proofreading articles, reducing AI flavor, when content feels robotic, or when user mentions AI detection rate or lack of authenticity.
Use this when the user wants to review, polish, or proofread articles. Triggers include requests such as "polish my article", "check this", "revise my writing", "proofread this", "look over my article"
Makes video scripts more suitable for actual recording by enhancing colloquial tone and removing formal language. Use when proofreading video scripts, when content is too formal, or when scripts need to sound more natural for speaking aloud.
Proofread and improve English text written by the user before answering their actual question. Use this skill whenever the user's message contains English sentences or paragraphs — even mixed with Korean — and a substantive answer is expected. Trigger on any message where English prose is present: questions, requests, opinions, descriptions, or explanations written (fully or partly) in English. Do NOT skip proofreading just because the English looks mostly correct; always run the correction block first. Skip only for: single English words, proper nouns, code snippets, or messages written entirely in Korean with no English prose.
Text proofreading for Markdown documents. Detects stylistic issues based on guidelines and presents revision suggestions. Used when users make requests such as "proofread the text", "fix the writing style", or "proofread the document".
Proofread and correct text for grammar, spelling, punctuation, style, clarity, and consistency, with support for multiple style guides and readability analysis.
Systematically reduce the AI detection rate to below 30%, and add a human touch through a three-round review process (content, style, details). Use this skill when users mention phrases such as "too AI-like", "sounds written by AI", "reduce AI detection rate", "more human-like", "more natural", or "colloquial"
Three rounds of review to reduce AI detection rate and make articles more human-like. Activate this when users mention phrases such as "too AI-like", "sounds written by AI", "reduce AI detection rate", "review", or "make it more natural".
Review work after prose exists: editorial review, craft critique, continuity/voice review, copyediting, proofreading, and synthesis of reader-sim signal. Load when diagnosing a draft rather than rewriting it.
Run the proofreading protocol on lecture files. Checks grammar, typos, overflow, consistency, and academic writing quality. Produces a report without editing files.
A skill for writing and revising Japanese business documents to make them easy to read and understand. It can be used for creating and proofreading business documents such as meeting minutes (including transcribing to minutes), research/analysis reports, internal guides/manuals, research notes, discussion papers, proposals, reports, emails, and slide outlines, as well as following instructions like 'write from the conclusion', 'clarify the argument', 'keep headings concise', and 'explain technical terms in an easy-to-understand way'. It also supports removing AI-like tones (direct, indirect, or colloquial feedback such as 'AI-like', 'unnatural', 'make it more natural Japanese', 'mechanical', 'make it sound human', 'monotonous', or phrasing like 'it would be possible to...', as well as cases where the document was said to be written by AI or suspected of being so), improving hard-to-read or unclear sentences (such as incorrect word order, long sentences, unclear meaning, incorrect comma placement, etc.), writing new note articles, blog posts, and essays (including requests to write from scratch on any topic), rewriting and polishing existing sentences, diagnosing and scoring AI-like tones (requests without rewriting, such as 'Did AI write this?', 'Score the AI-like tone', 'Judge how AI-like this is'), and requests to learn and profile one's own writing style (including requests to write in one's own style by reading past sentences). It also addresses readability principles such as removing forbidden words, avoiding monotonous rhythm, homogeneous paragraph structure, literal translation of English syntax, as well as word order, commas, one meaning per sentence, and the distance between subject and predicate. The structuring of technical documents or formatting of Markdown itself (such as one sentence per line, quote blocks, footnote notation, etc.) is not covered—this falls under another skill, and this skill specializes in the naturalness, readability, and comprehensibility of text.
Identify grammar, logical, and flow errors in text and suggest targeted fixes without rewriting the entire text. Use when proofreading content, checking writing quality, or reviewing a draft.