본문으로 건너뛰기
cccskills
무료GitHub에 공개

deslop

Edit blog posts, documentation, marketing copy, and PR descriptions to remove formulaic AI writing patterns. Replace filler, vague claims, and staged emphasis with plain statements while preserving concrete details and the writer's voice.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

Remove AI writing patterns from prose so it reads like a person wrote it. Use when writing, editing, or reviewing user-facing text (blog posts, docs, marketing copy, PR descriptions), or when asked to "deslop", "de-AI", or "make it sound human".

설치 방법 보기

이럴 때 유용합니다

  • Editing AI-drafted blog posts
  • Removing wordy introductions from documentation
  • Toning down exaggerated marketing copy
  • Making PR descriptions clearer and more natural

포함된 파일(2)

  • SKILL.md2.3 KB
  • LICENSE1.0 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Deslop

Make prose sound like a specific person wrote it. Fix each tell by stating the underlying claim plainly, not by swapping in a new flourish.

Cut or rewrite

  • Filler: throat-clearing ("Here's the thing:"), emphasis crutches ("Let that sink in."), meta-commentary ("In this section, we'll explore..."), "It's worth noting," and business jargon ("navigate the landscape," "leverage").
  • Staged contrasts like "Not X. Y." or "It's not X, it's Y." State Y.
  • Manufactured rhythm: dramatic fragments ("Speed. That's it."), rhetorical questions answered right away ("The result? Devastating."), three-part phrasing that exists only for cadence ("fast, simple, and powerful"), and paragraphs that end on a one-liner restating the paragraph.
  • AI vocabulary: "delve," "tapestry," "quietly," "serves as," "highlighting its importance," invented concept labels ("the supervision paradox"), and inflated stakes.
  • Vagueness: declaratives that name nothing ("The reasons are structural"), "experts argue" with no name, and "every," "always" or "never" doing vague work.
  • False agency, where a thing does a person's verb ("the complaint becomes a fix"). Name who did it.
  • Signposting: announcing what you're about to say, then summarizing what you said. "In conclusion." "Despite these challenges."
  • Formatting tells: em dashes, unicode arrows, and lists where every item opens with a bolded keyword.

Keep

Specifics (names, numbers, examples), "you" for the reader in blog posts, varied sentence length, and short plain lines that carry information. Keep bullet points and numbered steps for actions and instructions; don't fold them back into paragraphs. When editing someone else's writing, keep their voice.

Example

Before: "Here's the thing: most pipelines break in production. Not because the code is bad. Because the data is bad. Let that sink in."

After: "Most pipelines break in production. The code runs fine. The data doesn't match the assumptions baked into it."

Adapted from stephenturner/skill-deslop (MIT, see LICENSE).

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Research questions about a market, examine recorded ChatGPT answers and cited websites, and identify themes where a brand appears or is missing. Receive ranked prompt groups and suggested questions for future tracking.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Finding question themes related to a product category
  • Checking brand mentions and cited websites
  • Identifying themes with limited brand visibility
every-app/open-seo2.4만2026년 10월 14일 업데이트

Audit how a brand appears in AI answers by examining mentions, website citations, competitors, and cited pages. Receive one to three evidence-based priorities, such as improving a page, seeking inclusion in a relevant source, or fixing access barriers.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Investigate why AI answers recommend competitors
  • Check brand mentions and website citations
  • Prioritize pages to improve or create
every-app/open-seo2.4만2026년 10월 14일 업데이트

Compare several competitors to see which sites lead a search market, what content earns rankings, and where opportunities remain. The report covers keyword reach, links from other sites, and practical next steps.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Identifying leading sites in a search market
  • Comparing competitors' successful content themes
  • Finding underserved topics to target
every-app/open-seo2.4만2026년 10월 14일 업데이트

Analyze a named competitor's unpaid search traffic, ranking keywords, content themes, and links from other websites. Identify strengths, weaknesses, and relevant opportunities, with an optional comparison to your own site and a report of recommended actions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Investigate a specific competitor's SEO strengths
  • Find pages and keywords worth targeting
  • Compare a competitor with your own site
every-app/open-seo2.4만2026년 10월 14일 업데이트

Create or update skills using OpenSEO's repository conventions. Keep one canonical source, distinguish internal and public workflows, maintain Claude Code links, and register public skills in documentation, the in-app agent, and plugin bundles.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Add a new skill to the OpenSEO repository
  • Turn a development workflow into an internal skill
  • Repair drift between skill directories
every-app/open-seo2.4만2026년 10월 14일 업데이트

Evaluate changes to OpenSEO skills by running fresh Codex sessions against a local backend. Compare saved reports using weighted criteria, then inspect tool logs to understand failures and check whether revised instructions improve output.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Comparing report quality before and after skill edits
  • Checking revised instructions across different websites
  • Scoring SEO audit reports against defined criteria
every-app/open-seo2.4만2026년 10월 14일 업데이트

every-app의 스킬 모두 보기

이 스킬의 문제 신고