Agent skill

Contribute Turbo

Propose a turbo skill improvement upstream by filing a GitHub issue against the turbo repo.

MITAuto-check passedDevelopment

Install Contribute Turbo

skills CLI

$ npx skills add tobihagemann/turbo --skill contribute-turbo -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install tobihagemann/turbo contribute-turbo --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/codex/skills/contribute-turbo .claude/skills/contribute-turbo && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "contribute-turbo" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/contribute-turbo into .claude/skills/contribute-turbo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "contribute-turbo", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/tobihagemann/turbo/tree/main/codex/skills/contribute-turbo

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add tobihagemann/turbo --skill contribute-turbo -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install tobihagemann/turbo contribute-turbo --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .agents/skills && cp -r skills-src/codex/skills/contribute-turbo .agents/skills/contribute-turbo && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "contribute-turbo" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/contribute-turbo into .agents/skills/contribute-turbo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "contribute-turbo", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add tobihagemann/turbo --skill contribute-turbo -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install tobihagemann/turbo contribute-turbo --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/codex/skills/contribute-turbo .cursor/skills/contribute-turbo && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "contribute-turbo" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/contribute-turbo into .cursor/skills/contribute-turbo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "contribute-turbo", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/tobihagemann/turbo.git --path codex/skills/contribute-turbo

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add tobihagemann/turbo --skill contribute-turbo -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install tobihagemann/turbo contribute-turbo --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/codex/skills/contribute-turbo .gemini/skills/contribute-turbo && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "contribute-turbo" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/contribute-turbo into .gemini/skills/contribute-turbo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "contribute-turbo", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install tobihagemann/turbo contribute-turbo

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add tobihagemann/turbo --skill contribute-turbo -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .github/skills && cp -r skills-src/codex/skills/contribute-turbo .github/skills/contribute-turbo && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "contribute-turbo" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/contribute-turbo into .github/skills/contribute-turbo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "contribute-turbo", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add tobihagemann/turbo --skill contribute-turbo -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install tobihagemann/turbo contribute-turbo --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/codex/skills/contribute-turbo .opencode/skills/contribute-turbo && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "contribute-turbo" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/contribute-turbo into .opencode/skills/contribute-turbo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "contribute-turbo", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: contribute-turbo
GitHub stars: 408
Token cost: ~1.1k tokens
SKILL.md length: 511 words
Files: 1
Skills in repo: 81
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Propose a turbo skill improvement upstream by filing a GitHub issue against the turbo repo.

Works in 3 steps: Identify the Proposed Change → Craft Contribution Context → Run $create-issue Skill
The user asks to contribute to turbo
SKILL.md covers Step 1: Identify the Proposed…, Step 2: Craft Contribution… and Step 3: Run $create-issue Skill
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Contribute Turbo is an agent skill from tobihagemann/turbo. Propose a turbo skill improvement upstream by filing a GitHub issue against the turbo repo. Use when the user asks to "contribute to turbo", "submit turbo changes", "contribute back", "suggest a turbo improvement", or "upstream my changes".

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. It works with GitHub and Turborepo. The repository describes itself as: Reusable workflows for planning, building, reviewing, and shipping with Claude Code and Codex. The licence is MIT.

When your agent uses it

The user asks to contribute to turbo
Submit turbo changes
Contribute back
Suggest a turbo improvement

Example prompts

“contribute to turbo”
“submit turbo changes”
“contribute back”
“/contribute-turbo”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

Identify the Proposed Change
Craft Contribution Context
Run $create-issue Skill

What it can do on your machine

Read from SKILL.md and the folder at commit 931eda5. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Contribute Turbo loads about 1.1k tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 511 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~64
When it runs · the whole SKILL.md, loaded when a task matches: ~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from tobihagemann/turbo at commit 931eda5, republished under its MIT licence (© tobihagemann). 511 words, ~1,080 tokens.

Download SKILL.mdSave it as .claude/skills/contribute-turbo/SKILL.md (or your agent's skills folder).

name: contribute-turbo
description: Propose a turbo skill improvement upstream by filing a GitHub issue against the turbo repo. Use when the user asks to "contribute to turbo", "submit turbo changes", "contribute back", "suggest a turbo improvement", or "upstream my changes".

Contribute Turbo

Propose an improvement to a turbo skill as an issue on tobihagemann/turbo.

Step 1: Identify the Proposed Change

Confirm the local repo exists:

bash

test -d ~/.turbo/repo

If it does not, tell the user to run the Turbo setup first and stop.

Detect skills whose installed copy has drifted from the repo baseline:

bash

for skill in ~/.agents/skills/*/; do
  name=$(basename "$skill")
  repo_dir=~/.turbo/repo/codex/skills/"$name"
  [ -d "$repo_dir" ] || continue
  diff -rq "$skill" "$repo_dir" >/dev/null 2>&1 && continue
  echo "$name"
done

For each drifted skill, read both versions of every file that differs and the single version of every file present on one side only. Classify each hunk and each one-sided file:

Correction — a session edit meant to improve the skill upstream. Include it in the proposal.
Customization — a persistent local addition that belongs to this machine only (extra workflow steps, personal paths, machine-specific notes, internal references). Leave it out of the proposal.
Upstream-newer — content the repo copy carries and the installed copy lacks, left behind by a Skip or Exclude during an earlier update. Leave it out of the proposal.
Ambiguous — use request_user_input to confirm classification.

When no corrections survive classification, take the proposed change from conversation context instead. When the conversation describes no change either, tell the user there is nothing to contribute and stop.

Present the corrections 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 request_user_input to confirm which corrections 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 change [what it does] so that [benefit].

Example:

During a code review session, the evaluate-findings skill encountered a finding with security-default severity. The existing instructions only handled critical, high, medium, and low severities, causing the finding to be silently dropped. The change adds security-default to 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 codex/skills/<name>/, the step or section it belongs in, and the exact replacement text or a diff.

Show full SKILL.md (167 more words)Show less

Privacy Filter

Before finalizing, verify the whole proposal — the "why" explanation, the cited paths, and the proposed replacement text — contains none of the following:

Project or repo names
File paths from the user's project
Company or product names
API keys, URLs, or credentials
Business logic or domain-specific terminology that identifies the project
User names beyond the contributor's GitHub handle

Output the drafted proposal as text. Then use request_user_input for approval. The user must approve the proposal before proceeding.

Step 3: Run `$create-issue` Skill

Use update_plan to track each approved concern, restating any remaining steps of a parent workflow alongside them. 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 call update_plan to mark this step completed and continue with the next step of the active workflow.

Files

Just SKILL.md in codex/skills/contribute-turbo of tobihagemann/turbo.

Open the folder on GitHubat commit 931eda5

Compare with similar skills

Contribute Turbo next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Contribute Turbo compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Contribute Turbo this skilltobihagemann/turbo	408	—	~1.1k	Automated safety check: Pass	MIT	2 days ago
Scaffold Nextjsmblode/agent-skills	144	—	~2.8k	Automated safety check: Pass	MIT	2 days ago
PR Babysitteropeninterpreter/openinterpreter	69k	3 repos	~4.2k	Automated safety check: Pass	Apache-2.0	today
Greplooponyx-dot-app/onyx	32k	4 repos	~3.3k	Automated safety check: Pass	MIT	yesterday
Check PRonyx-dot-app/onyx	32k	2 repos	~2.3k	Automated safety check: Pass	MIT	yesterday
Setup Matt Pocock Skillsbestofjs/bestofjs	3.1k	20 repos	~1.7k	Automated safety check: Pass	MIT	6 days ago

Similar skills

Scaffold Nextjs
mblode/agent-skills
Scaffolds a Next.js turborepo with Blode UI, icons, Ultracite (oxlint/shadcn), workspace hooks, and GitHub/Vercel setup.
144 GitHub stars~2.8k tokensUpdated 2 days ago
DevelopmentAuto-check passed
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
69k GitHub starsUsed in 3 repos~4.2k tokens
DevelopmentAuto-check passed
Greploop
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
32k GitHub starsUsed in 4 repos~3.3k tokens
DevelopmentAuto-check passed
Check PR
onyx-dot-app/onyx
Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.
32k GitHub starsUsed in 2 repos~2.3k tokens
DevelopmentAuto-check passed
Setup Matt Pocock Skills
bestofjs/bestofjs
Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout.
3.1k GitHub starsUsed in 20 repos~1.7k tokens
DevelopmentAuto-check passed
Contributor-First PR Merge
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
16k GitHub starsUsed in 1 repo~847 tokens
DevelopmentAuto-check passed

Questions about Contribute Turbo

What does Contribute Turbo do?

Propose a turbo skill improvement upstream by filing a GitHub issue against the turbo repo. Contribute Turbo is an agent skill from tobihagemann/turbo. Propose a turbo skill improvement upstream by filing a GitHub issue against the turbo repo.

When should I use Contribute Turbo?

Contribute Turbo fits situations like: the user asks to contribute to turbo; submit turbo changes; contribute back; suggest a turbo improvement.

How do I install Contribute Turbo in Claude Code?

Run `npx skills add tobihagemann/turbo --skill contribute-turbo -a claude-code`. Or copy the skill folder (codex/skills/contribute-turbo in tobihagemann/turbo) into .claude/skills/contribute-turbo in your project. Claude Code loads it when a task matches its description.

How do I install Contribute Turbo in Codex?

Run `npx skills add tobihagemann/turbo --skill contribute-turbo -a codex`. Or copy the skill folder (codex/skills/contribute-turbo in tobihagemann/turbo) into .agents/skills/contribute-turbo in your project. Codex loads it when a task matches its description.

Can I use Contribute Turbo in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tobihagemann/turbo --skill contribute-turbo -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/contribute-turbo, .gemini/skills/contribute-turbo, .github/skills/contribute-turbo and .opencode/skills/contribute-turbo in your project.

What does Contribute Turbo need to run?

SKILL.md names no scripts, command-line tools or credentials: Contribute Turbo is instructions for the agent only.

Does Contribute Turbo access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Contribute Turbo safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Contribute Turbo use?

Contribute Turbo is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Contribute Turbo use?

About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Contribute Turbo?

Skills that share tags, products or a category with Contribute Turbo: Scaffold Nextjs (mblode/agent-skills, 144 stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Greploop (onyx-dot-app/onyx, 32k stars) and Check PR (onyx-dot-app/onyx, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Contribute Turbo?

tobihagemann (a GitHub user) maintains it in tobihagemann/turbo, which has 408 GitHub stars. The repository holds 81 skills in this directory. The repository was last updated on October 9, 2026.

Source: tobihagemann/turbo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Contribute Turbo

Install Contribute Turbo

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Contribute Turbo

Step 1: Identify the Proposed Change

Step 2: Craft Contribution Context

Privacy Filter

Step 3: Run `$create-issue` Skill

Files

Compare with similar skills

Similar skills

Scaffold Nextjs

PR Babysitter

Greploop

Check PR

Setup Matt Pocock Skills

Contributor-First PR Merge

More from tobihagemann/turbo

Consult Oracle

Fetch PR Comments

Recall Rationale

Resolve PR Comments

Resolve PR Comments

Assess Technical Debt

Questions about Contribute Turbo

Install Contribute Turbo

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Contribute Turbo

Step 1: Identify the Proposed Change

Step 2: Craft Contribution Context

Privacy Filter

Step 3: Run $create-issue Skill

Files

Compare with similar skills

Similar skills

More from tobihagemann/turbo

Related

Questions about Contribute Turbo

Step 3: Run `$create-issue` Skill