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

openmark-polisher

Scrub English drafts for AI tells before publishing. Use for any English LinkedIn post or newsletter draft right after composition and BEFORE export. Removes em-dash-as-pause, weak hedges, rule-of-three patterns, AI vocabulary, negative parallelisms, and inflated symbolism. Triggers on "polish", "humanize", "make this sound human", "/polisher", or after any English composer output. Leaves Arabic and Hebrew drafts untouched — humanizer-* skills handle those.

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

연동 도구LinkedIn
설치 방법 보기

포함된 파일(1)

  • SKILL.md3.8 KB

SKILL.md(원문)

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

OpenMark — Polisher (English AI-tell scrub)

The composer wrote a draft. Your job is to remove the residue that makes it read AI-shaped. ONE pass, ≤ 6 minutes. Output is the rewritten draft, nothing else.

When to use vs not

  • English drafts only. Arabic / Hebrew → use the humanizer-ar-* / humanizer-he skills.
  • Run AFTER the composer sub-agent, BEFORE the verifier sub-agent.

What to scrub (the 8 high-signal AI tells)

  1. Em dash used as a pause (—). Replace with comma, colon, parentheses, or a line break. Hyphen compounds like well-architected stay.
  2. Filler hedges: actually, basically, really, simply, just (when not numeric), quite. Delete.
  3. Pleasantries: Sure!, Of course!, Happy to, Here's what I found:, In conclusion, Bottom line:. Delete or rewrite into the line.
  4. Rule of three in lists or sentences (X, Y, and Z). If the three items don't all carry weight, cut to two or one. Two-element lists beat three-element padded lists.
  5. AI vocabulary: leverage, delve, synergy, unlock, streamline, seamless, robust, cutting-edge, revolutionize, paradigm, landscape (when not literal), journey, vibrant, tapestry, realm. Replace with the specific noun.
  6. Negative parallelism: Not only X, but also Y. Pick one. Say it once.
  7. Inflated symbolism: at its core, fundamentally, essentially, in essence. Delete; if the sentence still reads, you didn't need it.
  8. Vague attributions: experts say, studies show, many believe. Name the person, org, paper, or cut the claim.

Workflow

  1. Read the draft once for shape. Note the format (LinkedIn post / essay / roundup / comparison / analytical).
  2. Run the 8 scrubs above, in order. Don't change meaning.
  3. Re-check word count is still inside the schema bounds. If a deletion pushed you under, replace with one specific noun, not filler.
  4. Confirm citations survived — every [phrase](URL) is still in the body.
  5. Output the rewritten draft as the same Pydantic shape you received. No commentary, no diff, no "I removed X" — just the new draft.

Voice anchors (don't lose these)

Generic AIAhmad's voice
"leverage AI to streamline workflows""use the agent for the boring half"
"fundamentally transformative""actually changes the work"
"Three weeks ago, an agent shipped a pull request, the maintainer didn't notice, and the bot got merged.""Three weeks ago an agent shipped its own pull request. The maintainer didn't notice for a day."
"In conclusion, the implications are significant."(delete the sentence)

What NOT to do

  • Don't change citations. Same URLs, same anchor positions.
  • Don't change the schema shape. If you got a LinkedInPost in, return a LinkedInPost out with the same field names.
  • Don't translate. English in, English out.
  • Don't add new claims. You scrub, you don't research.

Self-check before returning

Tick all four:

  • No em dash used as a pause anywhere in the draft
  • No leverage / delve / synergy / unlock / streamline / seamless / realm / tapestry
  • No rule-of-three padding ("X, Y, and Z" where Z is the weakest)
  • Word count still inside schema bounds

If any one fails, fix and re-check. Then return the draft.

리뷰

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

댓글

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

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

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

0 / 1,000자

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

같은 저장소의 스킬

Reusable skill for coding agents to build mediahost integrations, API clients, scrapers, bulk downloaders, and media tools. Incorporates the unofficial Python wrapper, auth flow, endpoints, rate-limit handling, and cross-language patterns ...

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

OthmanAdi/OpenMark102026년 7월 28일 업데이트

Reusable skill for coding agents (Claude, GPT, etc.) to build, optimize, debug, and productionize AI agents and coding agents in Rust. Embeds Rig/ADK patterns, Tokio async architecture, tracing observability, performance techniques, erro...

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

OthmanAdi/OpenMark102026년 7월 28일 업데이트

Remove AI-generated writing patterns from Egyptian Arabic (عامية مصرية / Masri) text. Use when editing or reviewing Egyptian dialect text to make it sound authentically human-written.

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

OthmanAdi/OpenMark102026년 7월 28일 업데이트

Remove AI-generated writing patterns from Modern Standard Arabic (MSA/الفصحى) text. Use when editing or reviewing Arabic formal text to make it sound naturally human-written.

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

OthmanAdi/OpenMark102026년 7월 28일 업데이트

Remove AI-generated writing patterns from Levantine Arabic (الشامي — Syrian, Lebanese, Palestinian) text. Use when editing or reviewing Levantine dialect text to make it sound authentically human-written.

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

OthmanAdi/OpenMark102026년 7월 28일 업데이트

Remove AI-generated writing patterns from Modern Hebrew (עברית מודרנית) text. Use when editing or reviewing Hebrew text to make it sound naturally human-written.

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

OthmanAdi/OpenMark102026년 7월 28일 업데이트

OthmanAdi의 스킬 모두 보기

이 스킬의 문제 신고