stop-slop-technical

Rewrite prose removing AI tells while preserving technical accuracy and precision.

1|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/dsteven12/airtable-sa-skills --skill stop-slop-technical
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stop-slop-technical
Source: https://github.com/dsteven12/airtable-sa-skills/tree/main/skills/stop-slop-technical
Command: npx skills add https://github.com/dsteven12/airtable-sa-skills --skill stop-slop-technical

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Remove AI writing patterns from prose while preserving technical precision. Use when drafting, editing, or reviewing any text — conversations, documents, explanations, Slack messages, emails — to eliminate predictable AI tells without sacrificing accuracy in technical or system-level descriptions.

Core Features & Use Cases

  • Remove filler phrases that announce content
  • Name the actor in each sentence (human or system) to avoid passive voice
  • Be specific and readable in technical contexts; maintain trust and clarity
  • Real-world use: drafting architecture notes, write-ups, Slack messages, emails with technical detail

Quick Start

Rewrite prose to remove AI tells while preserving technical accuracy.

Frequently Asked Questions about stop-slop-technical

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

FAQPage Schema
How do I remove AI writing patterns from technical architecture docs?

To remove AI writing patterns from technical architecture docs, apply rules that cut filler phrases, name the system actor in each sentence, and enforce specific factual tone while preserving technical accuracy.

What are common AI tells in technical writing and how do I fix them?

Common AI tells in technical writing include filler phrases that announce content, passive voice hiding the actor, and predictable rhythm. Fix them by naming the actor, being specific, and varying sentence structure.

Can I edit Slack messages and emails to eliminate AI tells without losing technical precision?

You can edit Slack messages and emails to eliminate AI tells without losing technical precision by applying drafting and reviewing rules that maintain factual tone and enforce specificity across communication formats.

Does this approach work for drafting system explanations and write-ups?

This approach works for drafting system explanations and write-ups by enforcing core rules across conversations and documents, ensuring you name the human or system actor to avoid passive voice while keeping technical detail intact.

What is the best way to improve readability in technical communication?

The best way to improve readability in technical communication is to cut filler phrases, name the actor in each sentence, be specific, and vary rhythm while maintaining a factual tone across documents.