
ai-content-detection-normalization
by dibelElyrian
Test blog website
SKILL.md
name: ai-content-detection-normalization description: Reduce AI-writing fingerprints and normalize content to sound human.
Use this skill for any content creation or edits across SulitFinds.
Why this matters:
- AI-generated content can be flagged by Google and hurt SEO rankings
- Readers trust human-sounding content more
- Authenticity builds long-term audience trust
Common AI writing patterns to AVOID:
-
Punctuation markers:
- Em dashes and en dashes (use commas, periods, or hyphens instead)
- Excessive semicolons in casual content
- Overuse of colons for lists
-
Sentence starters to AVOID:
- "In today's world..." or "In today's fast-paced..."
- "When it comes to..."
- "It's important to note that..."
- "It's worth mentioning that..."
- "Let's dive in" or "Let's explore"
- "Whether you're a... or a..."
- "From X to Y, there's something for everyone"
-
Transition words to AVOID or limit:
- "Moreover", "Furthermore", "Additionally" (overused by AI)
- "In conclusion", "To summarize", "In summary"
- "That being said", "With that in mind"
- "It goes without saying"
- "Needless to say"
-
Filler phrases to REMOVE:
- "It's no secret that..."
- "The truth is..."
- "At the end of the day..."
- "All in all..."
- "Last but not least..."
- "Without further ado..."
-
Generic qualifiers to LIMIT:
- "Very", "highly", "extremely", "incredibly"
- "Absolutely", "definitely", "certainly"
- "Robust", "seamless", "cutting-edge", "state-of-the-art"
-
Structural patterns to BREAK:
- Perfectly symmetrical paragraphs (same length, same structure)
- Every paragraph starting with a transition word
- Lists where every item has the exact same format
- Overly consistent sentence length throughout
-
Tone markers to AVOID:
- Excessive enthusiasm ("Amazing!", "Incredible!", "Game-changer!")
- Corporate buzzwords ("leverage", "synergy", "optimize")
- Fake conversational hooks ("You might be wondering...")
What to DO instead:
-
Vary sentence length naturally:
- Mix short punchy sentences with longer explanatory ones
- Let some paragraphs be 2 sentences, others 4-5
-
Use natural Filipino-English code-switching when appropriate:
- "Sulit na sulit ang bili mo" (when it fits the tone)
- Common Filipino expressions readers would use
-
Be specific instead of generic:
- Instead of "affordable price" → "under PHP 500"
- Instead of "many options" → "around 5-6 choices"
-
Write like you're explaining to a friend:
- Direct address ("you") is fine
- Skip formal introductions when the title already explains the topic
- Get to the point faster
-
Allow imperfection:
- Not every section needs a perfect transition
- Some paragraphs can just start with the main point
- Vary your list formats (some bulleted, some numbered, some inline)
-
Use active voice predominantly:
- "This kettle heats water in 3 minutes" not "Water is heated in 3 minutes by this kettle"
-
Include specific details that AI typically lacks:
- Local context (Philippine weather, typical Filipino households)
- Practical observations (not claims of personal testing)
- Real constraints (Manila apartment sizes, typical budgets)
Pre-publish checklist:
- Read the content aloud - does it sound natural?
- Check for repeated phrase patterns across paragraphs
- Verify no em dashes or en dashes remain
- Ensure transitions vary and don't all follow the same pattern
- Confirm specific details replace generic claims
- Check that enthusiasm levels are realistic, not excessive
Operational requirement:
- Before finalizing any blog post, run this AI-content normalization pass
- Flag any content that still reads robotic after normalization
- When in doubt, simplify and shorten rather than elaborate
スコア
総合スコア
リポジトリの品質指標に基づく評価
SKILL.mdファイルが含まれている
ライセンスが設定されている
100文字以上の説明がある
GitHub Stars 100以上
3ヶ月以内に更新がある
10回以上フォークされている
オープンIssueが50未満
プログラミング言語が設定されている
1つ以上のタグが設定されている
レビュー
レビュー機能は近日公開予定です