Implement Audit Trail
技能 已验证 活跃Implement 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.
功能
- 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
使用场景
- 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
非目标
- 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.
安装
/plugin install agent-almanac@pjt222-agent-almanac质量评分
已验证类似扩展
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 for legal teams using Claude. Loads the right reference for the user's question (privilege configuration, MCP hardening, verification, long documents, practice-area patterns, skill authoring) and routes to specialized starter skills (NDA triage, version diff, meeting brief, citation verification, status synthesis). Auto-invokes when the user mentions legal work, contracts, redlines, NDAs, privilege, attorney-client, court filings, depositions, regulatory compliance, or asks how to set up Claude for a law firm or in-house legal team.
TradeMemory Protocol
100Evolution Engine 的领域知识 — 支持 LLM 从原始 OHLCV 数据中自主发现策略。涵盖生成-回测-选择-进化循环、向量化回测、样本外验证和策略梯度。在发现交易模式、运行回测、进化策略或审查进化日志时使用。由“evolve”、“discover patterns”、“backtest”、“evolution”、“strategy generation”、“candidate strategy”触发。
Context Mode Ops
100使用并行子代理军队管理 context-mode GitHub 问题、PR、发布和营销。为每个任务编排 10-20 个动态代理。在分类问题、审查 PR、发布版本、撰写 LinkedIn 帖子、宣布发布、修复错误、合并贡献、验证 ENV 变量、测试适配器或同步分支时使用。