Sparkfinderoven Security Compliance Skills
Security & compliance skill suite with OWASP scanning, CVE detection, GDPR audits, SOC2 readiness, threat modeling, and incident response workflows
- Skill ID
- reason-machines/security-skills/sparkfinderoven-security-compliance-skills
- Publisher
- reason-machines
- Repository
- security-skills
- Installs
- 0
- Files
- 1
- Synced
- Sep 23, 2026
Open any RiverX project, open the Skills panel in the chat, and search for this identifier. The files are fetched from the source repository at install time.
reason-machines/security-skills/sparkfinderoven-security-compliance-skillsInstalls these files- SKILL.md
What this skill tells the agent
🔒 Security & Compliance Skills Suite
Skill by ara.so — Security Skills collection.
This skill suite provides specialized commands and workflows for security audits, vulnerability management, compliance (GDPR/SOC2/ISO27001), and incident response. Derived from hesreallyhim/awesome-claude-code, it offers 10 security-focused commands and 5 multi-step workflows with structured output.
Installation
Local Installation
# Clone the repository
git clone https://github.com/sparkfinderoven/r01-hesreallyhim-awesome-claude-code-security.git
# Copy to Claude skills directory
mkdir -p ~/.claude/skills
cp -r r01-hesreallyhim-awesome-claude-code-security ~/.claude/skills/security-compliance
# Or create symlink for auto-updates
ln -s $(pwd)/r01-hesreallyhim-awesome-claude-code-security ~/.claude/skills/security-complianceRegister with Claude Code
In a Claude Code session:
/read ~/.claude/skills/security-compliance/SKILL.mdCore Commands
/owasp-scan - OWASP Top 10 Security Scan
Scans code for OWASP Top 10 vulnerabilities with exploit descriptions, CVSS scores, and remediation steps.
Usage:
/owasp-scan <target_directory>
/owasp-scan src/ --output json
/owasp-scan . --exclude node_modules,distOutput Structure:
╔══════════════════════════════════════════════════╗
║ OWASP Top 10 Scan — src/ ║
╠══════════════════════════════════════════════════╣
║ A01 Broken Access Control ✓ 3 checks ║
║ A02 Cryptographic Failures ✓ 2 checks ║
║ A03 Injection ✓ 5 checks ║
║ A04 Insecure Design ✓ 1 check ║
║ A05 Security Misconfiguration ✓ 4 checks ║
╚══════════════════════════════════════════════════╝
FINDINGS (17 files scanned)
┌──────┬────────────────────────────────┬──────────┬─────────────┐
│ Sev │ Vulnerability │ CVSS │ File:Line │
├──────┼────────────────────────────────┼──────────┼─────────────┤
│ 🔴 │ SQL Injection │ 9.8 │ api.js:45 │
│ 🔴 │ Hardcoded JWT Secret │ 9.1 │ auth.js:12 │
│ 🟠 │ Insecure Deserialization │ 8.1 │ parser.js:8 │
│ 🟡 │ Missing CSRF Protection │ 6.5 │ routes.js:3 │
└──────┴────────────────────────────────┴──────────┴─────────────┘Example Remediation:
// ❌ VULNERABLE: SQL Injection
const query = `SELECT * FROM users WHERE id = ${req.params.id}`;
// ✅ FIXED: Parameterized Query
const query = 'SELECT * FROM users WHERE id = ?';
db.query(query, [req.params.id]);
// ❌ VULNERABLE: Hardcoded Secret
const secret = 'my-secret-key-123';
// ✅ FIXED: Environment Variable
const secret = process.env.JWT_SECRET;/dep-cve - Dependency CVE Scanner
Analyzes project dependencies for known CVEs with exploitability scores and upgrade paths.
Usage:
/dep-cve
/dep-cve --scope full --output md
/dep-cve --severity high,criticalExample Output:
CVE SCAN RESULTS (234 dependencies checked)
Critical Vulnerabilities: 2
High: 5
Medium: 12
Low: 8
┌────────────┬─────────────────┬──────────┬────────────┬──────────────┐
│ Package │ CVE ID │ CVSS │ Current │ Fix Version │
├────────────┼─────────────────┼──────────┼────────────┼──────────────┤
│ lodash │ CVE-2021-23337 │ 9.8 │ 4.17.15 │ 4.17.21 │
│ express │ CVE-2022-24999 │ 7.5 │ 4.17.1 │ 4.18.0 │
└────────────┴─────────────────┴──────────┴────────────┴──────────────┘
UPGRADE PATH:
npm update lodash@4.17.21 express@4.18.0Checking in CI/CD:
# .github/workflows/security.yml
name: Security Scan
on: [push, pull_request]
jobs:
cve-scan:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- name: CVE Scan
run: |
/dep-cve --severity critical,high --output json > cve-report.json
if [ $(jq '.critical + .high' cve-report.json) -gt 0 ]; then
exit 1
fi/gdpr-audit - GDPR Compliance Audit
Maps data flows, identifies consent gaps, and generates DPA (Data Processing Agreement) checklists.
Usage:
/gdpr-audit
/gdpr-audit --scope full --output pdf
/gdpr-audit --focus consent,data-flowExample Analysis:
╔══════════════════════════════════════════════════╗
║ GDPR Compliance Audit ║
╠══════════════════════════════════════════════════╣
║ Data Inventory ✓ Complete ║
║ Consent Mechanisms ⚠ 3 gaps found ║
║ Data Flow Mapping ✓ Complete ║
║ DPA Requirements ✗ 5 missing ║
╚══════════════════════════════════════════════════╝
DATA FLOWS IDENTIFIED:
User Registration → Database (EU) → Analytics (US) → Email Provider (US)
CONSENT GAPS:
🔴 Analytics tracking: No explicit consent banner
🔴 Email marketing: Opt-out only (requires opt-in)
🟡 Cookie policy: Missing granular control
ACTION ITEMS:
□ Implement consent management platform (est: 2 weeks)
□ Add cookie consent banner with granular controls (est: 3 days)
□ Update privacy policy with Article 13/14 requirements (est: 1 week)
□ Establish Data Processing Agreements with US vendors (est: 2 weeks)Implementation Example:
// GDPR-compliant consent implementation
class ConsentManager {
constructor() {
this.consent = this.loadConsent();
}
requestConsent(purposes = ['necessary', 'analytics', 'marketing']) {
return {
necessary: true, // Always granted
analytics: this.consent.analytics || false,
marketing: this.consent.marketing || false,
timestamp: new Date().toISOString()
};
}
grantConsent(purpose) {
this.consent[purpose] = true;
this.consent.timestamp = new Date().toISOString();
this.saveConsent();
}
revokeConsent(purpose) {
this.consent[purpose] = false;
this.saveConsent();
this.deleteData(purpose); // Article 17: Right to erasure
}
saveConsent() {
// Store in cookie with 13-month expiry (ePrivacy Directive)
document.cookie = `gdpr_consent=${JSON.stringify(this.consent)}; max-age=${60*60*24*395}; secure; samesite=strict`;
}
}/soc2-readiness - SOC 2 Type II Readiness Assessment
Gap analysis across all 5 Trust Service Criteria (TSC): Security, Availability, Processing Integrity, Confidentiality, Privacy.
Usage:
/soc2-readiness
/soc2-readiness --tsc security,availability
/soc2-readiness --generate-evidence-listExample Report:
SOC 2 TYPE II READINESS ASSESSMENT
Overall Readiness: 68% (Medium Risk)
┌────────────────────────────┬──────────┬──────────┬─────────────┐
│ Trust Service Criteria │ Score │ Gaps │ Risk Level │
├────────────────────────────┼──────────┼──────────┼─────────────┤
│ CC1: Control Environment │ 75% │ 3 │ 🟡 Medium │
│ CC2: Communication │ 80% │ 2 │ 🟢 Low │
│ CC3: Risk Assessment │ 60% │ 5 │ 🟠 High │
│ CC4: Monitoring │ 70% │ 4 │ 🟡 Medium │
│ CC5: Control Activities │ 65% │ 6 │ 🟠 High │
│ CC6: Logical Access │ 55% │ 8 │ 🔴 Critical│
│ CC7: System Operations │ 72% │ 3 │ 🟡 Medium │
└────────────────────────────┴──────────┴──────────┴─────────────┘
CRITICAL GAPS (CC6: Logical Access):
🔴 No MFA enforcement for administrative accounts
🔴 Password policy does not meet complexity requirements
🔴 No formal access review process (90-day requirement)
🔴 Service accounts share credentials
REMEDIATION ROADMAP (12 weeks):
Week 1-2: Implement MFA (Okta/Auth0)
Week 3-4: Deploy password manager + rotate service accounts
Week 5-6: Establish quarterly access review process
Week 7-8: Implement SIEM for security monitoring
Week 9-10: Conduct tabletop exercise for incident response
Week 11-12: Evidence collection + documentationMore from reason-machines
Use this skill in a project
Open any RiverX project, search the Skills panel for reason-machines/security-skills/sparkfinderoven-security-compliance-skills, and install it in one click.
