investigate-capa-root-cause SKILL.md skillA
investigate-capa-root-cause 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/investigate-capa-root-cause@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/investigate-capa-root-cause/SKILL.md- Versions recorded
- 3
- Latest version
- v1.0, committed Aug 17, 2026
- First version recorded
- Apr 19, 2026
- Size
- 12,815 bytes
- Repository stars
- 43
- License
- MIT
Investigate root causes and manage CAPAs (Corrective and Preventive Actions) for compliance deviations. Covers investigation method selection (5-Why, fishbone, fault tree), structured root cause analysis, corrective vs preventive action design, effectiveness verification, and trend analysis. Use when an audit finding requires a CAPA, when a deviation or incident occurs in a validated system, when a regulatory observation needs a formal response, when a data integrity anomaly requires…
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
# Investigate CAPA Root Cause Conduct a structured root cause investigation and develop effective corrective and preventive actions for compliance deviations. ## When to Use - An audit finding requires a CAPA - A deviation or incident occurred in a validated system - A regulatory inspection observation needs a formal response - A data integrity anomaly requires investigation - Recurring issues suggest a systemic root cause ## Inputs - **Required**: Description of the deviation, finding, or incident - **Required**: Severity classification (critical, major, minor) - **Required**: Evidence collected during the audit or investigation - **Optional**: Previous related CAPAs or investigations - **Optional**: Relevant SOPs, validation documents, and system logs - **Optional**: Interview notes from involved personnel ## Procedure ### Step 1: Initiate the Investigation ```markdown # Root Cause Investigation ## Document ID: RCA-[CAPA-ID] ## CAPA Reference: CAPA-[YYYY]-[NNN] ### 1. Trigger | Field | Value | |-------|-------| | Source | [Audit finding / Deviation / Inspection observation / Monitoring alert] | | Reference | [Finding ID, deviation ID, or observation number] | …
Read the whole file at its exact version.
How to install
mdr add pjt222/agent-almanac/investigate-capa-root-cause@sha256:0b1391f595b31cd8The 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_o2itq3lz73gfpmyu)
3 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 | 12,815 B | A | view · diff |
| v1.0 | 2026-04-26 | f5b501b | 12,786 B | A | view · diff |
| v1.0 | 2026-04-19 | e334ebd | 12,884 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 (12815 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_o2itq3lz73gfpmyu GET https://markdownregistry.com/api/v1/resolve?ref=pjt222/agent-almanac/investigate-capa-root-cause GET https://markdownregistry.com/api/v1/blob/0b1391f595b31cd8668b11664f32340da482757131476a7cd9e319cdb2808c8c
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.