agentsclimarketplace

Compliance monitoring

Skill Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack/plugins/devtools-pack/skills/compliance-monitoring

A curated pack of custom Claude Code skills for developers — installable as a Claude Code plugin marketplace.

Install
npx -y skills add Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack --skill compliance-monitoring

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

When to activate: compliance monitoring, continuous compliance, control monitoring, compliance dashboard, policy attestation, compliance calendar, third-party audit, KRI, KCI

SKILL.md

8.5 KB, ~1.9k tokens by cl100k_base, as published. Nobody here has run it

Compliance Monitoring

Continuous Control Monitoring Framework

Monitoring Levels

LevelWhatHowFrequency
AutomatedTechnical controls (patch status, MFA enforcement, encryption)SIEM, CSPM, vulnerability scannersReal-time / daily
Semi-automatedProcess controls (access reviews completed, training done)GRC platform, HRIS integrationWeekly / monthly
ManualJudgment controls (policy adherence, vendor assessments)Sampling, walkthroughsQuarterly / annually

Control Monitoring Architecture

Data Sources → Monitoring Tools → GRC Platform → Dashboard → Alerts
─────────────────────────────────────────────────────────────────────
SIEM logs     →  Splunk/Sentinel →  ServiceNow  → KCI view  → Slack/email
CSPM scans    →  Wiz/Prisma      →  GRC         → Risk heat → PagerDuty
Vuln scanner  →  Tenable/Qualys  →  GRC         → map       → Jira tickets
HRIS data     →  Direct API      →  GRC         →           →

Compliance Dashboard Design

Dashboard Sections

1. Overall Compliance Posture

  • Compliance score by framework (0-100%)
  • Trend vs prior period (up/down with delta)
  • Controls by status: Effective / Needs Attention / Failing / Not Tested

2. Control Performance

Control domainTotalEffectiveAt riskFailing
Access control242211
Change management121110
Vulnerability mgmt8620
Incident response101000

3. Exception Register Summary

  • Open exceptions by age (< 30 days / 30-90 days / > 90 days)
  • Exceptions by severity (Critical / High / Medium / Low)
  • Overdue remediation items

4. Upcoming Compliance Activities

  • Access reviews due
  • Policy attestations due
  • Audit windows approaching
  • Certification renewals

5. Regulatory Deadlines

  • Breach notification windows (if active incidents)
  • Filing deadlines
  • Audit submission dates

Exception Management Process

Exception Lifecycle

Identified → Documented → Risk Accepted → Monitored → Remediated/Expired

Exception Request Template

Exception ID: EXC-2024-047
Control: CC6.1 — MFA for all admin access
Exception: Legacy system X cannot support MFA due to vendor limitation
Business justification: Critical operational system; vendor roadmap: MFA in Q3
Risk level: High
Compensating controls:
  - Network-level access restriction (IP whitelist)
  - Session recording enabled
  - Access limited to 2 named administrators
  - Quarterly access review
Requested by: [Name], [Title]
Approved by: CISO
Valid until: [Date — max 12 months]
Review date: [Mid-point review date]

Exception Approval Authority

Risk levelApproval required
LowControl owner
MediumCompliance team
HighCISO or equivalent
CriticalCISO + Legal + Executive sponsor

Exception Reporting

  • All open exceptions in monthly compliance report
  • Critical exceptions flagged to board/audit committee quarterly
  • Exceptions approaching expiry: 30-day advance notification to owner

Policy Attestation Workflow

Annual Attestation Process

  1. Q4 prior year: Review and update all policies
  2. January: Distribute attestation to all covered employees
  3. Rolling 30 days: Employees read and acknowledge each policy
  4. Day 30: Send reminder to non-completers
  5. Day 45: Escalate non-completers to managers
  6. Day 60: Final escalation to HR for disciplinary follow-up
  7. End of cycle: Report completion rates to leadership

Attestation Coverage

PolicyAudienceFrequency
Information Security PolicyAll employeesAnnual
Acceptable Use PolicyAll employeesAnnual
Data Classification PolicyAll employeesAnnual
Privacy Policy (internal)All employeesAnnual
Code of ConductAll employeesAnnual
Conflicts of InterestLeadership + financeAnnual
PCI DSS (if applicable)In-scope employeesAnnual

Completion Targets

  • Overall completion: ≥ 98% by 60-day deadline
  • Manager-level and above: 100% required
  • Non-completion = unacceptable for audit purposes; HR notified

Compliance Calendar Template

By Regulation

GDPR / Data Protection

MonthActivity
JanuaryAnnual privacy notice review
MarchDPA / controller-processor agreements review
JuneData subject request metrics review
SeptemberDPIA review for new processing activities
NovemberData breach register review

SOC 2

TimingActivity
OngoingEvidence collection for audit period
QuarterlyAccess reviews, VA scans
60 days before auditGap assessment
30 days before auditEvidence packaging
Audit windowAuditor fieldwork support

ISO 27001

TimingActivity
AnnualInternal audit
AnnualRisk assessment
AnnualManagement review
AnnualPolicy review and approval
Every 3 yearsCertification audit (+ annual surveillance audits)

Automated vs Manual Control Testing

Control typeAutomated testing approachManual testing approach
MFA enforcementQuery IdP — % accounts with MFA disabledSample access logs; verify manual bypass impossible
Patch currencyPull patch scan results; flag > 30-day-old critical patchesReview sample of systems for patch evidence
Encryption at restCSPM scan for unencrypted storageReview encryption configuration documentation
Access reviewsTrack completion % from GRC platformVerify sample of certifications have correct decisions
Incident responseTabletop exercise resultsReview incident log for response time vs SLA
Change managementPull % of changes with approved ticketsSample emergency changes for retroactive approval

Key Risk Indicators vs Key Control Indicators

Key Risk Indicators (KRIs) — leading indicators of risk

KRIThresholdAction
Open critical vulnerabilities > 30 days> 5Escalate to CISO
Failed login attempts (anomalous spike)> 3× baselineTrigger investigation
Privilege escalation events unreviewed> 0Immediate review
Employees without security training> 5%Escalate to HR
Critical vendor without SOC 2> 0Risk acceptance or remediation

Key Control Indicators (KCIs) — lagging indicators of control effectiveness

KCITargetAlert threshold
MFA adoption rate100%< 98%
Access review completion100% by deadline< 95% at 30 days
Patch SLA compliance (critical)100% within 30 days< 90%
Policy attestation completion≥ 98%< 90%
Incident response time (P1)< 1 hour> 4 hours

Compliance Reporting

Monthly Report — Internal

  • Control effectiveness summary (% effective)
  • Open exceptions and aging
  • Incidents with compliance implications
  • Upcoming deadlines

Quarterly Report — Leadership

  • Compliance posture vs prior quarter
  • Key risks and mitigations
  • Audit findings and remediation status
  • Regulatory changes on horizon

Annual Report — Board / Audit Committee

  • Year-in-review: assessments completed, certifications maintained
  • Material risks and how addressed
  • Budget vs actuals for compliance program
  • Roadmap for coming year

Regulatory Change Management

  1. Monitor: Subscribe to regulatory update feeds (IAPP, regulatory agency newsletters)
  2. Assess: For each change, assess applicability and impact on current controls
  3. Gap analysis: Identify control gaps created by new requirements
  4. Remediation plan: Timeline and owner for each gap
  5. Update: Revise policies, procedures, training to reflect changes
  6. Communicate: Brief relevant teams and leadership on changes
  7. Document: Record assessment and response for audit evidence

Gives 0 of the 12 instructions most audit compliance skills give in ~1.9k tokens

Counted across 936 of the 1,487 authors here whose files we hold, read 2026-08-06

  • group findings by severityin 44 of 936
  • Fetch latest guidelines before each reviewin 43 of 936, across 3 files
  • Check files against all fetched rulesin 42 of 936, across 2 files
  • Output findings in terse file:line formatin 41 of 936, across 3 files
  • Ask user which files to review if none specifiedin 41 of 936, across 3 files
  • Read specified files or prompt user for filesin 39 of 936, across 1 file
  • generate the audit reportin 39 of 936, across 36 files
  • assign a severity to every findingin 25 of 936
  • run automated accessibility scansin 23 of 936, across 13 files
  • map findings to WCAG criteriain 20 of 936, across 10 files
  • confirm audit scopein 19 of 936, across 9 files
  • check title tags and meta descriptions for uniquenessin 19 of 936, across 5 files

Said here and by no other author read

  • track controls across automated semi-automated and manual levels
  • route monitoring tool data to a GRC platform
  • maintain a compliance dashboard
  • document exceptions with compensating controls
  • obtain approval based on exception risk level
  • monitor exceptions and notify owners before expiry

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.