Kimi Code is an installer target
Kimi Code scans four tiers for skills, and .agents/skills/ appears in two of them:
the project tier and the user tier. That is the folder Antigravity, Copilot, Codex,
and OpenCode already read, so the whole door is one installer row, and the AGENTS.md
pointer covers the rest. Nothing new is written to your project.
It takes no global folder of its own, and that is deliberate. Kimi Code's
$KIMI_CODE_HOME/skills/ moves with a variable the installer cannot see, so writing
it would be guessing, and the shared folder is the same at both scopes regardless.
Contributed by @fajarhide.
The Kimi Code plugin door
Unlike Copilot, Kimi Code accepts a repo-installable manifest, so this door has two
halves. The repo now ships .kimi-plugin/plugin.json, which registers the six skills
and points systemPromptPath at rules/antislop.md, the same pointer the Antigravity
and Cursor doors load. Install it from a Kimi Code session:
/plugins install https://github.com/miqdadbadjuber/anti-slop
No marketplace file is added, because the command takes the repository URL directly.
Contributed by @fajarhide.
What this release could not check
Neither half has been run in a live Kimi Code session. No maintainer had an install to
test against, so both rest on the vendor's own documentation rather than on a session
that proves them. The live check moves to v3.2.13, which is a maintenance round.
The guide now answers "how do I know an update exists"
The Update section of GUIDE.md went straight into per-route commands and never said how
to learn that a new version is out. It now names the two places that always carry the
current version, and points out that npx antislop-ai --version is itself the check on
the installer route. The closing list of plugin doors also omitted Kimi Code, and now
names it.
A motion comparison in the README
The four builds from See the difference, animated, sits above the FAQ. It ships as an
animated GIF. It was converted to an animated WebP for the smaller file and converted
back: a GIF is dithered to 256 colors, and a lossy WebP re-encodes that per-pixel dither
as blocking, so the smaller file looked worse at full size.
The contributor block stays at the bottom of the README, between the star history chart
and the license. Contributed by @fajarhide.
Full detail is in the ROADMAP.