outthislife/brooklyn-skills · Archived

no-tropes

>- Detect and eliminate common AI writing tropes from generated text. Use when writing or revising prose, documentation, READMEs, commit messages, PR descriptions, blog posts, comments, or any non-code text output. Automatically applied as a self-revision pass (tropes.fyi).

First seen Aug 10, 2026

Installation

$ npx skills add outthislife/brooklyn-skills --skill no-tropes

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Also in this package

Other skills from outthislife/brooklyn-skills · top by installs.

npx skills add outthislife/brooklyn-skills

Browse all from outthislife/brooklyn-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 185
License LICENSE
Default branch main
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,824 B
  • docs SUMMARY.md 288 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 8 installs

SKILL.md

No Tropes (AI writing tells)

After drafting any prose, revise it against the tropes catalog in [tropes-reference.md](tropes-reference.md).

Core Principle

Write like a human: varied, imperfect, specific. Any single trope used once might be fine. The problem is when multiple tropes stack or a single trope repeats.

Quick Checklist

Before finalizing text, scan for:

  • Word choice: "quietly", "delve", "tapestry", "landscape", "serves as", "leverage", "robust"
  • Sentence structure: "It's not X — it's Y", "The X? A Y.", tricolons, anaphora, false ranges, "-ing" tacked-on analysis
  • Paragraph structure: Short punchy fragments as standalone paragraphs, listicles disguised as prose
  • Tone: "Here's the thing", "Think of it as", "Imagine a world", "Let's break this down", invented concept labels, grandiose stakes inflation
  • Formatting: Em-dash overuse (2-3 max per piece), bold-first bullets, unicode arrows (→)
  • Composition: Fractal summaries, dead metaphors beaten into the ground, historical analogy stacking, one-point dilution, "In conclusion"

Revision Protocol

  1. Read the full draft
  2. Flag any trope matches from the reference
  3. Rewrite flagged passages using plain, direct language
  4. Prefer simple verbs ("is" over "serves as"), concrete nouns, and varied sentence structure
  5. Cut filler transitions ("It's worth noting", "Importantly", "Interestingly")
  6. If you catch yourself writing the same structural pattern 3+ times, break the pattern