miqdadbadjuber/anti-slop v3.2.15

v3.2.15: Amp as an installer target

on GitHub

Amp is an installer target

• Amp reads .agents/skills/ in a project, the folder Antigravity, Copilot, and Kimi Code already share, so picking it with any of them installs antislop once. Under your home directory it reads ~/.config/agents/skills/, a folder of its own, so a global install is the only one that writes somewhere new.
• It also loads .claude/skills/, so installing Amp beside Claude Code puts the same skill names in two folders it reads, and the installer names that collision.
• The AGENTS.md block carries the pointer: Amp includes that file from the working directory up to your home directory.
• Eleven agents now resolve to eight project folders.

Amp gets no plugin door

• Amp does not scan a bundled skills/ folder, so a plugin has to register each skill by a call when it loads.
• Single-file plugins cannot register skills at all, and amp plugins add installs single files only.
• A directory plugin is the only kind that can register a skill, and it has no one-command install from a repository URL.
• A skill arriving through a plugin is renamed <plugin>:<skill>, which does not match the bare names the core and the pointer block already use.

So Amp takes Copilot's shape: the installer is the whole door, and there is nothing extra to install.

Two corrections from the last release

• v3.2.14 said Cline was the only agent here that lets a global skill outrank a project one. Amp documents the same order, so the README and the guide now name both and stop speaking for the agents whose documentation does not settle it.
• The guide counted the agents that read more than one folder as two. It is five: Codex, Hermes, OpenCode, Cline, and Amp.

Updating

Same route as before: run npx antislop-ai and choose Overwrite them when it finds the existing folders. It prints the version on disk next to the one it carries. Every other route is listed in the README's Update table and walked through in GUIDE.md.