unslop-code

Read this first, because the most common misunderstanding sinks the whole thing.

This skill does not write good code for you, and it has no house style. It does two narrow things. It removes the specific surface cues that make code read as machine-generated, and it points you at the deeper tells (the ones that ship bugs) that no scanner can catch. Whether the code is correct, well-factored, and right for the problem is still your call. A guardrail is not an engineer.

The trap to avoid (this is the whole point)

The surface tells are the cheap part. You can strip every emoji, delete every // rest of your code stub, and fix every bare except, and still ship a file that is tutorial-shaped, calls a made-up API, over-engineers a simple task, and ignores how the rest of the repo works. Those are the loudest tells in the data, and a clean lint hides them. The verified ranking is blunt about it: boilerplate (18.6%), hallucinated APIs (11.2%), and over-engineering (7.8%) tower over the cosmetic stuff (emoji 3.9%, verbose names 0.4%). So removing surface tells is the easy 40% of the job, not the job. Do not mistake a clean scan for clean code.