New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Run Checks

by tobihagemann in tobihagemann/turbo

Run the project's full verification gate: every check the project defines as a pass/fail condition, built from its CI config, check scripts, and configured tools, or from a formatter-linter-test…

MITAuto-check passedDevelopment

Install Run Checks

skills CLI
$ npx skills add tobihagemann/turbo --skill run-checks -a claude-code

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

GitHub CLI
$ gh skill install tobihagemann/turbo run-checks --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/run-checks .claude/skills/run-checks && 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/

Facts

Skill name
run-checks
GitHub stars
408
Token cost
~628 tokens
SKILL.md length
338 words
Files
1
Skills in repo
81
Repo updated
First seen
Licence
MIT

At a glance

Run the project's full verification gate: every check the project defines as a pass/fail condition, built from its CI config, check scripts, and configured tools, or from a formatter-linter-test…

  • Works in 4 steps: CI config — where present, it is the… → Check scripts — package-manager scripts… → Configured tools — any tool with a… → …
  • The user asks to run checks
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Run the verification gate

What it does

Run Checks is an agent skill from tobihagemann/turbo. Run the project's full verification gate: every check the project defines as a pass/fail condition, built from its CI config, check scripts, and configured tools, or from a formatter-linter-test baseline when it declares none. Use when the user asks to "run checks", "run the verification gate", "run lint and tests", "run the test suite", "check that this passes", "does this pass CI", or "run the project's checks".

Its SKILL.md is about 630 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, covering Linting and formatting and Test generation. 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 run checks
  • Run the verification gate
  • Run lint and tests
  • Run the test suite

Example prompts

  • “run checks”
  • “run the verification gate”
  • “run lint and tests”
  • “/run-checks”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. CI config — where present, it is the authoritative gate; run the checks it enforces.
  2. Check scripts — package-manager scripts (check, verify, lint, typecheck, build), Makefile, Taskfile, or justfile targets, or a combined…
  3. Configured tools — any tool with a config committed to the repo, such as a dead-code or unused-dependency gate. A committed config means…
  4. Baseline — when the project declares nothing more, run the formatter, then the linter, then the build where the project produces one, then…

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.

    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

Run Checks loads about 628 tokens when it runs. Until then it costs about 107 tokens; SKILL.md has 338 words of instructions outside code blocks.

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

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). 338 words, ~628 tokens.

Download SKILL.mdSave it as .claude/skills/run-checks/SKILL.md (or your agent's skills folder).
name
run-checks
description
Run the project's full verification gate: every check the project defines as a pass/fail condition, built from its CI config, check scripts, and configured tools, or from a formatter-linter-test baseline when it declares none. Use when the user asks to "run checks", "run the verification gate", "run lint and tests", "run the test suite", "check that this passes", "does this pass CI", or "run the project's checks".

Run Checks

Build the gate by combining every source below that the project declares (sources 1-3); run the baseline (source 4) only when the project declares none of them. Passing the gate must mean the project's own checks (and CI, where it exists) pass.

  1. CI config — where present, it is the authoritative gate; run the checks it enforces.
  2. Check scripts — package-manager scripts (check, verify, lint, typecheck, build), Makefile, Taskfile, or justfile targets, or a combined format+lint script.
  3. Configured tools — any tool with a config committed to the repo, such as a dead-code or unused-dependency gate. A committed config means the project treats the tool as a gate; run it even when no script or CI invokes it. Do not run such a tool when the project has not configured it.
  4. Baseline — when the project declares nothing more, run the formatter, then the linter, then the build where the project produces one, then the test suite.

Run the formatter first so later checks see formatted code, then the rest. A check passes only when its command exits 0. Judge each run by its exit status and the runner's full summary, never by filtering the output for selected summary lines. Fix any failure the tools do not auto-resolve, then re-run each failed check and judge it by the re-run. When a fix, or a tool resolving its own failure, edits the code while the gate is running, re-run every check whose passing run started before that edit. When the same edit keeps recurring across re-runs, stop and report the checks that produce it. For test failures, run the $investigate skill to diagnose the root cause, apply the suggested fix, and re-run; if investigation finds no root cause, stop and report with its findings.

State which sources the project declared, which checks ran, and each check's final exit status, so a narrower-than-intended gate or a failing check stays visible.

Then call update_plan to mark this step completed and continue with the next step of the active workflow.

© tobihagemann, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

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

Open the folder on GitHubat commit 931eda5

Compare with similar skills

Run Checks 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.

Run Checks compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Run Checks this skilltobihagemann/turbo408—~628Automated safety check: PassMIT
Bench Batonnooga/let-go570—~821Automated safety check: PassMIT
Auto HarnessPacificStudio/openase268—~1.2kAutomated safety check: PassApache-2.0
Conducty Shiprobertbarclayy/conducty176—~1.9kAutomated safety check: PassMIT
UI OnlyOutThisLife/brooklyn-skills199—~364Automated safety check: PassMIT
Pre Commitwellwelwel/poku1.2k—~728Automated safety check: PassMIT

Similar skills

  • Bench Baton

    nooga/let-go

    Coordinate heavy local workloads across worktrees, processes, and subagents — benchmarks and timing-sensitive gates run exclusively on a quiesced machine, while builds, test suites, regeneration…

    570 GitHub stars~821 tokensUpdated today
    DevelopmentAuto-check passed

  • Auto Harness

    PacificStudio/openase

    Diagnose and strengthen a repository's harness layer: AGENTS.md rules, knowledge layout, architecture boundaries, lint and type gates, API and generated-client contracts, test scaffolding…

    268 GitHub stars~1.2k tokensUpdated 2 mo ago
    DevelopmentAuto-check passed

  • Conducty Ship

    robertbarclayy/conducty

    Pre-merge / pre-deploy gate. An agent skill from robertbarclayy/conducty.

    176 GitHub stars~1.9k tokensUpdated 3 mo ago
    DevelopmentAuto-check passed

  • UI Only

    OutThisLife/brooklyn-skills

    While iterating on UI, do not waste time on tsc, lint, typecheck, format, full test suites, commit, or push until the user likes how it looks and works.

    199 GitHub stars~364 tokensUpdated 5 days ago
    DevelopmentAuto-check passed

  • Pre Commit

    wellwelwel/poku

    Run the mandatory pre-commit checks for the poku repository before staging a commit.

    1.2k GitHub stars~728 tokensUpdated 3 mo ago
    Testing & QAAuto-check passed

  • Zizkadb Test

    ZIZKA-AI-SL/ZizkaDB

    Run the full ZizkaDB test suite across all layers — lint, Python unit tests, SDK tests, MCP tests, TypeScript tests, and dashboard build verification.

    130 GitHub stars~358 tokensUpdated 4 days ago
    Testing & QAAuto-check passed

More from tobihagemann/turbo

All 81 skills in this repo

  • Consult Oracle

    tobihagemann/turbo

    Consult ChatGPT Pro via ChatGPT browser automation for problems that resist standard approaches.

    408 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Fetch PR Comments

    tobihagemann/turbo

    Fetch and summarize review feedback and conversation from a GitHub PR (unresolved review threads, review bodies, and PR conversation comments) without making changes.

    408 GitHub stars~967 tokensUpdated yesterday
    Auto-check passed

  • Recall Rationale

    tobihagemann/turbo

    Recall why a past change was made by locating the Claude Code transcript that produced it.

    408 GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed

  • Resolve PR Comments

    tobihagemann/turbo

    Evaluate, fix, answer, and reply to GitHub pull request review comments and conversation comments.

    408 GitHub stars~3.8k tokensUpdated yesterday
    Auto-check passed

  • Resolve PR Comments

    tobihagemann/turbo

    Evaluate, fix, answer, and reply to GitHub pull request review comments and conversation comments.

    408 GitHub stars~3.8k tokensUpdated yesterday
    Auto-check passed

  • Assess Technical Debt

    tobihagemann/turbo

    Assess project-wide structural technical debt: complexity hotspots, deprecated API usage, duplication clusters, architecture rot, and low-value tests.

    408 GitHub stars~2.8k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Run Checks

What does Run Checks do?

Run the project's full verification gate: every check the project defines as a pass/fail condition, built from its CI config, check scripts, and configured tools, or from a formatter-linter-test…. Run Checks is an agent skill from tobihagemann/turbo. Run the project's full verification gate: every check the project defines as a pass/fail condition, built from its CI config, check scripts, and configured tools, or from a formatter-linter-test baseline when it declares none.

When should I use Run Checks?

Run Checks fits situations like: the user asks to run checks; run the verification gate; run lint and tests; run the test suite.

How do I install Run Checks in Claude Code?

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

How do I install Run Checks in Codex?

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

Can I use Run Checks 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 run-checks -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/run-checks, .gemini/skills/run-checks, .github/skills/run-checks and .opencode/skills/run-checks in your project.

What does Run Checks need to run?

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

Does Run Checks 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 Run Checks 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 Run Checks use?

Run Checks 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 Run Checks use?

About 628 tokens (SKILL.md is roughly 2.5k 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 Run Checks?

Skills that share tags, products or a category with Run Checks: Bench Baton (nooga/let-go, 570 stars), Auto Harness (PacificStudio/openase, 268 stars), Conducty Ship (robertbarclayy/conducty, 176 stars) and UI Only (OutThisLife/brooklyn-skills, 199 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Run Checks?

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.