# Slopscriber

> Update repository documentation and agent guidance against current sources when fixing drift or cleaning up docs.

- Skill: `uinaf/slopscriber` (Agent Skill, multi-file: 21 files)
- Install (CLI): `npx skillmds@latest add uinaf/slopscriber`
- Raw SKILL.md: https://api.skillmd.com/api/skills/uinaf/slopscriber/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: uinaf (https://skillmd.com/u/uinaf)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/uinaf/slopscriber

---


# Slopscriber

Keep documentation accurate, findable, and worth reading. Edit the affected
surfaces; a local change does not require a repository-wide audit.

Verify claims against their owning code, configuration, or cited source.
Preserve current commands, invariants, boundaries, and recovery paths; remove
stale facts, repetition, and history that belongs elsewhere. Keep one canonical
home per contract and link to it with a task-shaped label.

## Negative-state rule

Remove absent or retired capabilities unless the limitation changes a current
action. Keep actionable limits precise and pair them with the supported path.

## Choose the reference

- Agent guidance or retrieval structure: [agent-first.md](references/agent-first.md).
- README, contributor, security, or deep-doc placement: [documentation.md](references/documentation.md).
- Private, cross-repo, or machine-local evidence; saving a durable rule:
  [source-boundaries.md](references/source-boundaries.md).
- Long-lived feature contracts or decisions: [specifications.md](references/specifications.md).
- Writing defaults when the owner has no stronger convention:
  [style.md](references/style.md).

Do not invent contributor/security policy, create a second backlog, implement
missing readiness infrastructure, or turn docs cleanup into runtime
verification. When the request includes those tasks, keep their ownership
distinct and continue separately authorized work.

Check changed links, commands, and moved references against current sources.
Use the repository's doc checks; running a documented command is a separate
action whose scope and side effects still need authorization. Report what
changed, what was verified, and any remaining gap. Do not create a report file
unless requested or required by the repository.