Loading...
Loading...
Found 24 Skills
Use only when explicitly asked to write or edit prose. Not for code comments, commit messages, or inline docs.
Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells and produce more human-like writing.
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.
Read this when writing or revising articles. It applies to explanatory texts such as documentation, comments, commit messages, PR descriptions, and articles, as well as reading material such as novels. It is also useful for fixing prose that feels “AI-like” or is difficult to read.
Removes AI writing artifacts from documentation and code. Use when editing LLM-generated prose, reviewing READMEs, polishing docs before publishing, or cleaning up AI-generated code. Use for emdash cleanup, formulaic phrase removal, tone calibration, over-commented code, verbose naming, and AI code smell detection.
You MUST use this when drafting, rewriting, shortening, tightening, reviewing, or explaining edits to prose in English or Ukrainian for a particular reader - docs, READMEs, PR descriptions and review replies, chat messages, emails, articles, reports, and product copy - including a single paragraph, email, or reply the user pastes, requests to make text clearer, shorter, less generic, less AI-sounding, or less bureaucratic, and rewriting a draft to match a sample of the author's writing. Dash policy belongs to dashfix, negative-parallelism audits to negafix, deciding whether a review finding is valid to review-resolution, agent instruction files to maintaining-agent-context, and interface copy written while designing a UI to frontend-crafting. Not for translation.
Creative writing skill for drafting and editing narrative fiction prose. Use when writing new scenes, chapters, or dialogue, or when editing existing prose. Discovers and follows project-specific style guides, character voice conventions, and formatting preferences.
Use for durable prose artifacts: docs, README, release notes, UI copy, comments, commit messages, PR/issue text. Skip ordinary chat replies.
Apply Strunk's timeless writing rules to ANY prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Makes your writing clearer, stronger, and more professional.
Prose editing, rewriting, and humanizing text for natural tone. Use when asked to "write", "rewrite", "edit", "humanize", "improve text", "fix the tone", "remove AI language", "proofread", or when writing copy, docs, blog posts, articles, emails, PR descriptions, or plans.
Strip the tells of AI-generated writing from prose so it reads like a person wrote it. Use when asked to humanize text, remove AI-isms, make writing sound less like ChatGPT, edit out "AI slop," or review a draft for robotic phrasing without rewriting it. Covers em-dash overuse, puffery, filler, and the AI vocabulary words.
Detect and remove AI writing tells ("slop") from prose while preserving the author's voice. Load when drafting or reviewing prose, blog posts, essays, white papers, marketing copy, emails, docs, or reports, and when a human asks to make writing sound less AI-generated or to review someone else's writing for AI tells. Triggers on "sounds like AI", "slop", "AI tell", "make this more human", "editorial pass", or "review my writing".