Chdb Datastore
vemetric/vemetric
A skill your agent uses when the user has tabular data (pandas DataFrame, parquet, csv, Arrow, json) and wants to filter, group, aggregate, join, or speed up slow pandas.
Strip agent-generated noise from a diff — comments that restate the code, private helpers in test files, near-duplicate tests, tests with no assertions, unrequested indexes and validation, defensive…
Install Slop Check
$ npx skills add polarsource/polar --skill slop-check -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install polarsource/polar slop-check --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/polarsource/polar.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/slop-check .claude/skills/slop-check && rm -rf skills-srcUse ~/.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/
Install the "slop-check" agent skill from https://github.com/polarsource/polar/tree/main/.agents/skills/slop-check into .claude/skills/slop-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slop-check", 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 install https://github.com/polarsource/polar/tree/main/.agents/skills/slop-checkType 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.
$ npx skills add polarsource/polar --skill slop-check -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install polarsource/polar slop-check --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/polarsource/polar.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/slop-check .agents/skills/slop-check && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "slop-check" agent skill from https://github.com/polarsource/polar/tree/main/.agents/skills/slop-check into .agents/skills/slop-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slop-check", 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.
$ npx skills add polarsource/polar --skill slop-check -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install polarsource/polar slop-check --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/polarsource/polar.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/slop-check .cursor/skills/slop-check && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "slop-check" agent skill from https://github.com/polarsource/polar/tree/main/.agents/skills/slop-check into .cursor/skills/slop-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slop-check", 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 https://github.com/polarsource/polar.git --path .agents/skills/slop-check--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add polarsource/polar --skill slop-check -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install polarsource/polar slop-check --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/polarsource/polar.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/slop-check .gemini/skills/slop-check && rm -rf skills-srcUse ~/.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/
Install the "slop-check" agent skill from https://github.com/polarsource/polar/tree/main/.agents/skills/slop-check into .gemini/skills/slop-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slop-check", 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.
$ gh skill install polarsource/polar slop-checkInstalls 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).
$ npx skills add polarsource/polar --skill slop-check -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/polarsource/polar.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/slop-check .github/skills/slop-check && rm -rf skills-srcUse ~/.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/
Install the "slop-check" agent skill from https://github.com/polarsource/polar/tree/main/.agents/skills/slop-check into .github/skills/slop-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slop-check", 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.
$ npx skills add polarsource/polar --skill slop-check -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install polarsource/polar slop-check --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/polarsource/polar.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/slop-check .opencode/skills/slop-check && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "slop-check" agent skill from https://github.com/polarsource/polar/tree/main/.agents/skills/slop-check into .opencode/skills/slop-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slop-check", 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
slop-check- GitHub stars
- 10k
- Token cost
- ~971 tokens
- SKILL.md length
- 507 words
- Files
- 1
- Skills in repo
- 18
- Repo updated
- First seen
- Licence
- MIT
At a glance
Strip agent-generated noise from a diff — comments that restate the code, private helpers in test files, near-duplicate tests, tests with no assertions, unrequested indexes and validation, defensive…
- Asks to tighten a diff
- SKILL.md covers Scope, Checks, Do not flag and Output
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Cut verbose comments
What it does
Slop Check is an agent skill from polarsource/polar. Strip agent-generated noise from a diff — comments that restate the code, private helpers in test files, near-duplicate tests, tests with no assertions, unrequested indexes and validation, defensive guards that duplicate an existing check. Use before opening a PR on agent-written code, or when the user asks to tighten a diff, remove slop, or cut verbose comments.
Its SKILL.md is about 970 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 Data & Analytics, covering DataFrames. The repository describes itself as: Polar — A billing platform for the intelligence era. The licence is MIT.
When your agent uses it
- Asks to tighten a diff
- Cut verbose comments
Example prompts
- “/slop-check”
What it can do on your machine
Read from SKILL.md and the folder at commit e4fc909. 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
Slop Check loads about 971 tokens when it runs. Until then it costs about 94 tokens; SKILL.md has 507 words of instructions outside code blocks.
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 polarsource/polar at commit e4fc909, republished under its MIT licence (© polarsource). 507 words, ~971 tokens.
Download SKILL.mdSave it as
.claude/skills/slop-check/SKILL.md (or your agent's skills folder).- name
- slop-check
- description
- Strip agent-generated noise from a diff — comments that restate the code, private helpers in test files, near-duplicate tests, tests with no assertions, unrequested indexes and validation, defensive guards that duplicate an existing check. Use before opening a PR on agent-written code, or when the user asks to tighten a diff, remove slop, or cut verbose comments.
- license
- MIT
- metadata.author
- polar
- metadata.version
- 1.0.0
Slop Check (Polar)
The handle is the diff. The evidence is lines that should not exist.
Not a bug hunt, not a style guide. One job: delete code that is recognisably agent-written and that a Polar reviewer would ask you to remove. Run it before the other lenses, because everything it cuts is diff nobody else has to read.
Calibration, from real reviews:
"Verbosy LLM comment" · "Meaningless slop comment imho, let's drop" · "That's typical of Claude, it puts those private helper functions everywhere!" · "Lol, LLM was zealous here" · "This feels like a new thing that Claude always wants to throw in" · "Overengineering IMO, that case would be at most rare"
Scope
Any diff. It is cheap, there is no reason to skip it.
Owned elsewhere: reinvented helpers → reuse-check; written conventions → conventions-check.
Checks
Propose a deletion, not a rewrite, wherever a deletion will do.
1. Comments that restate the code. The repo rule is: no comments unless necessary, the code should be self-explanatory. Comment the non-obvious why, never the what. Endpoint docstrings are not slop — they render into OpenAPI — but strip implementation detail out of them.
2. Private helpers in test files. The strongest agent tell here. _make_auth_subject()
or _create_order(...) at the top of a test module instead of the fixtures. If a helper is
genuinely needed it is a pytest fixture. Also flag save_fixture called twice on one object,
and re-setting data a fixture already provides.
3. Near-duplicate tests. Agents write one test per input permutation. Flag any group in the diff that differs only by an input value and asserts the same branch, and say which to keep.
4. Tests that assert nothing. A test body with no assert / expect always passes.
Grep every new test.
5. Unrequested extras. An index nobody asked for, validation the type already enforces, a
config flag with one caller, an abstraction with one implementation, a try/except for
something the framework handles, an overload that changes no behaviour. Ask of each: what
breaks if this is deleted? If nothing, delete it.
Show full SKILL.md (170 more words)Show less
6. Guards that duplicate an existing check. Defensive code repeating an upstream check, or
guarding a case the data model makes impossible. Also a superfluous session.flush() —
flushing is only for data that must be visible before the request ends.
7. Dead on arrival. Added in the diff but nothing calls it: unused argument, unused
import, method with no caller, getattr where attribute access works, a wrapper that only
forwards.
Do not flag
Two ways this check goes wrong, both worse than the slop itself.
- Domain comments. A comment explaining why a lock is released only on the webhook path,
or why a status maps to Stripe's
lost, is exactly what the team wants. The test is whether the sentence carries information the code cannot. - Real coverage. Only flag a test that duplicates another test in this diff, or that asserts nothing. Cutting coverage to hit a "fewer tests" target is a worse outcome.
Output
## Slop
### 🟠 Delete
- `file:line-line` — <why>
### 🟡 Question
- `file:line` — <question, e.g. "index added but the task did not ask for one. What query needs it?">
### Verdict
✅ Clean | ❌ n lines to removeGroup by file and give line ranges, so the author can act without re-reading the diff.
© polarsource, 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 .agents/skills/slop-check of polarsource/polar.
Open the folder on GitHubat commit e4fc909
Compare with similar skills
Slop Check 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Slop Check this skillpolarsource/polar | 10k | — | ~971 | Automated safety check: Pass | MIT | |
| Chdb Datastorevemetric/vemetric | 394 | 2 repos | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| CSV Data Summarizercoffeefuelbump/csv-data-summarizer-claude-skill | 468 | 2 repos | ~1.4k | Automated safety check: Pass | None | |
| Paper FiguresEvoScientist/EvoSkills | 475 | 1 repos | ~4.4k | Automated safety check: Pass | Apache-2.0 | |
| Python Executorcortega26/chile-hub | 113 | 2 repos | ~1.5k | Automated safety check: Pass | MIT | |
| DataframelyQuantco/dataframely | 619 | — | ~2.4k | Automated safety check: Pass | BSD-3-Clause |
Similar skills
CSV Data Summarizer
coffeefuelbump/csv-data-summarizer-claude-skill
Analyzes CSV files, generates summary stats, and plots quick visualizations using Python and pandas.
Paper Figures
EvoScientist/EvoSkills
A skill your agent uses to produce standalone, publication-ready PNG graphics and reproducible matplotlib scripts from tabular data (CSVs or DataFrames).
Python Executor
cortega26/chile-hub
Execute Python code in a safe sandboxed environment via [inference.sh](https://inference.sh).
Dataframely
Quantco/dataframely
Best practices for polars data processing with dataframely. An agent skill from Quantco/dataframely.
Retentioneering Product Analytics
retentioneering/retentioneering-tools
Analyze event logs, clickstreams, user paths, product funnels, retention, behavioral segments, transition graphs, step matrices, sequence patterns, and customer journeys using Retentioneering.
More from polarsource/polar
All 18 skills in this repoPolar Python SDK
polarsource/polar
Integrate Polar billing in server-side Python applications using the versioned Polar and PolarAsync clients.
Polar Typescript SDK
polarsource/polar
Integrate Polar billing in server-side TypeScript applications using the versioned createPolar and createPolarCore clients.
Adr Check
polarsource/polar
Check a code change against the repo's Accepted Architecture Decision Records (ADRs) in handbook/engineering/decisions/ and report violations with citations.
API Surface Review
polarsource/polar
Review changes to Polar's API contract — Pydantic schemas, FastAPI endpoints, OpenAPI output and the generated SDKs.
Billing Review
polarsource/polar
Review a diff that touches Polar's billing domain — subscriptions, cycles and crons, orders, billing entries, meters and usage, discounts, checkout, payments and dunning, refunds, disputes, payouts…
Interview Task
polarsource/polar
Prepare an interview task for a candidate, as part of our hiring process.
Related
Categories
Questions about Slop Check
What does Slop Check do?
Strip agent-generated noise from a diff — comments that restate the code, private helpers in test files, near-duplicate tests, tests with no assertions, unrequested indexes and validation, defensive…. Slop Check is an agent skill from polarsource/polar. Strip agent-generated noise from a diff — comments that restate the code, private helpers in test files, near-duplicate tests, tests with no assertions, unrequested indexes and validation, defensive guards that duplicate an existing check.
When should I use Slop Check?
Slop Check fits situations like: asks to tighten a diff; cut verbose comments.
How do I install Slop Check in Claude Code?
Run `npx skills add polarsource/polar --skill slop-check -a claude-code`. Or copy the skill folder (.agents/skills/slop-check in polarsource/polar) into .claude/skills/slop-check in your project. Claude Code loads it when a task matches its description.
How do I install Slop Check in Codex?
Run `npx skills add polarsource/polar --skill slop-check -a codex`. Or copy the skill folder (.agents/skills/slop-check in polarsource/polar) into .agents/skills/slop-check in your project. Codex loads it when a task matches its description.
Can I use Slop Check 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 polarsource/polar --skill slop-check -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/slop-check, .gemini/skills/slop-check, .github/skills/slop-check and .opencode/skills/slop-check in your project.
What does Slop Check need to run?
SKILL.md names no scripts, command-line tools or credentials: Slop Check is instructions for the agent only.
Does Slop Check 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 Slop Check 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 Slop Check use?
Slop Check is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Slop Check use?
About 971 tokens (SKILL.md is roughly 3.9k 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 Slop Check?
Skills that share tags, products or a category with Slop Check: Chdb Datastore (vemetric/vemetric, 394 stars), CSV Data Summarizer (coffeefuelbump/csv-data-summarizer-claude-skill, 468 stars), Paper Figures (EvoScientist/EvoSkills, 475 stars) and Python Executor (cortega26/chile-hub, 113 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Slop Check?
polarsource (a GitHub organization) maintains it in polarsource/polar, which has 10,340 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 7, 2026.
Source: polarsource/polar on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.