amendment-record SKILL.md skillA
amendment-record from openehr/ai-plugins is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add openehr/ai-plugins/amendment-record@git:20261008.b2a84a7Pins git:20261008.b2a84a7 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- openehr/ai-plugins
- Path
plugins/openehr-specs/skills/amendment-record/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261008.b2a84a7, committed Oct 8, 2026
- First version recorded
- Jun 5, 2026
- Size
- 6,797 bytes
- Repository stars
- 3
- License
- Apache-2.0
Author or update amendment records in openEHR specification documents: the `master00-amendment_record.adoc` table in `specifications-XX` repos. This skill should be used when the user asks to add or update an amendment entry, choose the document version bump, add a CR/PR reference, mark a release boundary, or fix the `latest_issue`/`latest_issue_date` anchors. Not for the ITS-REST amendment record (use its-rest), general spec authoring (use authoring), the release process (use governance), or…
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
# openEHR Specification Amendment Record Authoring
The amendment record tracks every change to an openEHR specification document. It appears as
`master00-amendment_record.adoc` in each spec directory within the `specifications-XX`
repositories (RM, AM, BASE, LANG, PROC, SM, QUERY, CNF, TERM, ITS-*) and is included in
`master.adoc` after the front matter. The conventions here are specific to the openEHR
specification ecosystem and its Jira-based change management process. The `specifications-ITS-REST`
record is an HTML table, not this file; use the `its-rest` skill for it.
For detailed lookups — Jira project keys, CR/PR linking phrasing, release-boundary placement,
multi-raiser formatting, multi-change grouping, and detail-text style — see
**`references/conventions.md`**.
## File Structure
```asciidoc
= Amendment Record
[cols="1,6,2,2", options="header"]
|===
|Issue|Details|Raiser|Completed
|[[latest_issue]]N.N.N
|{Details of most recent change.}
|{Raiser name(s)}
|[[latest_issue_date]]dd Mon yyyy
|
|{Details of previous change.}
|{Raiser name(s)}
|dd Mon yyyy
4+^h|*XX Release N.N.N*
|N.N.N
|{Details of change in previous release.}
|{Raiser name(s)}
|dd Mon yyyy
|===
```
…Read the whole file at its exact version.
How to install
mdr add openehr/ai-plugins/amendment-record@sha256:992180160ce69df7The line at the top of this page pins the label git:20261008.b2a84a7, 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_dgzb76zzpqav3a4r)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Jun 5, 2026 and Oct 8, 2026, about one every 42 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261008.b2a84a7 latest | 2026-10-08 | b2a84a7 | 6,797 B | A | view · diff |
| git:20261007.405e68d | 2026-10-07 | 405e68d | 6,049 B | A | view · diff |
| git:20261007.d097047 | 2026-10-07 | d097047 | 5,018 B | A | view · diff |
| git:20260605.b66fd15 | 2026-06-05 | b66fd15 | 4,163 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 (6797 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
openehr/ai-plugins · 3 stars · license Apache-2.0 · pushed 2026-10-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_dgzb76zzpqav3a4r GET https://markdownregistry.com/api/v1/resolve?ref=openehr/ai-plugins/amendment-record GET https://markdownregistry.com/api/v1/blob/992180160ce69df70ea2b05a200cc3b459b7d7af0a497eacb550c99fe52eca5c
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.