Capa Officer
v2.1.1CAPA system management for medical device QMS. Covers root cause analysis, corrective action planning, effectiveness verification, and CAPA metrics. Use for...
⭐ 1· 1.6k·8 current·8 all-time
byAlireza Rezvani@alirezarezvani
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description, SKILL.md content, reference docs, and the included capa_tracker.py script all align with CAPA investigation, RCA, verification, and metrics reporting. No environment variables, unrelated binaries, or surprising dependencies are requested.
Instruction Scope
SKILL.md contains procedural guidance, templates, and decision trees for CAPA work; it does not instruct the agent to read arbitrary system files, access credentials, or transmit data to external endpoints. The instructions stay within the CAPA domain.
Install Mechanism
There is no install specification (instruction-only) and included code is bundled with the skill. No remote downloads or extract steps are present. This minimizes supply-chain/install risk.
Credentials
The skill declares no required environment variables, credentials, or config paths. That matches the documented purpose (local CAPA guidance and a local tracker script).
Persistence & Privilege
always is false and the skill does not request persistent system-wide configuration or cross-skill modifications. Model invocation is enabled (platform default) but that is normal and not excessive here.
Assessment
This skill appears coherent and self-contained for CAPA/QMS use. Before installing: (1) Review the included capa_tracker.py source yourself (it runs locally and appears not to make network calls) and confirm its behavior is acceptable for your environment; (2) Avoid feeding sensitive patient data or PHI into third-party skills unless you’ve validated data handling and compliance; (3) If you prefer to limit autonomous behavior, disable model invocation for the skill or require explicit user invocation; (4) Run the script in a sandbox or test workspace first and validate reports and recommendations against your SOPs. If you need the vendor/source verified, ask the publisher for provenance or a repository link before use.Like a lobster shell, security has layers — review code before you run it.
latestvk97d66te8mgk41585cc1y2mnw982kh7x
License
MIT-0
Free to use, modify, and redistribute. No attribution required.