# Installation > Install the kill-ai-slop skill via npx or manual copy, and set up the Astro website dependencies for local development. - Repository: yetone/kill-ai-slop - GitHub: https://github.com/yetone/kill-ai-slop - Human docs: https://grok-wiki.com/public/docs/yetone-kill-ai-slop-c0d8c9670cbb - Complete Markdown: https://grok-wiki.com/public/docs/yetone-kill-ai-slop-c0d8c9670cbb/llms-full.txt ## Source Files - `README.md` - `skill/README.md` - `skill/SKILL.md` - `website/astro.config.mjs` --- --- title: "Installation" description: "Install the kill-ai-slop skill via npx or manual copy, and set up the Astro website dependencies for local development." --- Kill AI Slop ships two installable surfaces from the same repository: the `kill-ai-slop` Agent Skill under `skill/` (SKILL.md, references, and a dependency-free scanner), and the multilingual Astro field guide under `website/`. Skill install is a directory copy into an agent skills root; the website is a normal `npm install` under `website/`. ## What you install | Surface | Path | Requires packages | Purpose after install | |---|---|---|---| | Agent skill | `skill/` → host skills dir as `kill-ai-slop/` | No | Agent-driven scan → triage → report → fix | | Standalone scanner | `skill/scripts/scan.mjs` | No (pure Node) | Read-only grouped or JSON report | | Field guide site | `website/` | Yes (`npm install`) | Local dev at `http://localhost:4321`, static build to `dist/` | ``` website/ Astro site (multilingual, static, zero-JS-by-default) skill/ kill-ai-slop Agent Skill (SKILL.md + references + scanner) ``` The skill is self-contained: copy the whole directory; there is no package install and no build step for the skill itself. ## Prerequisites | Task | Runtime | |---|---| | Universal skill installer | `npx` (Node) | | Manual skill copy | `git` + shell (or any copy tool) | | Standalone scanner | Node only | | Website local run / build | Node + npm under `website/` | No model provider, API key, or hosted connector is required for install. Agent hosts (for example Claude Code) only need their own skills directory layout. ## Install the agent skill Choose one path. Destination folder name must be `kill-ai-slop`. ### Option A — Universal agent installer ```bash npx skills add yetone/kill-ai-slop ``` Follow the installer prompt for the target coding agent. ### Option B — Ask the agent to install Paste into the coding agent (Claude Code, Cursor, or another Agent Skills host): ``` Install the kill-ai-slop skill from https://github.com/yetone/kill-ai-slop/tree/main/skill Copy everything in that directory into a kill-ai-slop/ folder inside your agent's skills directory, then confirm it's registered. ``` The host should read `SKILL.md`, place the directory, and register the skill. You do not need to name individual files; the agent copies the directory as-is. ### Option C — Manual clone and copy ```bash git clone https://github.com/yetone/kill-ai-slop # Claude Code examples — swap the destination for other agents cp -r kill-ai-slop/skill ~/your-project/.claude/skills/kill-ai-slop # this project only cp -r kill-ai-slop/skill ~/.claude/skills/kill-ai-slop # every project ``` Copy the **entire** `skill` directory. Do not flatten or omit `references/` or `scripts/`. | Host example | Project-scoped skills | User-global skills | |---|---|---| | Claude Code | `/.claude/skills/kill-ai-slop` | `~/.claude/skills/kill-ai-slop` | Other agents use their own skills root; keep the folder name `kill-ai-slop`. ### Skill layout after install | Path | Role | |---|---| | `SKILL.md` | Skill name, description, workflow, guardrails | | `references/taxonomy.md` | 23 tells: definition, why it reads as slop, fix direction | | `references/detection.md` | Code patterns per tell and common false positives | | `references/fixes.md` | Before→after remediation patterns | | `scripts/scan.mjs` | Dependency-free scanner | Skill frontmatter identity: | Field | Value | |---|---| | `name` | `kill-ai-slop` | | Triggers (examples) | “kill AI slop”, “de-slop”, “remove the AI look”, “make this not look AI-generated” | ### Verify the skill 1. Confirm the host lists or loads `kill-ai-slop`. 2. Confirm the directory contains `SKILL.md`, `references/`, and `scripts/scan.mjs`. 3. Invoke with a plain request such as: > Kill the AI slop in this project. Also accepted: “de-slop this”, “remove the AI look”, “make this not look AI-generated”. Expected host behavior after install: **scan** → **triage** (slop vs intentional) → **report** grouped summary **before** edits → **fix** only approved groups. The standalone scanner never edits files; file changes come only from the agent workflow when you approve them. ## Install website dependencies (local field guide) Live site: [killaislop.com](https://killaislop.com). For a local copy: ```bash cd website npm install npm run dev # http://localhost:4321 npm run build # → dist/ (static, deploy anywhere) ``` | Command | Result | |---|---| | `npm install` | Install website dependencies in `website/` | | `npm run dev` | Dev server at `http://localhost:4321` | | `npm run build` | Static output under `website/dist/` | Astro config (`website/astro.config.mjs`): | Key | Value | Notes | |---|---|---| | `site` | `https://killaislop.com` | Canonical site URL | | `build.inlineStylesheets` | `'auto'` | Stylesheet inlining policy | | Integrations | none | Single static, dependency-light content site by design | Success signals: - Dev: field guide serves on `http://localhost:4321`. - Build: `dist/` is produced and is static (deploy-anywhere artifact). ## Run the scanner without the agent skill You can point the scanner at any web project path. It is pure Node, has no dependencies, and never edits files. From the repository root: ```bash node skill/scripts/scan.mjs path/to/project # grouped report node skill/scripts/scan.mjs path/to/project --json # machine-readable ``` From inside the installed skill directory (or `skill/`): ```bash node scripts/scan.mjs path/to/src # human-readable report node scripts/scan.mjs path/to/src --json # machine-readable ``` | Mode | Flag | Output use | |---|---|---| | Human-readable | (default) | Grouped `file:line` hits for review | | Machine-readable | `--json` | Triage / tooling | Treat hits as leads to confirm by reading code, not automatic verdicts. ## Constraints - Skill install = full directory copy as `kill-ai-slop/`; no skill packages, no skill build. - Scanner: read-only; no file writes. - Website: install and run only under `website/`; skill and site installs are independent. - No new dependencies are required to *use* the skill workflow on a target project (skill guardrail). ## Troubleshooting | Symptom | Check | |---|---| | Agent does not pick up the skill | Folder name is `kill-ai-slop`; path is the host’s skills directory (e.g. `.claude/skills/` or `~/.claude/skills/`); `SKILL.md` is present at the skill root. | | Incomplete skill (missing taxonomy / scanner) | Entire `skill/` tree was copied, including `references/` and `scripts/`. | | `npx skills add` fails | Node/`npx` available; network can reach the package/skills registry and `yetone/kill-ai-slop`. Fall back to Option B or C. | | `npm run dev` / `npm run build` fails | Commands run from `website/` after `npm install`. | | Scanner path wrong | From repo root use `skill/scripts/scan.mjs`; from skill root use `scripts/scan.mjs`. | ## Next Shortest path to a first scanner report and a local field-guide run. Prompts, host behavior, and how the skill uses references and the scanner after install. Point the dependency-free scanner at a path and read grouped vs JSON reports. Dev server, static build output, and how catalogue entries render on the index. Scan, triage, report, then propose or apply fixes without silent scanner edits. Invocation, path argument, `--json`, and the no-edit constraint.