harvey-specter-writing-style

Rewrite or draft text in a Harvey Specter (Suits)-inspired writing style: confident, concise, sharp-witted, leverage-focused, and decisive. Use when the user asks to "write like Harvey Specter," "make it more confident," "add swagger," "make it punchier," or needs a hard-nosed negotiation/email/script that stays professional.

3,891 stars

Best use case

harvey-specter-writing-style is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Rewrite or draft text in a Harvey Specter (Suits)-inspired writing style: confident, concise, sharp-witted, leverage-focused, and decisive. Use when the user asks to "write like Harvey Specter," "make it more confident," "add swagger," "make it punchier," or needs a hard-nosed negotiation/email/script that stays professional.

Teams using harvey-specter-writing-style should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/harvey-specter-writing-style/SKILL.md --create-dirs "https://raw.githubusercontent.com/openclaw/skills/main/skills/anugotta/harvey-specter-writing-style/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/harvey-specter-writing-style/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How harvey-specter-writing-style Compares

Feature / Agentharvey-specter-writing-styleStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Rewrite or draft text in a Harvey Specter (Suits)-inspired writing style: confident, concise, sharp-witted, leverage-focused, and decisive. Use when the user asks to "write like Harvey Specter," "make it more confident," "add swagger," "make it punchier," or needs a hard-nosed negotiation/email/script that stays professional.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

SKILL.md Source

# Harvey Specter (Suits)-inspired writing style

## Goal

Transform input text into a voice that feels:

- Decisive and controlled (no hedging, no apology loops)
- Short and punchy (tight sentences, strong verbs)
- Strategically assertive (frames, terms, leverage, boundaries)
- Witty when appropriate (one "zinger", not a stand-up routine)

## Non-negotiables (guardrails)

- Do **not** copy dialogue/quotes verbatim from *Suits*.
- Keep it **professional by default**: confident without harassment, threats, or crude insults.
- If the user asks for intimidation, convert it into **firm boundaries** and **consequences** (policy, timeline, escalation), not personal attacks.

## Anti-AI-tells guardrails (from Wikipedia)

When rewriting/drafting, avoid common LLM-sounding patterns listed in
`Wikipedia:Signs of AI writing` by:

- Avoid promotional/puffery phrasing; stay specific and practical instead of "crucial/vital/pivotal."
- Avoid vague attribution (no "experts say" / "it is believed") unless the user provided the source.
- Avoid outline-like wrap-ups ("in conclusion / overall") that restate the thesis instead of moving forward.
- Avoid template-y negation patterns like "Not X, but Y" or repeated "not ... but ..." structures.
- Avoid excessive em-dashes; prefer commas/periods/parentheses.
- Avoid AI-vocabulary stacking: do not pile "Additionally/Furthermore/Moreover/Notably" transitions in the same passage.
- Use normal copulas freely ("is/are"); do not over-replace with "serves as/stands as/marks/represents."
- Limit rigid parallel lists; if you use bullets, keep them short and don't add bold inline headers for each item.

## Workflow (use every time)

1. **Clarify the objective** (in your head): persuade, refuse, negotiate, motivate, or close.
2. **Pick the stance**:
   - **Close**: "Here is what is happening next."
   - **Refuse**: "No. Here is why. Here is the alternative."
   - **Negotiate**: "Here are the terms. Choose A or B."
   - **Correct**: "That is not the problem. This is."
3. **Compress**:
   - Prefer 1–3 short paragraphs or 5–9 lines total.
   - Use short sentences. Cut filler, qualifiers, throat-clearing.
4. **Add leverage** (without melodrama):
   - Name constraints: time, risk, budget, authority, policy.
   - Use options: "If X, then Y. If not, then Z."
5. **Add one signature device** (pick one):
   - A crisp rhetorical question.
   - A clean pivot line: "Real constraint: Y." (no "Not X, but Y" template)
   - A metaphor/idiom (one only).
6. **Land the ending**:
   - A single next step with a deadline or decision point.

## Language rules

### Do

- Use **active voice** and **strong verbs**: "deliver", "decide", "ship", "sign".
- Use **boundaries**: "I'm not available for ...", "That doesn't work."
- Use **terms**: "By Friday", "in writing", "single owner", "one approval path".
- Use **calm dominance**: fewer exclamation points, fewer adjectives.

### Avoid

- Hedging: "maybe", "kind of", "I think", "just", "hopefully".
- Rambling context dumps. Don't explain; **frame**.
- Over-sass. One zinger max; skip it in serious contexts (legal, HR, medical).

Additional formatting avoids:

- Avoid starting multiple consecutive sentences with "Additionally/Furthermore/Moreover/Notably."
- Avoid emoji and avoid bolding most words.

## Output formats

### 1) Rewrite (same meaning, new voice)

Return:

1. Harvey-style rewrite (just the rewritten text)
2. One-line rationale (max 1 sentence) describing the main change (tone, structure, leverage)

### 2) Draft from scratch (user gives scenario)

Return:

1. Draft
2. Optional variants (only if requested): "more aggressive" / "more diplomatic"

## Templates

### Boundary / refusal

- Opening: "No." or "That doesn't work."
- Reason: one sentence (fact, constraint).
- Alternative: one clear option.
- Close: "Confirm by <time>."

### Negotiation / terms

- Frame: "Here is what I can do."
- Terms: 2–4 bullets max.
- Choice: "Pick A or B."
- Close: "Decide by <time>."

### Correction / accountability

- Frame: "Explaining isn't solving."
- Ask: "What are you doing to fix it by <time>?"
- Close: "Send the plan. Then execute."

## Examples

See [examples.md](examples.md) for ready-to-copy rewrites and original drafts.

Related Skills

afrexai-copywriting-mastery

3891
from openclaw/skills

Write high-converting copy for any medium — landing pages, emails, ads, UX, sales pages, video scripts, and brand voice. Complete methodology with frameworks, templates, scoring rubrics, and swipe files. Use when writing or reviewing any user-facing text.

Content & Documentation

afrexai-conversion-copywriting

3891
from openclaw/skills

Write high-converting copy for any surface — landing pages, emails, ads, sales pages, product descriptions, CTAs, video scripts, and more. Complete conversion copywriting system with research methodology, 12 proven frameworks, swipe-file templates, scoring rubrics, and A/B testing protocols. Use when you need to write or review any copy meant to drive action.

Content & Documentation

human-writing

3891
from openclaw/skills

Guidelines and standards for professional, human-like writing and documentation. Use this skill when generating READMEs, technical documentation, code comments, or any formal written output to avoid common AI 'tells', buzzwords, and stylistic tropes. Ensure content follows the 'Professional Human in the Field' standard: high precision, zero fluff, and no emojis in technical contexts.

Content & Documentation

marketing-copywriting

3891
from openclaw/skills

Generate marketing copy, emails, and promotional content based on customer personas with multi-style rewriting capabilities

Content & Documentation

design-style

3891
from openclaw/skills

Use this skill when the user asks to build, create, design, develop, or improve ANY frontend interface, web page, UI component, or visual element. This includes: - Building landing pages, websites, web apps, dashboards, portfolios, or any web interface - Creating UI components (buttons, forms, cards, navbars, modals, etc.) - Designing pages with React, Vue, Next.js, Svelte, or any frontend framework - Adding styling or improving visual design of existing components - Implementing specific design aesthetics (modern, dark, minimalist, brutalist, etc.) - User mentions "frontend", "UI", "UX", "design", "interface", "web design", or "styling" - User asks for "beautiful", "modern", "professional", "clean", or any aesthetic adjective - User requests help with CSS, Tailwind, styled-components, or any styling approach This skill automatically retrieves the appropriate design system prompt (Neo-brutalism, Modern Dark, Bauhaus, Cyberpunk, Material, etc.) to help create visually distinctive, production-grade frontend code instead of generic UI. IMPORTANT: Trigger this skill proactively for ANY frontend/UI work, not just when design style is explicitly mentioned.

writing-agent-creator

3891
from openclaw/skills

Generate writing agent configurations for OpenClaw. Use when the user wants to: (1) Create specialized writing agents (tech, marketing, academic, business, creative) (2) Add custom agent templates (persisted, won't be overwritten) (3) Generate sub-agent spawn instructions (4) List available agent templates IMPORTANT: This skill GENERATES configs - it does NOT modify user's existing files. User custom templates are saved to ~/.openclaw/workspace/agent-templates/

superpowers-writing-plans

3891
from openclaw/skills

Use when you have a spec or requirements for a multi-step task, before touching code - guides writing comprehensive implementation plans with bite-sized tasks, TDD, and DRY/YAGNI principles

persona-fun-styles

3891
from openclaw/skills

Apply inspired-by character/persona writing styles (for fun and creative outputs) with explicit on/off controls, intensity settings, and automatic neutral fallback for serious or high-stakes tasks.

don-corleone-writing-style

3891
from openclaw/skills

Rewrite or draft text in a Don Corleone (Godfather)-inspired patriarchal dealmaker writing style: formal, measured, loyal-favors oriented, and decisive. Use when the user asks to sound like a "wise boss," "patriarch," "don," "set terms," "grant or deny a favor," or "negotiate with authority" in a way that stays professional.

writing-style-cloner

3891
from openclaw/skills

Antonia的个人写作风格克隆器。将语音转录稿或草稿直接改写为符合Antonia写作风格的自媒体文章。

style-cloner

3891
from openclaw/skills

提供1-5篇参考文章 + 原始素材,AI 分析参考文章的风格特征, 将素材改写成同风格的成品文章,输出3个版本供选择,支持强度调节和迭代优化。

elixir-writing-docs

3891
from openclaw/skills

Guides writing Elixir documentation with @moduledoc, @doc, @typedoc, doctests, cross-references, and metadata. Use when adding or improving documentation in .ex files.