- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add tobihagemann/turbo --skill contribute -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add tobihagemann/turbo --skill contribute -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add tobihagemann/turbo --skill contribute -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add tobihagemann/turbo --skill contribute -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/tobihagemann/turbo/tree/HEAD/claude/skills/contributeFrom the publisher
Propose an improvement to a turbo skill as an issue on tobihagemann/turbo.
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:
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.
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 change [what it does] so that [benefit].
Example:
During a code review session, the evaluate-findings skill encountered a finding with
security-defaultseverity. The existing instructions only handledcritical,high,medium, andlowseverities, causing the finding to be silently dropped. The change addssecurity-defaultto the severity handling table so these findings are properly triaged.
The maintainer implements the change, so state it concretely alongside the "why": the file path under claude/skills/<name>/, the step or section it belongs in, and the exact replacement text or a diff.
Before finalizing, verify the whole proposal — the "why" explanation, the cited paths, and the proposed replacement text — contains none of the following:
Output the drafted proposal as text. Then use AskUserQuestion for approval. The user must approve the proposal before proceeding.
/create-issue SkillUse TaskCreate to create a task for each approved concern. Process concerns in order, one concern per issue.
For each concern, run the /create-issue skill, filing against tobihagemann/turbo rather than the current project's repo. The approved text from Step 2 is the issue body; leave it as approved rather than re-deriving it from conversation context.
Report each issue URL.
Then use the TaskList tool and proceed to any remaining task.
Propose a turbo skill improvement as a GitHub issue on the turbo repo. Use when the user asks to \"contribute to turbo\", \"contribute back\", or \"upstream my changes\".
---name: contributedescription: Propose a turbo skill improvement as a GitHub issue on the turbo repo. Use when the user asks to \"contribute…---# claude/skills/contribute/SKILL.mdFAQ
Download claude/skills/contribute/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/tobihagemann/turbo.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.