aireg-publish SKILL.md skillA
aireg-publish from atlanai/ai-registry is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add atlanai/ai-registry/aireg-publish@git:20261014.5e72f77Pins git:20261014.5e72f77 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- atlanai/ai-registry
- Path
examples/aireg/artifacts/aireg/skill/aireg-publish/0.1.1/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261014.5e72f77, committed Oct 14, 2026
- Size
- 7,458 bytes
- Repository stars
- 12
- License
- Apache-2.0
Publish a skill or agent to a registry, or release a new version of one, including an edit made to an installed copy. Use when asked to publish, share, contribute or release a skill or agent, send an edit to an installed skill back to its registry, update one that is already in a registry, publish a project's skills from CI, or fix what registry validation reports.
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
# Publish to a registry A released version is never edited: every change is a new version. Pass `--json` to the CLI and read `data`. Pick the path by where the user is working: - **An installed skill or agent the user edited**: send it home. - **Outside the registry's repository**, with a skill in some folder: contribute it. - **A project whose skills should reach a registry on every change**: publish from CI. - **Inside the registry's repository**: add or version it there, then release. ## An installed skill you edited `aireg status --json` shows it `edited`. Publish it by name, and don't read `.registry/` to work out where it came from: ```sh aireg publish <name> --dry-run --yes --json # data.artifacts: the version it would release aireg publish <name> --yes --json ``` - A registry in a folder takes the next version in place. - A git registry exits 2 with `is a git registry`: publish into a clone instead, as below, with `aireg publish <name> --to ../<clone>/<namespace> --yes --json`. - If a newer version was published since the edit, it refuses. Offer `aireg update` and redoing the edit there, or `--force` to publish over it. ## Contribute from any folder …
Read the whole file at its exact version.
How to install
mdr add atlanai/ai-registry/aireg-publish@sha256:01d8f9c220d303b5The line at the top of this page pins the label git:20261014.5e72f77, 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_pygeukab6uofqkdc)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 14, 2026.
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 (7458 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
atlanai/ai-registry · 12 stars · license Apache-2.0 · pushed 2026-10-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_pygeukab6uofqkdc GET https://markdownregistry.com/api/v1/resolve?ref=atlanai/ai-registry/aireg-publish GET https://markdownregistry.com/api/v1/blob/01d8f9c220d303b56047772710c4aa37dcfa3ca8cbbc65b3d42740d3ae00afd7
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 atlanai/ai-registry
Every file in atlanai/ai-registry