no-ai-slop

Review and refine Jira, Confluence, and Bitbucket text to remove AI-generated patterns.

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/lyingparachute/skills --skill no-ai-slop-lyingparachute
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: no-ai-slop
Source: https://github.com/lyingparachute/skills/tree/main/no-ai-slop
Command: npx skills add https://github.com/lyingparachute/skills --skill no-ai-slop-lyingparachute

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that text for Jira, Confluence, or Bitbucket is concise, high-value, and human-sounding, removing AI-generated slop and maintaining clarity and professionalism.

Core Features & Use Cases

  • Text Review and Refinement: Strips out unnecessary detail and maintains a professional tone.
  • AI Slop Identification: Detects and removes common AI-generated patterns.
  • Use Case: Before submitting a design doc for sign-off, use this Skill to ensure the content is clear, direct, and free of AI-generated sloppiness.

Quick Start

Use the no-ai-slop skill to review and refine the text for your design doc 'project-x.md'.

Frequently Asked Questions about no-ai-slop

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

FAQPage Schema
How do I remove AI-generated slop from Confluence and Bitbucket documentation?

To remove AI-generated slop from documentation, you review and refine the text to identify common AI patterns like padded lists, repetition, and unnecessary details. This ensures your Confluence and Bitbucket content remains concise, high-value, and professional.

What is AI slop in professional communication and how do I identify it?

AI slop in professional communication is unnecessary detail, padded lists, and repetition generated by AI models. You can identify it by reviewing text for these common AI-generated patterns and refining the content to maintain a clear, direct, and human-sounding tone.

How do I refine a design doc for sign-off to ensure it sounds human?

To refine a design doc for sign-off and ensure it sounds human, review the text to strip out unnecessary details and AI-generated patterns. This process maintains clarity and professionalism, ensuring the content is direct and high-value before submission.

Does text refinement for Jira issues support the removal of padded lists?

Yes, text refinement for Jira issues supports the removal of padded lists. The process specifically identifies and eliminates common AI-generated patterns, including padded lists and repetition, to maintain a concise and professional tone across your documentation.

What is the best way to eliminate repetition in AI-assisted technical writing?

The best way to eliminate repetition in AI-assisted technical writing is to run a targeted text review that detects and removes common AI-generated patterns. This strips unnecessary details and maintains a professional, human-sounding tone for your documentation.

When should I review text for AI-generated patterns before submitting to Bitbucket?

You should review text for AI-generated patterns before submitting to Bitbucket whenever you want to ensure the content is clear, direct, and free of AI sloppiness. This is crucial before design doc sign-offs to maintain professionalism and high value.