chore: ask before changing repository skills

[rasdani]

Require agents to suggest specific repository skill changes, explain the benefit, and wait for user approval before editing. Existing explicit requests or approvals remain sufficient; ordinary code, workflow, documentation, and PR requests do not authorize skill changes. Reading and following skills remains allowed.

Changes only AGENTS.md, using the same approval guidance as PrimeIntellect-ai/prime-envs#814. Remove skills from the generic documentation-change exception so their edits consistently require approval.

Validation: git diff --check, Markdown lint, and pre-push hooks (Ruff check/format and ty) passed.

Note

Require user approval before changing repository skills in AGENTS.md

Adds policy guidance to AGENTS.md requiring agents to suggest a specific skill update, explain its value, and get user approval before creating, modifying, renaming, or deleting skills or their supporting files and symlinks. Explicitly requested or previously approved changes may proceed without another approval; ordinary code or PR requests do not implicitly authorize skill changes.

^{Macroscope summarized b3de58f.}

---

Note

Low Risk
Documentation-only change to agent behavior guidelines; no runtime or application code affected.

Overview
Adds Skills policy to AGENTS.md: agents must propose a concrete skill change, explain the benefit, and wait for user approval before creating, editing, renaming, or deleting anything under skills/ (including supporting files and symlinks).

Explicit user requests or prior approvals still count; routine asks (code fixes, docs, workflows, opening PRs) do not grant permission to touch skills. Reading and following bundled skills stays unchanged.

^{Reviewed by Cursor Bugbot for commit b3de58f. Bugbot is set up for automated code reviews on this repo. Configure here.}

[mikasenghaas]

why this change? this has prob prevented excessive changes before

[rasdani]

@codex revert this line

[rasdani]

@codex revert the line mika flagged