Implement Audit Trail
Skill Verifiziert AktivImplement audit trail functionality for R projects in regulated environments. Covers logging, provenance tracking, electronic signatures, data integrity checks, and 21 CFR Part 11 compliance. Use when an R analysis requires electronic records compliance (21 CFR Part 11), when you need to track who did what and when in an analysis, when implementing data provenance tracking, or when creating tamper-evident analysis logs for regulatory submissions.
To enable R projects in regulated environments to meet compliance requirements by implementing comprehensive audit trails, including logging, provenance, and data integrity checks.
Funktionen
- Structured audit logging for R sessions
- Data integrity verification via hashing
- Tracking of data transformations
- Recording of session environment information
- Integration with Git for change control
Anwendungsfälle
- When an R analysis requires electronic records compliance (21 CFR Part 11)
- When needing to track who did what and when in an R analysis
- When implementing data provenance tracking for R projects
- When creating tamper-evident analysis logs for regulatory submissions
Nicht-Ziele
- Managing R package dependencies beyond R's standard mechanisms
- Performing general code quality checks or static analysis
- Directly interacting with external regulatory submission systems
Documentation
- info:Configuration & parameter referenceWhile the skill's functions are documented with parameters and their purpose, default values are not explicitly stated for parameters like `log_dir` and `analyst` in `init_audit_log`.
Code Execution
- info:ValidationThe R functions include checks for basic conditions (e.g., audit log initialization) and use standard R package functions for hashing and data comparison, but do not explicitly use a schema validation library for all inputs and outputs.
- info:Error HandlingThe R code includes basic error handling with `stop()` calls for critical failures like uninitialized logs, and `warning()` for integrity check failures, but doesn't employ structured error reporting with `code`, `retryable`, or `hint` fields.
Compliance
- info:GDPRThe skill logs analyst names and session information, which could potentially include personal data if not handled carefully. However, it does not submit this data to a third party, and the primary focus is on compliance with regulations like 21 CFR Part 11, not general GDPR compliance.
Errors
- info:Actionable error messagesError messages in the R code (e.g., 'Audit log not initialized') clearly state the problem but lack specific remediation steps or documentation links.
Execution
- info:Pinned dependenciesThe SKILL.md frontmatter lists `jsonlite` and `digest` as `allowed-tools`, but these are R packages and their versions are not explicitly pinned within the skill's documentation or scripts.
Practical Utility
- info:Edge casesThe skill mentions common pitfalls like missing timestamps and forgotten initialization, but does not provide explicit documentation for handling all potential failure modes with defined recovery steps within the SKILL.md.
Installation
/plugin install agent-almanac@pjt222-agent-almanacQualitätspunktzahl
VerifiziertVertrauenssignale
Ähnliche Erweiterungen
Monitor Data Integrity
100Design and operate a data integrity monitoring programme based on ALCOA+ principles. Covers detective controls, audit trail review schedules, anomaly detection patterns (off-hours activity, sequential modifications, bulk changes), metrics dashboards, investigation triggers, and escalation matrix definition. Use when establishing a data integrity monitoring programme for GxP systems, preparing for inspections where data integrity is a focus area, after a data integrity incident requiring enhanced monitoring, or when implementing MHRA, WHO, or PIC/S guidance.
Prepare Inspection Readiness
100Prepare an organisation for regulatory inspection by assessing readiness against agency-specific focus areas (FDA, EMA, MHRA). Covers warning letter and 483 theme analysis, mock inspection protocols, document bundle preparation, inspection logistics, and response template creation. Use when a regulatory inspection has been announced or is anticipated, when a periodic self-assessment is due, when new systems have been implemented since the last inspection, or after a significant audit finding that may attract regulatory attention.
Investigate Capa Root Cause
100Investigate 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 investigation, or when recurring issues suggest a systemic root cause.
Master Claude for Legal
100Master-Skill für Rechtsteams, die Claude verwenden. Lädt die richtige Referenz für die Benutzerfrage (Konfiguration von Privilegien, MCP-Härtung, Verifizierung, lange Dokumente, Muster für Fachbereiche, Skill-Erstellung) und leitet an spezialisierte Starter-Skills weiter (NDA-Triage, Versionsvergleich, Besprechungszusammenfassung, Zitationsverifizierung, Status-Synthese). Wird automatisch aufgerufen, wenn der Benutzer juristische Arbeit, Verträge, Redlines, NDAs, Privilegien, Anwaltsgeheimnis, Gerichtsakten, Vernehmungen, regulatorische Compliance erwähnt oder fragt, wie Claude für eine Anwaltskanzlei oder ein internes Rechtsteam eingerichtet wird.
TradeMemory Protocol
100Domänenwissen für die Evolution Engine — LLM-gestützte autonome Strategieentdeckung aus rohen OHLCV-Daten. Behandelt die Schleife Generieren-Backtesten-Auswählen-Entwickeln, vektorisiertes Backtesting, Out-of-Sample-Validierung und Strategiegraduierung. Verwenden Sie es beim Entdecken von Handelspatterns, Ausführen von Backtests, Entwickeln von Strategien oder Überprüfen von Evolutionsprotokollen. Löst aus bei "evolve", "discover patterns", "backtest", "evolution", "strategy generation", "candidate strategy".
Context Mode Ops
100Verwalten Sie GitHub-Issues, PRs, Releases und Marketing mit parallelen Subagenten-Armeen im Context-Mode. Orchestriert 10-20 dynamische Agenten pro Aufgabe. Verwenden Sie dies bei der Triage von Issues, der Überprüfung von PRs, der Veröffentlichung von Versionen, dem Schreiben von LinkedIn-Posts, der Ankündigung von Releases, der Behebung von Fehlern, dem Mergen von Beiträgen, der Validierung von ENV-Variablen, dem Testen von Adaptern oder dem Synchronisieren von Branches.