skills.rest
mikegogulski
mikegogulskiCOMMUNITY
Explore all skills by this author →
𝕏@mikegogulskiGitHub

abase-de-slopify

Detect and revise AI writing artifacts in documentation.

Updated Feb 16, 2026
Search Tags:#documentation#editing#ai writing#prose refinement#de-slopify#humanize text
One-click install
npx skills add https://github.com/mikegogulski/abase-django-blog-integration-test --skill abase-de-slopify
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: abase-de-slopify
Source: https://github.com/mikegogulski/abase-django-blog-integration-test/tree/main/.agents/skills/abase-de-slopify
Command: npx skills add https://github.com/mikegogulski/abase-django-blog-integration-test --skill abase-de-slopify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the issue of inauthentic, overly formulaic writing often produced by AI, making documentation sound more natural and human-written.

Core Features & Use Cases

  • AI Slop Detection: Identifies common AI writing artifacts like emdash overuse, repetitive sentence structures ("It's not X, it's Y"), and cliché lead-ins ("Here's why").
  • Manual Revision Guidance: Provides specific strategies and examples for rewriting sentences to eliminate these tells.
  • Use Case: After an AI drafts a README file, use this Skill to refine the prose, ensuring it reads like a human expert wrote it, not a machine.

Quick Start

Use the abase-de-slopify skill to review and revise the attached document for AI writing artifacts.

Frequently Asked Questions about abase-de-slopify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I humanize AI-generated text in my README files?▼

To humanize AI-generated text in README files, apply manual revision strategies that identify and rewrite AI writing artifacts like emdash overuse and formulaic sentence structures, ensuring natural language flow and an authentic human voice.

What are common signs of AI writing in API documentation?▼

Common signs of AI writing in API documentation include emdash overuse, repetitive "It's not X, it's Y" sentence structures, and cliché lead-ins such as "Here's why," which make public-facing text sound inauthentic and machine-generated.

How do I remove formulaic sentence structures from AI drafts?▼

Remove formulaic sentence structures from AI drafts by systematically reviewing the text and recasting sentences to eliminate repetitive patterns, ensuring prose refinement that achieves tone consistency and natural language flow.

Does de-slopifying documentation require manual review of the text?▼

Yes, de-slopifying documentation requires manual, systematic review and recasting of sentences to ensure natural language flow and tone consistency, as automated processing alone cannot fully restore an authentic human voice to public-facing text.

Can I use prose refinement techniques for public-facing technical text?▼

Yes, you can use prose refinement techniques for public-facing technical text like README files and API documentation to eliminate AI writing artifacts and ensure the content reads like a human expert wrote it.

Related Skills

Explore More Content & Communication Skills→
JiangAustinJiangAustin

chinese-documentation

Standardize Chinese-English technical documentation formatting, spacing, punctuation, and terminology.

Community
Basic
neuromechanistneuromechanist
42

humanizer

Detects and replaces artificial language patterns in academic and professional texts to improve natural flow.

Community
Intermediate
LAI-YEN-CHUNLAI-YEN-CHUN
1

editor

Edit text for clarity, grammar, and style with configurable tone adjustments.

Community
Intermediate
oakossoakoss
14

de-slopify

Remove AI writing artifacts from documentation and code.

Official
Intermediate