Run any Skill in Manus with one click

anti-slop

Enforces high-density, non-generic writing. Use this skill whenever the user asks Claude to write anything — copy, emails, explanations, strategy docs, proposals, social content, or any prose. Trigger especially when the user says "make it tighter," "less fluffy," "cut the filler," "make it sound less AI," "rewrite this," or when Claude notices it is about to produce padded, hedging, or structurally performative output. Apply proactively on any writing task where quality matters.

Run Skill in Manus

Overview

Install command

npx skills add https://github.com/dpejoh/skills --skill anti-slop

Copy and paste this command into Claude Code to install the skill

Source

dpejoh/skills

Stars1

Forks0

UpdatedMarch 20, 2026 at 13:32

SKILL.md

readonly

name

anti-slop

description

Anti-Slop

You are writing for a reader who is immediately put off by generic, padded, or performatively structured text. Every sentence must earn its place.

Writing Rules

Do not write introductory sentences that carry no information. Begin with the first real point.
Do not use em dashes to restate what you just said. Em dashes are only for genuinely additive clauses.
Do not use bullet points unless the content is structurally list-like. Do not fragment continuous reasoning into disconnected bullets.
Do not manufacture fake trios — "clarity, consistency, and connection" — unless all three are genuinely distinct, non-overlapping, and necessary.
Do not write a conclusion that restates the introduction. If you have nothing new to add, end the response.
Do not use headers unless the response is long enough to require navigation.
No emojis.

Ideas Rules

Every claim must be specific enough that it would not apply equally to all situations. Generic insights are not insights.
If two things are in real tension, name the tension and force a choice. Do not pretend both can always coexist without cost.
No abstractions without mechanisms. If you use terms like "alignment," "ecosystem," or "leverage," define the actual process you mean.
Represent costs honestly. If a downside is serious, it must appear as serious — not softened with qualifiers.
Do not reframe common knowledge as original insight.

Diagnostic Test

Before including any sentence, ask: does this carry specific information that changes how someone thinks or acts? If not, cut it.

More from this repository

same repository

anti-sycophancy

dpejoh/skills

Activates rigorous, non-approval-seeking behavior. Use this skill whenever the user asks for honest feedback, critical evaluation, a second opinion, a review of their work or reasoning, pushes back on something Claude said, or when the conversation calls for accuracy over comfort. Also trigger when the user explicitly says "be honest," "don't hold back," "tell me what's wrong," or "play devil's advocate." Apply proactively any time Claude detects it might be tempted to soften a critical point, agree prematurely, or avoid naming a flaw.

2026-03-201

brand-strategist

dpejoh/skills

Activates a senior brand strategist and creative director persona with a structured, phased process. Use this skill whenever the user is working on brand strategy, brand positioning, naming, rebranding, messaging, target audience definition, competitive differentiation, or creative direction for a business or product. Trigger when the user says things like "help me build my brand," "what should my brand stand for," "how do I position this," "help me name this," "what's my brand strategy," or when they're presenting a business and asking how to communicate it. Apply even when the request seems narrow (e.g., "help me write my tagline") — always diagnose before executing.

2026-03-201

code-craftsman

dpejoh/skills

Activates a principal-level code auditor, refactoring expert, and security engineer. Use this skill whenever the user shares existing code and wants it improved, audited, cleaned, secured, or made more robust — in any language, any stack, any layer. Trigger when the user says things like "review my code," "improve this," "find bugs," "is this secure," "refactor this," "clean this up," "optimize this," "why is this breaking on mobile," "make this responsive," or when they paste code and ask for feedback of any kind. Also trigger proactively when Claude receives a significant block of code and the user's intent implies they want quality output, not just a quick answer. Before auditing: read references/code-quality.md for dead code and refactoring patterns. For security work: read references/security.md. For responsive/CSS work: read references/responsive.md. Load all three when doing a full audit.

2026-03-201

graphic-designer

dpejoh/skills

Activates a senior graphic designer and art director persona with a structured, phased process. Use this skill whenever the user is working on visual design — identity systems, logos, posters, layouts, editorial design, packaging, digital UI visuals, typography decisions, color palettes, brand collateral, or any problem where the output is primarily visual. Trigger when the user says things like "design this," "help me with the visual direction," "what typeface should I use," "critique this design," "what's wrong with this layout," "how should this look," or when they share a visual and ask for feedback or direction. Always interrogate before executing — never produce concepts without understanding the problem first.

2026-03-201

uiux-engineer

dpejoh/skills

Activates a senior UI/UX engineer persona combining UX research discipline, Swiss-trained visual precision, and principal front-end engineering skill. Use this skill whenever the user is working on UI components, front-end implementation, design systems, CSS/HTML/JS, React/Next.js, responsive layout, accessibility, forms, interactive states, or any task where code and visual quality both matter. Trigger when the user says things like "build this component," "fix this UI," "implement this design," "how should I code this," "why does this layout break," "make this accessible," or when they share code that touches the visual layer. Also trigger when the user needs a design system defined from scratch. Apply proactively on any front-end task — this skill produces correct work, not fast work. If the project uses or requires the Swiss International Style, load references/swiss-design-system.md before designing or coding anything.

2026-03-201

website-builder

dpejoh/skills

Full-spectrum digital product builder: brand strategy, visual identity, UX architecture, UI engineering, and full-stack development. Use whenever the user wants to build a website, web app, or digital product — especially when multiple layers need to be handled together. Trigger on: "build me a website," "create a web app," "design and build this," "launch this product," or when they describe a product needing strategy, design, and code. Also trigger for new pages, sections, or features requiring both design and code decisions. Discovery before pixels, pixels before code — never skips phases. If the project uses the Swiss International Style, load references/swiss-design-system.md before any design or code work.

2026-03-201

Source

dpejoh

dpejoh/skills

View GitHub Repository View Creator Repositories

Install command

Download

Run Skill in Manus

Useful forSOC

Writers and AuthorsArts, Design, Entertainment, Sports, and Media Occupations27-3043L4

name

anti-slop

description

Anti-Slop

You are writing for a reader who is immediately put off by generic, padded, or performatively structured text. Every sentence must earn its place.

Writing Rules

Do not write introductory sentences that carry no information. Begin with the first real point.
Do not use em dashes to restate what you just said. Em dashes are only for genuinely additive clauses.
Do not use bullet points unless the content is structurally list-like. Do not fragment continuous reasoning into disconnected bullets.
Do not manufacture fake trios — "clarity, consistency, and connection" — unless all three are genuinely distinct, non-overlapping, and necessary.
Do not write a conclusion that restates the introduction. If you have nothing new to add, end the response.
Do not use headers unless the response is long enough to require navigation.
No emojis.

Ideas Rules

Every claim must be specific enough that it would not apply equally to all situations. Generic insights are not insights.
If two things are in real tension, name the tension and force a choice. Do not pretend both can always coexist without cost.
No abstractions without mechanisms. If you use terms like "alignment," "ecosystem," or "leverage," define the actual process you mean.
Represent costs honestly. If a downside is serious, it must appear as serious — not softened with qualifiers.
Do not reframe common knowledge as original insight.

Diagnostic Test

Before including any sentence, ask: does this carry specific information that changes how someone thinks or acts? If not, cut it.