compliance-controls

Map audit controls to evidence sources for automated compliance reporting.

Updated May 11, 2026

Search Tags:#audit #compliance #evidence #gdpr #pci-dss #soc2 #vendor-risk

Ready to run

npx skills add https://github.com/resultakak/argos --skill compliance-controls

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: compliance-controls
Source: https://github.com/resultakak/argos/tree/main/skills/compliance-controls
Command: npx skills add https://github.com/resultakak/argos --skill compliance-controls

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Compliance controls are mapped to audit evidence and runbooks to speed audits and reduce manual chasing of artifacts.

Core Features & Use Cases

Evidence-first control mapping: link controls to logs, change histories, and runbooks.
Continuous audit prep: asset inventory, data inventory, gap tracking, and vendor risk tracking.
DSR, incident response, and audit-response workflows with automation-friendly outputs.

Quick Start

Begin by defining scope, inventorying assets, and mapping core controls to evidence sources to begin continuous audit prep.

Frequently Asked Questions about compliance-controls

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I map audit controls to evidence sources for SOC 2 or GDPR?▼

Map audit controls to evidence sources by linking SOC 2 and GDPR requirements to logs, change histories, and runbooks. This enables automated collection and reporting while maintaining traceability across frameworks.

What's the best way to automate continuous audit preparation?▼

Automate continuous audit preparation by inventorying assets and data, then mapping core controls to automated sources like CloudTrail, git history, IaC diffs, and vulnerability scans to maintain continuous evidence traceability.

Can I use CloudTrail and git history for PCI-DSS compliance evidence collection?▼

Yes, you can use CloudTrail and git history for PCI-DSS compliance evidence collection. The system applies evidence-first control mapping to automated sources to maintain traceability across PCI-DSS scenarios.

How does evidence-first control mapping work for vendor risk management?▼

Evidence-first control mapping for vendor risk management works by linking vendor risk tracking controls to automated evidence sources like IaC diffs and vulnerability scans, enabling continuous gap tracking and audit-ready reporting.

Does this approach support incident response and DSR workflows?▼

Yes, this approach supports incident response and DSR workflows by providing automation-friendly outputs mapped to evidence sources. It links controls to runbooks to speed up audit response and reduce manual artifact chasing.