configure-labels SKILL.md skillA

configure-labels from tomzx/agents is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add tomzx/agents/configure-labels@git:20261007.b35fc4b

Pins git:20261007.b35fc4b in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: tomzx/agents
Path: skills/configure-labels/SKILL.md
Versions recorded: 5
Latest version: git:20261007.b35fc4b, committed Oct 7, 2026
First version recorded: Jun 4, 2026
Size: 9,407 bytes
Repository stars: 12
License: MIT

Configure the standard label set in a GitHub repository to match the SDLC labeling conventions used by triage and issue management skills.

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

# Configure Repository Labels

Sets up the standard label taxonomy in a GitHub repository so that downstream skills (triage-issues, label-issue, prioritize-issues) can classify and manage issues consistently.
Creates missing labels, updates descriptions and colors for existing labels that do not match the convention, and removes conflicts with GitHub defaults.
Idempotent: safe to re-run on a repository that already has some or all labels configured.

## Prerequisites

- Apply the shared SDLC conventions in `skills/sdlc/references/shared.md`.
- If no argument is provided, operate on `$REPO`.
- `gh` CLI authenticated with write access to the target repository
- Repository in `owner/repo` format (`$1`), or omit to use the repository in the current working directory

## Workflow

```
Determine target repository ($1 or CWD)
         |
         v
Fetch existing labels via gh label list
         |
         v
Compute desired label set (standard + project-specific)
         |
         v
For each desired label:
   Exists?
    /       \
  Yes         No
   |           |
   v           v
 Update if     Create label
 name/color/   via gh label
 desc differ
   |           |
   +-----+-----+
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add tomzx/agents/configure-labels@sha256:7af42638ec0917fd

The line at the top of this page pins the label git:20261007.b35fc4b, 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.

Badge

[![mdr](https://markdownregistry.com/badge/art_ontet2zbplypar6r.svg)](https://markdownregistry.com/a/art_ontet2zbplypar6r)

2 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 5 versions of this file, between Jun 4, 2026 and Oct 7, 2026, about one every 31 days.

version	committed	commit	size	audit
git:20261007.b35fc4b latest	2026-10-07	b35fc4b	9,407 B	A	view · diff
git:20260627.d2c36c7	2026-06-27	d2c36c7	9,416 B	A	view · diff
git:20260627.ea658bc	2026-06-27	ea658bc	9,366 B	A	view · diff
git:20260622.069b188	2026-06-22	069b188	9,291 B	A	view · diff
git:20260604.ff4203a	2026-06-04	ff4203a	9,411 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (9407 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

GitHub

tomzx/agents · 12 stars · license MIT · pushed 2026-10-21 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_ontet2zbplypar6r
GET https://markdownregistry.com/api/v1/resolve?ref=tomzx/agents/configure-labels
GET https://markdownregistry.com/api/v1/blob/7af42638ec0917fd7e4a943e6e8275c17957e387ee3b4dd72e233b915b23d406

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.

More from tomzx/agents

AGENTS.md AGENTS.md file

tomzx/agents · AGENTS.md

git:20261006.2803bc1 · audit A · 12 stars

CLAUDE.md CLAUDE.md file

tomzx/agents · CLAUDE.md

git:20260209.7ff04f3 · audit B · 12 stars

AGENTS.md@repositories/openchamber/openchamber AGENTS.md file

tomzx/agents · repositories/openchamber/openchamber/AGENTS.md

git:20260726.7244df1 · audit B · 12 stars

agents-section-daily-refresh SKILL.md skill

tomzx/agents · skills/agents-section-daily-refresh/SKILL.md · Curate the agent-maintained blog section (blog.tomrochette.com-content) by following the Daily refresh procedure in…