Loading...
Loading...
Found 23 Skills
Use when drafting or revising human-facing prose such as docs, essays, prompts, UI copy, reports, commit messages, PR text, or polished long-form writing. Combines anti-AI-trope editing with clear and concise style rules for stronger, more natural prose.
Review and adjust writing style to reduce AI-generated patterns, making text read more naturally and human-like. Supports Chinese and English.
Remove AI-generated jargon and restore human voice to text. Built from analyzing 1,000+ AI vs human content pieces.
Collaborate on document creation and refinement. Merges contributions, manages versions, and produces unified documents from multiple sources.
Write Thai-language prose (technical documentation, marketing copy, explainers, blog posts) that reads like a real Thai writer — not generic AI output. Counters training-data skew toward over-formal, over-polite, calqued Thai. Use this skill whenever the user asks for Thai writing, asks to translate English content into Thai, or asks to edit/rewrite existing Thai prose, even if they don't explicitly say "good prose." Also use when the user is in a Thai-language conversation and asks for any non-trivial prose output (a paragraph, section, blog post, landing page, doc page, README in Thai, email, announcement). The default Thai output without this skill is mechanically polite, connective-spammed, and calque-shaped — this skill fixes that.
Write, rewrite, or edit user-facing text in the repo's preferred plain human style. Use for any prose task: docs, README sections, comments, release notes, PRDs, posts, emails, explanations, and requests to humanize or tighten text. Default to general prose rules; read references/documentation.md only for README, technical docs, usage guides, CLI/API docs, or documentation audits.
Use this skill when you need to run the unslop repo, analyze a domain for repetitive AI defaults, generate a reusable skill file, and verify that the output is specific and materially different from the baseline.
Use when transforming technical content (notes, reports, results, drafts, experiment logs) into a polished blog post for senior engineers. Supports case studies, deep dives, and how-to guides.
Humanize text: strip AI-isms and add real voice.
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.
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, PRDs, RFCs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.