remove-repository skillA
remove-repository is agent-read markdown (skill) from raffertyuy/repo-of-repos: Remove a repo or local folder from repos/, updating repos.yaml, repos.md, and .gitignore.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified before it reaches your agent: the main file against the SHA-256 recorded here, the others against the git hashes of its source commit. The deterministic audit below grades the latest version, and the same checks always give the same file the same grade.
What the file says
# Remove Repository Remove a single repository or local source folder from the workspace. This is the inverse of `/add-repository`. The user will provide a repo name. For example: - `/remove-repository frontend` — remove the `frontend` entry - `/remove-repository backend-api` — remove the `backend-api` entry ## Behavior 1. **Validate** the entry exists in `repos/repos.yaml` by name - If not found, report the error and list available entries so the user can pick the right one - If found, proceed 2. **Show what will happen** — before taking any action, display: - The entry being removed (name, type, URL if git) - Whether the directory exists on disk - Ask the user: **delete the directory from disk too, or just remove the config entry?** 3. **Remove from `repos/repos.yaml`** — delete the entry from the `repos:` list - If this was the last entry, leave `repos: []` 4. **Remove from `repos/repos.md`** — delete the `## <name>` section and all its content up to the next `## ` heading or end of file - If no entries remain, restore the placeholder: `<!-- No repositories found. Clone repos into repos/ and run /pull-all-repos to populate this file. -->` …
Read the whole file at its exact version.
How to install
mdr add raffertyuy/repo-of-repos/remove-repository@git:20260723.1db5b32mdr add raffertyuy/repo-of-repos/remove-repository@sha256:594bac9f271d4dadPin to a label to follow the author's releases, or to a sha256 for exact bytes. Either way the resolved hash is written to mdr.lock, and mdr install fetches those bytes again and checks them, so it installs them exactly or fails.
[](https://markdownregistry.com/a/art_wwp6jxp6aowlvhrb)
2 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2217 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
raffertyuy/repo-of-repos · 12 stars · license MIT · pushed 2026-09-25 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_wwp6jxp6aowlvhrb GET https://markdownregistry.com/api/v1/resolve?ref=raffertyuy/repo-of-repos/remove-repository GET https://markdownregistry.com/api/v1/blob/594bac9f271d4dad64210ba70eeb28fb6bfe531fcae598ff0aca847dbb6b9ef9
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
More from raffertyuy/repo-of-repos
Every file in raffertyuy/repo-of-repos