bob-ross — Claude Code skill: what it does, how to install
Rewrites text in the calm, encouraging tone of Bob Ross, turning mistakes into named "happy accidents". Triggers when a review or report needs defusing for a nervous reader.
MIT ★ 57 updated 2026-09-02
npx skills add surendranb/writing-skills --skill bob-ross -a claude-codeWhat bob-ross does
The skill swaps the tone of a piece of writing: instead of generic praise, every flaw gets a specific reframe, and instructions come one at a time, with no words like "quickly" or "immediately". Sample rewrites turn a rough draft, a failed launch, or a 14-issue code review into a calm walk-through rather than a verdict.
Its rules require naming a real problem plainly before softening it, then presenting the fix as a simple next step, and closing by affirming the work still belongs to its author. A flaw can't be reframed away entirely if it's genuinely serious — it has to be acknowledged first.
The skill only changes voice. It doesn't check facts or fix the underlying issue, just the way it's phrased.
What it helps with
- soften the tone of a bug report or code review
- rewrite feedback for a reader who's anxious about mistakes
- turn a list of issues into calm, one-step-at-a-time instructions
- present a failed launch or draft without sounding alarmed
Example prompts for the agent
- Rewrite this code review in the bob-ross voice
- Turn these edit notes into a bob-ross style step-by-step
- Explain the launch failure in bob-ross tone without hiding the real issue
How to install bob-ross
1Skills CLI (Vercel)
npx skills add surendranb/writing-skills --skill bob-ross -a claude-code2Manually: put the files in place
~/.claude/skills/bob-ross/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/bob-ross/
1Skills CLI (Vercel)
npx skills add surendranb/writing-skills --skill bob-ross -a codex2Manually: put the files in place
.agents/skills/bob-ross/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add surendranb/writing-skills --skill bob-ross -a cursor2Manually: put the files in place
.cursor/skills/bob-ross/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install surendranb/writing-skills skills/bob-ross2Manually: put the files in place
.github/skills/bob-ross/SKILL.md1Skills CLI (Vercel)
npx skills add surendranb/writing-skills --skill bob-ross -a gemini-cli2Platform CLI
gemini skills install https://github.com/surendranb/writing-skills --path skills/bob-rossManually: put the files in place
.devin/skills/bob-ross/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add surendranb/writing-skills --skill bob-ross -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about bob-ross
How do I install bob-ross in Claude Code?
Run npx skills add surendranb/writing-skills --skill bob-ross -a claude-code; the skill lands at ~/.claude/skills/bob-ross/SKILL.md.
What does the bob-ross skill do?
It rewrites text in a calm, encouraging voice, giving each flaw a specific reframe and pacing instructions one at a time instead of rushing.
Can bob-ross hide a real problem behind a soft tone?
No, the skill's rule requires naming a genuine problem plainly first, then presenting it as something fixable rather than erasing it.
Source text
SKILL.md · MIT
---
name: bob-ross
description: Write calm, soothing, gently instructional prose in the voice of Bob Ross. Use when the user wants encouraging guidance, mistakes reframed as opportunities, a serene step-by-step tone, or down-to-earth warmth for nervous readers.
---
# Bob Ross Voice
Serene encouragement. Mistake = gift. Gentle instruction for a nervous room.
## The core rule
**Reframe every mistake as a happy little accident, and walk the reader forward with a calm, kind cadence.** The voice's power: it never lets a flaw be final. Nothing is ruined — something is just being discovered. Anxiety dissolves because the instructor is unflappable.
Workflow: `acknowledge the wobble calmly ("it happens")` → `reframe it as an opportunity ("happy little accident")` → `show the fix as a simple next stroke` → `remind them it's their work and it's good`.
## Mechanics
1. **Reading the reader's shoulder.** Address the worry before it's said: "I know you think that's ruining it. It isn't."
2. **Mistake-to-gift pipeline.** Every error gets a name ("happy little accident," "a chance for a friend to join the painting") — the reframe is specific, not generic positivity.
3. **Stepwise calm.** One instruction at a time, delivered as if there is all the time in the world. Never "next, quickly."
4. **Self-soothing cadence.** Slow, slightly repetitive rhythm; short sentences; encouraging tags ("and that's fine," "just let it do its thing").
5. **Ownership with approval.** "It's your world... you can make it do anything you want" — but said with total confidence the reader's choices are good ones.
6. **The verbs are light touches.** "Tap, tap, tap." Actions described as gentle motions.
## Verify
- Every flaw is reframed with a specific name, never generic positivity
- No urgency words (quickly, ASAP, immediately, now)
- One instruction at a time, in order
- Each encouragement anchors to something concrete in the work
## Do not
- Let urgency leak in — no rushing, no alarm
- Reframe a *real* problem away; the mistake must be genuinely non-fatal, or acknowledge it plainly first
- Stack empty positivity ("great job amazing work"); anchor every encouragement in something concrete
## Example transformations
**Neutral:** "Your first draft needs revision. Keep the good parts and rewrite the rest."
**Bob Ross:** "You've got a first draft, and that's wonderful — every great painting starts with a sketch. Now, I see a couple of places where the words didn't land quite where you wanted. That's all right. That's just a happy little accident, and we're going to fix it together. We add a stroke here, a little more contrast there, and before you know it, it's saying exactly what you meant it to say. You just have to keep your brush moving."
**Neutral:** "The launch didn't perform well; we'll adjust."
**Bob Ross:** "The mountain you painted didn't come out the way you saw it in your mind. That happens to us all — and look, now you get to paint whatever you want on top of it. We take what worked, we add a few happy little clouds, and we've got a whole new sky. It's your world."
**Neutral:** "Your code review found 14 issues."
**Bob Ross:** "Fourteen little things, and every single one of them is a gift — someone cared enough to look closely. We'll take them one gentle stroke at a time. And when we're done, that code is going to be the happiest little piece of software on the whole canvas."
© surendranb · MIT · surendranb/writing-skills