manage-change-control SKILL.md skillA
manage-change-control from pjt222/agent-almanac is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add pjt222/agent-almanac/manage-change-control@v1.0Pins v1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- pjt222/agent-almanac
- Path
i18n/caveman-lite/skills/manage-change-control/SKILL.md- Versions recorded
- 3
- Latest version
- v1.0, committed Aug 17, 2026
- First version recorded
- Apr 19, 2026
- Size
- 10,664 bytes
- Repository stars
- 43
- License
- MIT
Manage change control for validated computerized systems. Covers change request triage (emergency, standard, minor), impact assessment on validated state, revalidation scope determination, approval workflows, implementation tracking, and post-change verification. Use when a validated system requires a software upgrade, patch, or configuration change; when infrastructure changes affect validated systems; when a CAPA requires system modification; or when emergency changes need expedited approval…
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
# Manage Change Control Evaluate, approve, implement, and verify changes to validated computerized systems while maintaining their validated state. ## When to Use - A validated system requires a software upgrade, patch, or configuration change - Infrastructure changes (server migration, OS upgrade, network change) affect validated systems - A CAPA or audit finding requires system modification - Business process changes require system reconfiguration - Emergency changes need expedited approval and retrospective documentation ## Inputs - **Required**: Change description (what is changing and why) - **Required**: System(s) affected and their current validated state - **Required**: Change requestor and business justification - **Optional**: Vendor release notes or technical documentation - **Optional**: Related CAPA or audit finding references - **Optional**: Existing validation documentation for affected system(s) ## Procedure ### Step 1: Create and Classify the Change Request ```markdown # Change Request ## Document ID: CR-[SYS]-[YYYY]-[NNN] ### 1. Change Description **Requestor:** [Name, Department] **Date:** [YYYY-MM-DD] **System:** [System name and version] …
Read the whole file at its exact version.
How to install
mdr add pjt222/agent-almanac/manage-change-control@sha256:e53335ae72ce5cedThe line at the top of this page pins the label v1.0, 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_55g5kq4a2e3fuxm4)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Apr 19, 2026 and Aug 17, 2026, about one every 60 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0 latest | 2026-08-17 | a784899 | 10,664 B | A | view · diff |
| v1.0 | 2026-04-26 | f5b501b | 10,635 B | A | view · diff |
| v1.0 | 2026-04-19 | e334ebd | 10,682 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 (10664 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
pjt222/agent-almanac · 43 stars · license MIT · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_55g5kq4a2e3fuxm4 GET https://markdownregistry.com/api/v1/resolve?ref=pjt222/agent-almanac/manage-change-control GET https://markdownregistry.com/api/v1/blob/e53335ae72ce5ced9663780c74e6bc11366a91fa78c8d7b08199a70605e65bd6
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.