clean-markdown-human

Solid

Clean and line-edit Markdown documents for clear, specific, publication-ready prose. Use when asked to de-bloat, de-template, remove chatbot artifacts, fix vague wording, or make Markdown read like careful human editorial writing. Do not use to fabricate facts or bypass detectors.

Data & Documents 2 stars 0 forks Updated today MIT

Install

View on GitHub

Quality Score: 78/100

Stars 20%
16
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Clean Markdown Human Editor ## Principle Edit for clarity, specificity, continuity, and factual honesty. Do not try to trick AI detectors. Do not add fake imperfections, fake anecdotes, slang, typos, or unsupported personal details. Preserve the author's meaning. If a claim is unsupported, narrow it, mark it as needing a source, or remove it. ## Input rules - Work only on the Markdown document or file paths the user provides. - Preserve YAML frontmatter, code blocks, commands, tables with real data, footnotes, links, and citations unless they are clearly broken. - Do not invent sources, numbers, dates, author names, product features, benchmark results, quotes, or case studies. - If a citation marker looks like an internal chatbot artifact, remove the artifact and keep or repair the underlying real citation only if it exists. - If the document contains placeholders, either fill them from context or mark them as TODO. Do not leave publishing placeholders in final prose. ## Pass 1: Mechanical artifact cleanup Search for and remove or flag these classes of artifacts: - Unresolved chatbot citation markers: - `contentReference[oaicite:N]` - `oai_citation:N` - `cite` markers glued to internal run IDs - `[attached_file:N]` - `grok_card` - internal references matching `turn\d+(search|fetch|file|image)\d+` - AI-tool URL parameters: - `utm_source=chatgpt.com` - `utm_source=openai` - `utm_source=claude.ai` - `utm_source=perplexity.ai` - `utm_source=copilot...

Details

Author
khasky
Repository
khasky/awesome-agent-skills
Created
4 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Solid

awesome-document-style

Clean and line-edit Markdown documents for clear, specific, publication-ready prose. Use when asked to de-bloat, de-template, remove chatbot artifacts, fix vague wording, or make Markdown read like careful human editorial writing. Do not use to fabricate facts or bypass detectors.

2 Updated today
khasky
AI & Automation Listed

plastic-humanizer

Use to clean authored prose so it reads human and clutter-free. Removes AI tells and slop from a document, spec, outcome, README, report, or release note. Use when the user says "humanize", "de-slop", "remove the AI tells", or "clean up the wording". For documents, not for every chat reply, and not for code.

9 Updated 1 weeks ago
zalom
AI & Automation Listed

humanizer

Remove signs of AI-generated writing from prose that carries a personal voice, tuned for Claude output. Use when the user asks to humanize, de-AI, clean up, or improve the tone of blog posts, essays, opinion pieces, launch announcements, newsletters, emails, or long-form articles that read like an LLM wrote them. Also use to judge whether a given text was AI-generated. Triggers on AI patterns like markdown overuse, AI vocabulary, sycophantic openers, post action summaries, standalone caveat lines, unsolicited safety disclaimers, vague attributions, significance inflation, em dash overuse, or manufactured drama. Not for prose that lives in a repository or on a forge: commits, PRs, reviews, issues, READMEs, docs, changelogs, code comments, error messages.

0 Updated 4 days ago
svyatov