agentleFS
poorvith-mppoorvith-mp/skills-writing/skills/writing-taste/SKILL.md

writing-taste

Skill0 starsChanged 3 months agoMITView on GitHub

Kill tells that make text read as generated: uniform rhythm, filler transitions and recaps. For visual design, see design-taste. Use when eliminating AI writing tells or robotic tone.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Action: If any of these words appear in a draft, highlight and replace them immediately with concrete, unpretentious equivalents.

    line 23
  2. Distinctive:

    Never say something is "extremely efficient".

    line 43
  3. Distinctive:

    Never say an outage was "devastating".

    line 44

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

writing-taste

Core Philosophy

Most AI-generated writing reads like synthetic corporate sludge. Large language models naturally drift toward predictable statistical medians: symmetrical sentence structures, timid hedging, false enthusiasm, and exhausted clichés. Writing taste is the deliberate craft of human editorial discernment. It is the ruthless elimination of generative "AI tells", the injection of visceral sensory and technical nouns, the celebration of strong opinionated stances, and the restoration of rhythmic variance to the prose.


4-Step Anti-AI Stylistic Sanitization Protocol

Step 1: The Banned AI Cliché & Slop Registry

  1. The Instant-Kill Verb & Noun List:
    • Banned Verbs: Delve, Unlock, Unleash, Elevate, Harness, Supercharge, Foster, Demystify, Seamlessly integrate.
    • Banned Nouns: Tapestry, Beacon, Testament, Game-changer, Paradigm, Synergy, Landscape, Journey.
    • Banned Adjectives: Crucial, Pivotal, Vibrant, Robust, Paramount, Holistic, Unprecedented.
    • Banned Structural Phrases: "In today's fast-paced digital landscape", "It's important to remember", "At the end of the day", "Let's dive in".
  2. Action: If any of these words appear in a draft, highlight and replace them immediately with concrete, unpretentious equivalents.

Step 2: Breaking Symmetrical Monotony (The Rule of Variance)

  1. The Symmetrical Triplet Tell:
    • LLMs are obsessed with groups of three: "Our tool is fast, reliable, and scalable." or "We must innovate, adapt, and succeed."
    • Break triplets: Use two contrasting elements, or collapse to a single authoritative noun:
      • Slop: "Building microservices requires patience, discipline, and expertise."
      • Edited: "Building microservices requires discipline."
  2. Radical Sentence Length Variance:
    • Mix 3-word sentences with complex 25-word multi-clause sentences. Contrast breeds attention.

Step 3: Killing Hedges & Corporate Timidity

  1. The Evasion Audit:
    • AI models hate committing to a falsifiable stance. They hedge with qualifiers: "It could be argued that...", "Many believe...", "To some extent..."
    • Strip the hedge: Make the direct, opinionated assertion. If trade-offs exist, state the specific boundary condition with exact numbers:
      • Hedged: "Serverless can sometimes be relatively expensive under certain conditions."
      • Direct: "Serverless compute costs double when API traffic exceeds 2,000 requests per second."

Step 4: Concrete Grounding & Visceral Specificity

  1. Replace Abstract Adjectives with Specific Nouns:
    • Never say something is "extremely efficient"; say it "runs in 4ms with 18MB RAM".
    • Never say an outage was "devastating"; say "the database dropped 14,000 customer sessions during market open".
    • Specificity is the antidote to generative blandness.

Deliverable Format: Editorial Polish & De-Slop Markup (DE-SLOP-AUDIT.md)

# Writing Taste & Anti-AI Slop Audit: [Draft Title]

## 1. Slop Density & Taste Metrics
- **Banned AI Tropes Identified**: 14 instances
- **Symmetrical Triplets Broken**: 6 instances
- **Hedges Eliminated**: 9 instances

## 2. Before-and-After De-Slopping Transformations

### Example 1: Opening Hook
- **AI Slop Original**:
  > *"In today's rapidly evolving tech landscape, it is crucial for engineering teams to harness the power of distributed tracing to unlock unprecedented observability into their systems."*
- **Tasteful Human Edit**:
  > *"If your distributed traces take longer to query than the outage itself, your observability stack is broken."*
- **Why It Works**: Kills 5 AI clichés (*landscape, crucial, harness, power, unlock, unprecedented*); grounds the hook in real developer frustration.

### Example 2: The Triplet Collapse
- **AI Slop Original**:
  > *"Our new billing engine is designed to be seamless, resilient, and cost-effective for modern teams."*
- **Tasteful Human Edit**:
  > *"The billing engine processes 10,000 invoices per second without dropping transactions."*
- **Why It Works**: Replaces three empty marketing adjectives with a verifiable technical benchmark.

## 3. Stylistic Guidelines for This Piece
- Lead with what broke, not corporate optimism.
- Keep sentences punchy. If a sentence has 3 commas, split it into two.

Worked Example: Overhauling an AI-Generated Product Announcement

  • Original Draft: Generated by an LLM; began with "We are thrilled to announce a game-changing milestone in our journey..."
  • Tasteful Rewrite: "We just shipped zero-downtime Postgres migrations. Here is the PR and how to run it locally in Docker."
  • Impact: Social engagement increased 8x; developers commented praising the direct, hype-free announcement.

Verification Checklist

  • Zero words from the Banned AI Cliché Registry appear in the text.
  • Symmetrical three-item lists are eliminated or restructured.
  • Hedging phrases ("perhaps", "arguably", "somewhat") are removed in favor of direct assertions.
  • Abstract marketing adjectives are replaced with concrete numbers, data, or physical nouns.
  • Sentence length varies dynamically across the entire piece.

Anti-Patterns

  • The Polite Corporate Throat-Clear: Spending the first 3 paragraphs summarizing what everyone already agrees on.
  • The Adjective Avalanche: Piling on descriptive superlatives ("revolutionary", "pivotal", "transformative") to mask a lack of substance.
  • Equal-Weight False Balance: Refusing to take a stand on an obvious technical choice by giving equal time to an inferior approach.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.