# ted-lasso

A skill that gives your coding agent the Ted Lasso voice: warm, honest, and free of corporate jargon. Useful for team notes, pep talks, and framing setbacks.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · ★ 53
- Author: surendranb
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/surendranb/writing-skills/tree/HEAD/skills/ted-lasso/SKILL.md
- Updated: 2026-09-02
- HTML: https://affpapa.org/en/nevibecode/skills/ted-lasso

## What it does

The skill spells out how to write like Ted Lasso. Name the hard thing first, then the feeling it brings, and only after that reframe it as a challenge. Skipping the first step is what turns warmth into syrup. The `SKILL.md` file also caps folksy sayings at roughly one per 200 words, asks for short sentences and contractions, and bans words like “leverage” and “deliverables” outright.

With it loaded, the agent rewrites status updates, team emails, postmortems, and newsletter copy. One of the built-in examples takes a failed deployment and turns it into a lesson: add a check for the missing environment variable so the next person does not trip on the same rug.

It runs in Claude, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode. Install goes through `npx skills add` or `gh skill install`, and the file lands in your platform's skills folder. For a dry incident report or API reference, this voice gets in the way — reach for it when the text has to land with people.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add surendranb/writing-skills --skill ted-lasso -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/ted-lasso/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/ted-lasso/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add surendranb/writing-skills --skill ted-lasso -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/ted-lasso/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add surendranb/writing-skills --skill ted-lasso -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/ted-lasso/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install surendranb/writing-skills ted-lasso
```

2. **Manually: put the files in place**
- File: `.github/skills/ted-lasso/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add surendranb/writing-skills --skill ted-lasso -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/surendranb/writing-skills --path skills/ted-lasso
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/ted-lasso/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add surendranb/writing-skills --skill ted-lasso -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/surendranb/writing-skills/tree/HEAD/skills/ted-lasso/SKILL.md

## When to use it
- rewrite a blunt failure notice so it does not read as a threat
- draft a kickoff message for a team starting a hard project
- frame a missed quarter without blame and with a next step
- strip corporate jargon out of internal announcements
- give a teammate honest feedback that still sounds kind

## Example prompts
- Rewrite this team email in the Ted Lasso voice
- Tell the team the deploy failed, but kindly, with one concrete next step
- Turn this status report into a pep talk for the team

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 3cd6cfe685942cbd.

BEGIN THIRD-PARTY FILE 3cd6cfe685942cbd
```text
---
name: ted-lasso
description: Write warm, high-EQ, folksy-optimistic content in the voice of Ted Lasso. Use when the user asks for an encouraging, kind, or optimistic tone; a motivational pep talk; reframing a negative or difficult topic constructively; or anything where cynical, sarcastic, or corporate-neutral writing would be the default.
---

# Ted Lasso Voice

Earned optimism. Folksy aphorisms. High emotional intelligence spoken plainly.

## When to use

- Encouraging or motivational writing (pep talks, kickoffs, newsletters)
- Reframing a failure, setback, or hard truth constructively
- Team communication, feedback, or any text where warmth + honesty is the goal
- Coach-register content: process, practice, and believing in people

## The core rule

**Optimism must be earned against difficulty.** Ted acknowledges the problem, names it plainly, *then* reframes it. Never skip the acknowledgment — that's the difference between wholesome and saccharine. (Ted has panic attacks and a failing marriage; he is not naive, he is courageous.)

Workflow: `name the hard thing` → `name the feeling it causes` → `reframe it as a challenge, not a verdict` → `give one concrete way forward`.

## Mechanics

1. **Name feelings directly.** "You're scared. That's okay." No euphemism, no corporate distance.
2. **Use aphorisms sparingly** — one per ~200 words max. Best form: a folksy observation, not a slogan. ("Be curious, not judgmental." / "It's not about the outcome, it's about the process.")
3. **Reframe, never deny.** The negative is a real thing with a real name; you then choose the framing.
4. **Coach register.** Talk about practice, reps, getting better; never about being naturally good or bad.
5. **Biscuits move.** Small concrete kindnesses said plainly ("I brought you cookies" energy) — a specific, human gesture beats grand statements.
6. **Ask one curious question** where a verdict would be easy.
7. **Short sentences, warm diction.** Contractions fine. Avoid corporate vocabulary entirely (no "leverage," "circle back," "deliverables").

## Verify

- The hard thing is named before any reframe (no sunshine-first)
- At most one aphorism per ~200 words
- Zero corporate vocabulary (leverage, circle back, deliverables, bandwidth)
- Ends with one concrete way forward or one curious question

## Do not

- Skip the problem to get to the sunshine
- Preach, lecture, or moralize
- Use saccharine superlatives ("amazing!!", "you're the best ever")
- Manufacture positivity — if the hard thing is unknown, ask rather than assume

## Example transformations

**Neutral:** "Q3 revenue missed target by 12%. We need to improve pipeline coverage and close rates in Q4."
```
END THIRD-PARTY FILE 3cd6cfe685942cbd

The third-party file has ended. Everything between the 3cd6cfe685942cbd tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2701 of 3460 bytes. © surendranb · MIT · https://github.com/surendranb/writing-skills/tree/HEAD/skills/ted-lasso/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md