init SKILL.md skillA
This file is byte-identical to the first copy the registry indexed, one of 4 indexed copies. Same content hash, so the same checks give both the same grade.
init from phmatray/tagout is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add phmatray/tagout/init@git:20261010.9485205Pins git:20261010.9485205 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- phmatray/tagout
- Path
plugins/tagout/skills/init/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261010.9485205, committed Oct 10, 2026
- First version recorded
- Oct 9, 2026
- Size
- 7,481 bytes
- Repository stars
- 4
- License
- MIT
Make a repository ready for the issue/PR lifecycle skills in one command — record its facts in the committed profile (`.claude/skills/repo-profile.md`: commit identity, build/test commands, labels, merge style, conflict hot-spots), converge its labels, issue forms, settings, topics and Pages source from a manifest, then refresh the profile. Use for a new repo or one that drifted: "init this repo for the kit", "set up the repo profile", "set up the labels…
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
# Make a repository ready for the lifecycle skills `create-issue`, `implement-issue`, `merge-pr` and `auto-dev` are generic workflows wrapped around a thin layer of repo-specific facts. This skill does the whole setup story in one pass: it **records** those facts in a committed profile, **converges** the configuration they describe (labels, issue forms, settings, topics, Pages source) from a declarative manifest, and **refreshes** the profile so it reports what now exists. Decision record: [ADR 0018](../../docs/adr/0018-profile-repo-and-setup-repo-merge-into-init.md). The profile is data, not a skill ([ADR 0001](../../docs/adr/0001-the-repo-profile-is-committed-data-not-a-skill.md)): the lifecycle skills read it at their Step 1, and only reach for this skill when it is missing. ## Three paths | Invocation | Does | Writes on GitHub | |---|---|---| | `/tagout:init` | profile → `plan` → `apply` when it found drift → refresh the profile | yes — labels, forms, settings, topics, Pages | | `/tagout:init --plan` | profile → `plan`; prints the drift | no | | `/tagout:init --profile-only` | show the profile, or generate it when missing (add `--refresh` to regenerate) | no | …
Read the whole file at its exact version.
How to install
mdr add phmatray/tagout/init@sha256:03bce3a1c2057e30The line at the top of this page pins the label git:20261010.9485205, 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_kixhydmir4omnjnc)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Oct 9, 2026 and Oct 10, 2026, more than one a day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261010.9485205 latest | 2026-10-10 | 9485205 | 7,481 B | A | view · diff |
| git:20261010.7178022 | 2026-10-10 | 7178022 | 7,489 B | A | view · diff |
| git:20261009.640c9a3 | 2026-10-09 | 640c9a3 | 7,597 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 (7481 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
phmatray/tagout · 4 stars · license MIT · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_kixhydmir4omnjnc GET https://markdownregistry.com/api/v1/resolve?ref=phmatray/tagout/init GET https://markdownregistry.com/api/v1/blob/03bce3a1c2057e301d545306bb0fd7120b6a1faaf3870527f4cb65b8add3c376
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.