contributelisted
Install: claude install-skill tobihagemann/turbo
# Contribute
Propose an improvement to a turbo skill as an issue on `tobihagemann/turbo`.
## Step 1: Identify the Proposed Change
Take the proposed changes from the lessons passed in: each names the turbo skill it targets, the change, and the session evidence behind it. Without them, take the proposed changes from conversation context. When neither describes a change to a turbo skill, tell the user there is nothing to contribute and stop.
Read each target skill's current text upstream, so each change is stated against the file as it stands on `main`:
```bash
gh api repos/tobihagemann/turbo/contents/claude/skills/<name>/SKILL.md -H 'Accept: application/vnd.github.raw'
```
Leave out a change whose target skill does not exist upstream, and tell the user.
Present the changes in a summary table:
```
| # | Skill | Change Summary |
|---|-------|----------------|
| 1 | /evaluate-findings | Added handling for security-default findings |
| 2 | /self-improve | Clarified routing for trusted reviewer feedback |
```
Use `AskUserQuestion` to confirm which changes to propose.
## Step 2: Craft Contribution Context
For each change, construct a "why" explanation. The goal: the turbo maintainer should understand what happened and why the existing instructions were insufficient, without learning anything about the contributor's project.
Use this template:
> During [general workflow description], the skill's instructions [what was missing or wrong]. This caused [what happened]. The ch