Loading...
Loading...
Found 24 Skills
Main entry for cross-platform content creation. Coordinates the entire creation process: Research → Image Selection → Writing → Polishing → Platform Conversion. Used for creating articles, developing content, conducting topic research, and publishing to Zhihu/Xiaohongshu/WeChat Official Accounts.
Analyze the writing style characteristics of articles, extract style dimensions and store them in the style material library. It can fuse multiple style materials to generate or update the main style profile (my_style.json). Use this skill when users say "analyze style", "extract writing style", "learn this tone", "analyze my writing style", "absorb this style", "update my style". Even if users just share an article and express interest in its style, consider using this skill.
Communicate ideas and information to others with purpose, clarity, and integrity. Ensure that artifacts are structured and phrased in a way that is mindful of their audience while avoiding AI slop patterns. Use when the user requests assistance with writing, commentary, or communication; when they point out AI slop, when they ask things like "help me say", "write for [a specific audience or context]", "polish [comments, sentences, artifacts]", or the like.
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.
Reviews and iterates on social media copy in album promo/ files. Use after populating promo templates and before release to polish platform-specific posts.
De-slop pass for any text. Scans for the statistical fingerprints of AI writing (negative parallelism / "not X but Y", em-dash density, rule-of-three, false ranges, puffery vocabulary, uniform cadence, hedged both-sidesing), rewrites by meaning, then re-scans until the text is clean and sits in the right register for its genre: academic article, tweet, reddit post, email, blog, docs, marketing. Use when the user says "deslopify", "deslop", "de-slop this", "remove the AI tells", "humanize this", "make this not sound like AI", or invokes /deslopify. Also use before publishing any agent-drafted prose.
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.
Review and edit copy for grammar, style, and clarity. Works with project style guides or uses sensible defaults. Use when reviewing marketing copy, blog posts, documentation, emails, or any business writing that needs polish.
When the user wants to edit, review, or improve existing marketing copy. Use when the user says anything like "edit this copy," "review my copy," "copy feedback," "proofread," "polish this," "make this better," "tighten this up," "this reads awkwardly," "clean up this text," "too wordy," "sharpen the messaging," "this doesn't sound like me," "something's off with this," "make this punchier," "this is boring," or "can you fix this copy." Handles everything from quick polish on a sentence to deep restructuring of a full page. World Code integrated — edits against your voice rules and World Code consistency. For writing new copy from scratch, see boring-copywriting.
Use for durable prose artifacts: docs, README, release notes, UI copy, comments, commit messages, PR/issue text. Skip ordinary chat replies.