adaptive-enforcement-lab/enforce
plugins/enforce/skills/enforce/SKILL.md
Make security mandatory through automation. Branch protection, pre-commit hooks, status checks, policy-as-code, and SLSA provenance for SOC 2 compliance.
tools
Updated Mar 27, 2026
$ install --global
skillsauthnpx skillsauth add adaptive-enforcement-lab/claude-skills enforceInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Mar 29, 2026, 8:39 AM36.7s7 files scanned
SKILL.md
- name:
- enforce
- description:
- >-
Enforce
When to Use This Skill
This section covers the enforcement mechanisms that make security policies mandatory, auditable, and impossible to ignore.
These controls pass SOC 2, ISO 27001, and PCI-DSS audits by shifting security left and making compliance automatic.
Implementation
See Implementation Roadmap for phased rollout:
- Phase 1: Branch protection (1 week)
- Phase 2: Status checks (2 weeks)
- Phase 3: Pre-commit hooks (1 week)
- Phase 4: Policy-as-code (4 weeks)
- Phase 5: SLSA provenance (2 weeks)
Total timeline: 10 weeks for complete enforcement stack.
Comparison
Understanding the distinction:
-
Secure (see Secure): Find and fix security issues
- Vulnerability scanners that identify CVEs
- SBOM generators that document dependencies
- Security tools that discover weaknesses
-
Enforce (this section): Make security mandatory through automation
- Branch protection that requires reviews
- Pre-commit hooks that block violations
- Status checks that prevent merges
- Policy-as-code that rejects non-compliant resources
- SLSA provenance that attests build integrity
Litmus test: Can this be bypassed?
- If yes → Belongs in Enforce (make it mandatory)
- If no → Belongs in Secure (it's a finding/fix tool)
Examples
See examples.md for code examples.
Full Reference
See reference.md for complete documentation.
Related Patterns
- Secure
- Build
- Patterns
References
- Source Documentation
- AEL Enforce
Related Skills
adaptive-enforcement-lab/workload-identity-federation-implementation
documentation
VerifiedTrustedCommunity
Workload Identity Federation implementation guide. GKE setup, IAM bindings, ServiceAccount configuration, migration from service account keys, and troubleshooting patterns.
SKILL.mdUpdated Mar 27, 2026
adaptive-enforcement-lab/workflow-trigger-security
development
VerifiedTrustedCommunity
Secure GitHub Actions trigger patterns for pull requests, forks, and reusable workflows. Preventing privilege escalation and code injection through trigger misconfiguration.
SKILL.mdUpdated Mar 27, 2026
adaptive-enforcement-lab/third-party-action-risk-assessment
development
VerifiedTrustedCommunity
Structured framework for evaluating GitHub Actions security before adoption. Trust tiers, risk assessment checklist, and decision tree for action evaluation.
SKILL.mdUpdated Mar 27, 2026
adaptive-enforcement-lab/storing-credentials
testing
VerifiedTrustedCommunity
Securely store GitHub App credentials across different environments. GitHub Actions secrets, external CI, Kubernetes, and automated rotation patterns.
SKILL.mdUpdated Mar 27, 2026