Agent skill

Clippy CI

by lakeops-org in lakeops-org/queryflux

Run QueryFlux Clippy the same way CI does (-D warnings, workspace, exclude queryflux-bench) and fix failures before opening or updating a PR.

Apache-2.0Auto-check passedDevelopment

Install Clippy CI

skills CLI
$ npx skills add lakeops-org/queryflux --skill clippy-ci -a claude-code

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

GitHub CLI
$ gh skill install lakeops-org/queryflux clippy-ci --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/lakeops-org/queryflux.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/clippy-ci .claude/skills/clippy-ci && 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
clippy-ci
GitHub stars
144
Token cost
~458 tokens
SKILL.md length
210 words
Files
1
Skills in repo
1
Repo updated
First seen
Licence
Apache-2.0

At a glance

Run QueryFlux Clippy the same way CI does (-D warnings, workspace, exclude queryflux-bench) and fix failures before opening or updating a PR.

  • Works in 5 steps: cargo fmt --all → Run the Clippy command above. → Fix every error. Do not… → …
  • CI Clippy fails
  • SKILL.md covers Command, Before every Rust PR, Common failure:… and After a Clippy CI failure
  • Calls cargo and make

What it does

Clippy CI is an agent skill from lakeops-org/queryflux. Run QueryFlux Clippy the same way CI does (-D warnings, workspace, exclude queryflux-bench) and fix failures before opening or updating a PR. Use when writing or changing Rust, creating or pushing a PR, CI Clippy fails, or the user mentions clippy, lint, or make lint.

Its SKILL.md is about 460 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. It works with Rust. The repository describes itself as: Multi-engine and Agentic AI SQL query router in Rust for all data platforms and lakehouses—with routing, queuing, guardrails, tracking, sqlglot dialect translation and more. The licence is Apache-2.0.

When your agent uses it

  • CI Clippy fails
  • The user mentions clippy

Example prompts

  • “/clippy-ci”

Workflow steps

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

  1. cargo fmt --all
  2. Run the Clippy command above.
  3. Fix every error. Do not #[allow(clippy::…)] unless the lint is a false positive and surrounding code already allows it.
  4. Re-run Clippy until exit 0.
  5. Include the fixes in the commit. Do not push with a red Clippy job.

What it can do on your machine

Read from SKILL.md and the folder at commit 06be044. 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

    Shell commands in SKILL.md call:

    • cargo
    • make

    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

Clippy CI loads about 458 tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 210 words of instructions outside code blocks.

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

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 lakeops-org/queryflux at commit 06be044, republished under its Apache-2.0 licence (© lakeops-org). 210 words, ~458 tokens.

Download SKILL.mdSave it as .claude/skills/clippy-ci/SKILL.md (or your agent's skills folder).
name
clippy-ci
description
Run QueryFlux Clippy the same way CI does (-D warnings, workspace, exclude queryflux-bench) and fix failures before opening or updating a PR. Use when writing or changing Rust, creating or pushing a PR, CI Clippy fails, or the user mentions clippy, lint, or make lint.

Clippy (match CI)

CI job Clippy in .github/workflows/ci.yml treats warnings as errors. Do not push Rust changes until this command exits 0.

Command

bash
CARGO_TARGET_DIR=target cargo clippy --workspace --all-targets --all-features --exclude queryflux-bench -- -D warnings
  • CARGO_TARGET_DIR=target avoids sandbox/DuckDB cache breakage (same as tests).
  • --all-targets includes tests and examples. Tests in the middle of a file fail clippy::items_after_test_module.
  • --exclude queryflux-bench matches CI (bench is built in benchmark.yml).
  • Local shortcut: make clippy / make lint (must use the same flags as CI).

Also run cargo fmt --all and cargo fmt --all -- --check before push (see .cursor/rules/pr-formatting.mdc).

Before every Rust PR

  1. cargo fmt --all
  2. Run the Clippy command above.
  3. Fix every error. Do not #[allow(clippy::…)] unless the lint is a false positive and surrounding code already allows it.
  4. Re-run Clippy until exit 0.
  5. Include the fixes in the commit. Do not push with a red Clippy job.

Common failure: items_after_test_module

#[cfg(test)] mod tests { … } must be the last item in the file. If you add helpers or impls after the test module, move the test module to the end.

After a Clippy CI failure

  1. Open the failed job log and copy the error: lines (clippy::…).
  2. Fix on the PR branch, fmt, re-run Clippy locally, push.
  3. Do not re-run the workflow hoping it is flaky; -D warnings failures are real.

© lakeops-org, Apache-2.0. 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 .cursor/skills/clippy-ci of lakeops-org/queryflux.

Open the folder on GitHubat commit 06be044

Compare with similar skills

Clippy CI 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.

Clippy CI compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Clippy CI this skilllakeops-org/queryflux144—~458Automated safety check: PassApache-2.0
Rust Best Practicesfarm-fe/farm5.6k3 repos~1.1kAutomated safety check: PassMIT
Doc Commentsbiomejs/biome26k—~3kAutomated safety check: PassApache-2.0
Rust Hygiene Audittsz-org/tsz577—~1.5kAutomated safety check: PassApache-2.0
Releasexin2017338/lynx-proxy502—~1.1kAutomated safety check: PassMIT
Flowmark Markdown Formatterjlevy/repren374—~631Automated safety check: PassMIT

Similar skills

  • Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook.

    5.6k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Doc Comments

    biomejs/biome

    Official

    A skill your agent uses whenever writing or editing Rust //, ///, or //!

    26k GitHub stars~3k tokensUpdated today
    DevelopmentAuto-check passed
  • Run a deep DRY + code-hygiene audit of the Rust workspace and turn the findings into verified, deduplicated, hierarchical GitHub tech-debt issues.

    577 GitHub stars~1.5k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Release

    xin2017338/lynx-proxy

    Publish a new release version of Lynx Proxy. An agent skill from xin2017338/lynx-proxy.

    502 GitHub stars~1.1k tokensUpdated 25 days ago
    DevelopmentAuto-check passed
  • Formats Markdown with the Flowmark auto-formatter for typographic cleanup and semantic line breaks, and helps adopt it across a repository.

    374 GitHub stars~631 tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Rsigma

    timescale/rsigma

    Use the rsigma CLI and MCP server: engine eval, engine daemon, rule lint, rule draft, rule tune, rule backtest, backend convert, mcp serve.

    165 GitHub stars~1.2k tokensUpdated yesterday
    DevelopmentAuto-check passed

Works with

Questions about Clippy CI

What does Clippy CI do?

Run QueryFlux Clippy the same way CI does (-D warnings, workspace, exclude queryflux-bench) and fix failures before opening or updating a PR. Clippy CI is an agent skill from lakeops-org/queryflux. Run QueryFlux Clippy the same way CI does (-D warnings, workspace, exclude queryflux-bench) and fix failures before opening or updating a PR.

When should I use Clippy CI?

Clippy CI fits situations like: CI Clippy fails; the user mentions clippy.

How do I install Clippy CI in Claude Code?

Run `npx skills add lakeops-org/queryflux --skill clippy-ci -a claude-code`. Or copy the skill folder (.cursor/skills/clippy-ci in lakeops-org/queryflux) into .claude/skills/clippy-ci in your project. Claude Code loads it when a task matches its description.

How do I install Clippy CI in Codex?

Run `npx skills add lakeops-org/queryflux --skill clippy-ci -a codex`. Or copy the skill folder (.cursor/skills/clippy-ci in lakeops-org/queryflux) into .agents/skills/clippy-ci in your project. Codex loads it when a task matches its description.

Can I use Clippy CI 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 lakeops-org/queryflux --skill clippy-ci -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/clippy-ci, .gemini/skills/clippy-ci, .github/skills/clippy-ci and .opencode/skills/clippy-ci in your project.

What does Clippy CI need to run?

Going by SKILL.md and its folder, Clippy CI needs the command-line tools its instructions call (cargo and make).

Does Clippy CI 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 Clippy CI 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 Clippy CI use?

Clippy CI is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Clippy CI use?

About 458 tokens (SKILL.md is roughly 1.8k 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 Clippy CI?

Skills that share tags, products or a category with Clippy CI: Rust Best Practices (farm-fe/farm, 5.6k stars), Doc Comments (biomejs/biome, 26k stars), Rust Hygiene Audit (tsz-org/tsz, 577 stars) and Release (xin2017338/lynx-proxy, 502 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Clippy CI?

lakeops-org (a GitHub organization) maintains it in lakeops-org/queryflux, which has 144 GitHub stars. The repository was last updated on October 9, 2026.

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