rockscy/solo-skills

# GitHub Repository: rockscy/solo-skills

**URL:** https://github.com/rockscy/solo-skills
**Author:** rockscy
**Description:** Claude Code skills for people who ship alone. 7 bilingual (EN+中文) skills for solo founders and indie devs: launch tweets, customer emails, decision frameworks, postmortems, and more.
**Homepage:** 
**Language:** Shell

## Stats
- Stars: 2
- Forks: 2
- Open Issues: 1
- Commits: 3
- Created: 2026-04-30T07:58:41Z
- Updated: 2026-05-09T01:31:41Z
- Pushed: 2026-04-30T10:24:13Z

## README
# solo-skills

> Claude Code skills for people who ship alone.

[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
[![Skills](https://img.shields.io/badge/skills-7-blue.svg)](#skills)

English | [简体中文](README.zh.md)

```bash
curl -fsSL https://raw.githubusercontent.com/rockscy/solo-skills/main/install.sh | bash
```

---

## What is this?

A small, opinionated set of [Claude Code](https://claude.com/claude-code) skills for the tasks solo founders and indie devs actually do every day: writing launch tweets, replying to awkward customer emails, running a 5-minute personal standup, turning a vague bug report into something actionable, deciding what to ship next when you're alone with the call.

Most skill packs assume you have a team. **This one assumes you don't.**

---

## Why?

| | Most skill packs | solo-skills |
|---|---|---|
| Audience | "Real engineers" (broad) | Solo founders, indie devs |
| Boundaries | "Use when…" only | "Use when…" **AND "Do NOT use when…"** |
| Examples | Often abstract | Worked input → output for every skill |
| Install | Manual copy | One-line `curl \| bash` |

The **"Do NOT use when…"** section is the core differentiator. Force-applying a framework when it doesn't fit is the #1 way solo devs waste a Saturday. Every skill in this pack tells you when it should *not* fire.

---

## Skills

| Skill | What it does |
|---|---|
| [ship-decision](skills/ship-decision/SKILL.md) | Force a fast, regret-minimizing call between 2–3 product options. |
| [launch-tweet](skills/launch-tweet/SKILL.md) | Draft a launch tweet or 3–4 tweet thread, no hype words. |
| [changelog-from-commits](skills/changelog-from-commits/SKILL.md) | Convert raw git log into user-facing release notes. |
| [bug-from-user](skills/bug-from-user/SKILL.md) | Convert a confusing customer message into a reproducible bug report. |
| [standup-solo](skills/standup-solo/SKILL.md) | 5-minute personal standup: shipped / blocked / today's #1. |
| [email-customer](skills/email-customer/SKILL.md) | Polite-but-firm reply to refunds, scope creep, complaints. |
| [postmortem-solo](skills/postmortem-solo/SKILL.md) | ≤350-word blame-free postmortem after a missed deadline or outage. |

---

## Install

### Option 1: One-liner (recommended)

```bash
curl -fsSL https://raw.githubusercontent.com/rockscy/solo-skills/main/install.sh | bash
```

This drops the seven skill directories into `~/.claude/skills/`. Existing files of the same name are **never** overwritten — the installer skips them and tells you which.

### Option 2: Manual

```bash
git clone https://github.com/rockscy/solo-skills.git
cp -r solo-skills/skills/* ~/.claude/skills/
```

### Verify

Open Claude Code and type `/`. You should see `ship-decision`, `launch-tweet`, etc. in the skill list.

---

## How to use

Inside any Claude Code session, the skills auto-trigger when you describe a matching situation. You can also invoke explicitly:

```
/ship-decision

I'm stuck choosing between rebuilding my landing page in Framer or sticking with my hand-coded Next.js page. I have ~6 hours of focused time this weekend.
```

Claude reads `SKILL.md`, applies the framework, and responds in the prescribed format.

---

## Design principles

1. **Boundaries first.** Every skill leads with *when not to use*. Wrong skill > no skill.
2. **One sentence beats one paragraph.** Output formats enforce brevity.
3. **Show input → output.** Every skill includes a worked example, not just guidelines.
4. **No corporate voice.** No "I'm excited", no "per our policy", no emoji decoration.

---

## Contributing

PRs welcome. Read [CONTRIBUTING.md](CONTRIBUTING.md). The bar:

- Skill solves a real problem a solo dev hits **monthly or more often**.
- Has a "When NOT to use" section. (Hard requirement.)
- Has at least one worked input → output example.
- Output format is concrete (table, structured text, fixed sections) — no "be helpful" vibes.

---

## License

[MIT](LICENSE) — copy, modify, ship, sell. No attribution required, but it's appreciated.