update-repo-meta SKILL.md skillA
update-repo-meta from urmzd/dotfiles is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add urmzd/dotfiles/update-repo-meta@git:20260530.d3be4ddPins git:20260530.d3be4dd in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- urmzd/dotfiles
- Path
dot_agents/skills/update-repo-meta/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260530.d3be4dd, committed May 30, 2026
- First version recorded
- Apr 8, 2026
- Size
- 2,533 bytes
- Repository stars
- 5
- License
- Apache-2.0
Update GitHub repository metadata via the gh CLI: add or remove repo topics, set the description, set the homepage URL, and change visibility (public/private). Reads current state and shows before/after. Use when updating repo settings, retagging topics, fixing a repo description or homepage, or making a repo public or private. Do NOT use to edit local repo files, branch protection, or release metadata; this only touches repo-level settings exposed by gh repo edit.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Update Repo Meta Update GitHub repository metadata. ## Steps 1. **Read current state**: `gh repo view --json name,description,homepageUrl,repositoryTopics,visibility` 2. **Determine changes**: Based on the user's argument or conversation context, figure out what to update. Common operations: - **Topics**: `gh repo edit --add-topic <topic>` or `--remove-topic <topic>` - **Description**: `gh repo edit --description "<text>"` - **Homepage**: `gh repo edit --homepage "<url>"` - **Visibility**: `gh repo edit --visibility public|private` 3. **Apply changes**: Run the appropriate `gh repo edit` commands. 4. **Verify**: Run `gh repo view --json name,description,homepageUrl,repositoryTopics,visibility` again and show the updated state. ## Rules - Show the before/after so the user can confirm the changes. - If no specific instructions are given, show the current metadata and ask what to change. - Topics should be lowercase, hyphenated (e.g., `cli-tool`, `go`, `mcp-server`). ## Gotchas - **Topic cap is 20.** GitHub caps a repo at 20 topics; `gh repo edit --add-topic` past that limit fails. Check the current count before adding in bulk. …
Read the whole file at its exact version.
How to install
mdr add urmzd/dotfiles/update-repo-meta@sha256:09c911aa382012c0The line at the top of this page pins the label git:20260530.d3be4dd, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_xk2pmiohwfji4qua)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Apr 8, 2026 and May 30, 2026, about one every 51 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260530.d3be4dd latest | 2026-05-30 | d3be4dd | 2,533 B | A | view · diff |
| git:20260408.a08708c | 2026-04-08 | a08708c | 1,340 B | A | view |
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 (2533 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
urmzd/dotfiles · 5 stars · license Apache-2.0 · pushed 2026-11-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_xk2pmiohwfji4qua GET https://markdownregistry.com/api/v1/resolve?ref=urmzd/dotfiles/update-repo-meta GET https://markdownregistry.com/api/v1/blob/09c911aa382012c0362a17f24f072cf52771eba9b7877974d595b4ef61feb57e
Your AI assistant 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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.