docs: trim repeated boilerplate in git, gitea, and bin skills

Finding 13: five blocks of near-identical wording were repeated across
skills within a plugin — the gitea "resolve owner and repo" step (5
skills), the 404-masks-403 note (6 files), the manual pagination
explanation (8 files), the git plugin's main/master force-push refusal
(7 files, some with multiple internal restatements), and the bin
skills' domain-glossary/ADR paragraph (5 skills). Tightened each
instance in place — same meaning, fewer words — rather than extracting
to a shared file, which ADR-0014's one-file-per-skill install
constraint rules out. Left the three git skills' structured-result
JSON shapes alone (coupled to the separate, out-of-scope git-orchestrate
merge candidate, finding 19).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01YR2CjVumUbEGWcMikcoXBD

plugins/gitea/.apm/skills/gitea-branches/SKILL.md

@@ -23,19 +23,19 @@ allowed-tools: Bash mcp__gitea__list_branches mcp__gitea__create_branch mcp__git
 
 ## Gotchas
 
-- **404 often means 403.** Gitea masks permission errors as not-found; on an unexpected one, check token scope before reporting a branch or commit missing.
-- **Nothing auto-paginates.** `list_branches` and `list_commits` return one page; iterate `page` until the returned count is below `per_page`.
+- **404 can mean 403.** Gitea masks permission errors as not-found — check token scope before reporting a branch or commit missing.
+- **Nothing auto-paginates.** `list_branches`/`list_commits` return one page — iterate `page` until the count is below `per_page`.
 - **`delete_branch` has no force-push guard.** Treat deleting a protected branch as a hard refusal unless the user explicitly confirms it in the conversation. Check `protected` from `list_branches` first — a protected branch need not be named `main`.
 
 ## Step 1 — Resolve owner and repo
 
-Before any tool call, extract `owner` and `repo` from the git remote:
+Extract `owner` and `repo` from the git remote before any tool call — `get_me` and `list_my_repos` are blocked under this skill's token scope, so the remote is the only source:
 
 ```bash
 rtk git remote get-url origin
 ```
 
-`get_me` and `list_my_repos` are blocked under the token scope this skill assumes, so the remote is the only source. If origin is not set or the URL is not a Gitea URL, stop and report: "No Gitea remote found — set origin to your Gitea instance URL."
+No origin, or not a Gitea URL: stop and report "No Gitea remote found — set origin to your Gitea instance URL."
 
 ## Step 2 — Dispatch
 

plugins/gitea/.apm/skills/gitea-branches/references/branches.md

@@ -29,8 +29,7 @@ list_branches owner: <owner> repo: <repo>
 **Response:** one object per branch: `name`, `protected` (bool), `commit_sha` (present when the
 underlying commit data is available).
 
-Paginate if you need the full list (see Gotchas in SKILL.md) — iterate `page` until the returned
-count is less than `per_page`.
+Paginate for the full list (see Gotchas) — iterate `page` until the count is less than `per_page`.
 
 ## `create_branch`