wicked-garden-platform-audit
Skill9 starsChanged 7 months agoMITView on GitHub
Audit evidence collection and trail verification. Gathers artifacts, validates controls, generates audit reports, and maintains compliance documentation.
- Installs packages
In this repository142 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- plugin-json-schemaSkill
- readme-style-guideSkill
- releaseSkill
- scaffoldSkill
- wicked-garden-agentic-agentic-patternsSkill
- wicked-garden-agentic-architectSkill
- wicked-garden-agentic-context-engineeringSkill
- wicked-garden-agentic-frameworksSkill
- wicked-garden-agentic-performance-analystSkill
- wicked-garden-agentic-review-methodologySkill
- wicked-garden-agentic-safety-reviewerSkill
- wicked-garden-agenticSkill
- wicked-garden-agentic-trust-and-safetySkill
- wicked-garden-appsSkill
- wicked-garden-archetypeSkill
- wicked-garden-build-guideSkill
- wicked-garden-classifySkill
- wicked-garden-coreSkill
- wicked-garden-data-engineerSkill
- wicked-garden-dataSkill
- wicked-garden-deliberateSkill
- wicked-garden-demoSkill
- wicked-garden-domain-coverageSkill
- wicked-garden-domain-extractorSkill
- wicked-garden-domain-modelerSkill
- wicked-garden-domainSkill
- wicked-garden-draftSkill
- wicked-garden-editor-scaffoldSkill
- wicked-garden-engineering-api-documentarianSkill
- wicked-garden-engineering-architectureSkill
- wicked-garden-engineering-backendSkill
- wicked-garden-engineering-debuggingSkill
- wicked-garden-engineering-docsSkill
- wicked-garden-engineering-frontendSkill
- wicked-garden-engineering-integrationSkill
- wicked-garden-engineering-large-scale-migrationSkill
- wicked-garden-engineering-migration-engineerSkill
- wicked-garden-engineering-patchSkill
- wicked-garden-engineeringSkill
- wicked-garden-engineering-solution-architectSkill
- wicked-garden-engineering-system-designSkill
- wicked-garden-engineering-unit-test-qualitySkill
- wicked-garden-governed-workerSkill
- wicked-garden-groundSkill
- wicked-garden-jam-brainstorm-facilitatorSkill
- wicked-garden-jam-councilSkill
- wicked-garden-jamSkill
- wicked-garden-learnSkill
- wicked-garden-mcp-scaffoldSkill
- wicked-garden-mcpSkill
- wicked-garden-mem-captureSkill
- wicked-garden-mem-ingestSkill
- wicked-garden-memSkill
- wicked-garden-personaSkill
- wicked-garden-platform-compliance-officerSkill
- wicked-garden-platform-complianceSkill
- wicked-garden-platform-errorsSkill
- wicked-garden-platform-gate-benchmark-rebaselineSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 26
If none of these is available, or Python 3 is missing, skip the script-backed step, say so, and follow the manual alternative where one is …
- Very specific: line 43
Read refs/audit.md (relative to this skill's base directory) — full collection rubric, control-testing checklist, SOC2/HIPAA control …
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Audit Skill
Collect evidence and verify audit trails for compliance.
Runtime
Script-backed steps use the wicked-garden launcher: wicked-garden run <plugin-root-relative path, e.g. scripts/…> [args]. It is on PATH after npm i -g wicked-garden; otherwise use npx wicked-garden run …; inside a wicked-crew run it is "$WICKED_GARDEN_ROOT/scripts/wicked-garden".
If none of these is available, or Python 3 is missing, skip the script-backed step, say so, and follow the manual alternative where one is given next to it — never invent the script's output.
Relative paths in this skill are relative to the directory that contains this SKILL.md.
When to Use
- Preparing for external audit
- Collecting evidence for compliance certification
- Verifying audit trail completeness
- Generating audit reports
- User says "audit", "evidence", "audit trail", "control testing"
Run it inline (no dispatch)
Invoked as <framework> [control_id|all]:
- Parse args:
<framework> [control_id](framework =soc2|hipaa|gdpr|pci; control_id orall). - Read
refs/audit.md(relative to this skill's base directory) — full collection rubric, control-testing checklist, SOC2/HIPAA control matrix, gap analysis, bus emit, and output format. - For framework-specific checklists:
Read
refs/checklists-soc2-hipaa.mdorrefs/checklists-gdpr-pci-evidence.md. For evidence scripts and organization:refs/checklists-evidence-operations.md. - Apply the rubric directly: collect evidence via code search, verify each control, document Pass/Partial/Fail with file:line refs, then emit the bus event and produce the audit report.
Audit Process
1. Define Scope
Identify audit targets:
- Code components
- Data flows
- Access controls
- Infrastructure
- Processes
2. Collect Evidence
Code Evidence:
- Access control implementation
- Encryption usage
- Input validation
- Error handling
- Logging statements
Configuration Evidence:
- TLS/SSL settings
- Database encryption
- Key management
- Network policies
- IAM roles
Documentation Evidence:
- Architecture diagrams
- Data flow diagrams
- Security policies
- Incident response plans
Operational Evidence:
- Access logs
- Audit logs
- Security events
- Change logs
See refs/checklists-soc2-hipaa.md, refs/checklists-gdpr-pci-evidence.md, and refs/checklists-evidence-operations.md for comprehensive evidence checklists.
3. Verify Controls
Test each control:
# Check encryption
grep -r "encrypt\|cipher\|AES\|TLS" {target}
# Check access controls
grep -r "authorize\|authenticate\|require.*auth" {target}
# Check audit logging
grep -r "log\|audit\|event" {target}See refs/frameworks-soc2-hipaa.md and refs/frameworks-gdpr-pci.md for framework-specific control testing procedures.
4. Document Gaps
Identify:
- Controls without evidence
- Incomplete audit trails
- Missing documentation
- Configuration gaps
5. Generate Report
Create report with:
- Controls tested
- Evidence collected
- Gaps identified
- Recommendations
- Risk assessment
Evidence Types
| Type | Description | Examples |
| Design | Architecture | Diagrams, specs, policies |
| Implementation | Code | Functions, configs, tests |
| Operational | Runtime | Logs, metrics, incidents |
| Process | Procedural | Approvals, reviews, training |
Integration
With the harness's task list
Attach audit evidence by appending ## Audit Evidence: {control_id} — Evidence file: {evidence_path} to the task description (reference file paths checked into the repo) — the harness's task list where it has one (the wicked-garden-workflow skill's refs/integration.md carries the field list and the harness-specific Hand-off), else your working notes.
With the knowledge layer
Hand-off — open the wicked-garden-mem skill and run its recall action with audit logging encryption as the query (FTS5 over indexed code); on Claude Code this is the Skill tool, on any other seat open the named skill from your catalog and carry it out inline, then continue here.
Output Format
## Audit Report: {Framework}
**Status**: {READY|NEEDS WORK|NOT READY}
**Controls Tested**: {count} | **Gaps**: {count}
### Controls Tested
| ID | Status | Evidence |
|----|--------|----------|
| CC6.1 | PASS | auth.py:15 |
| CC7.2 | FAIL | Missing |
### Evidence
- Design: docs/arch.md
- Code: src/auth.py, src/crypto.py
- Operational: /var/log/audit.log
### Critical Gaps (P0)
1. Missing admin audit trail
2. No TLS for PII endpoints
### Recommendations
1. Fix P0 gaps before certification
2. Schedule follow-up auditQuality Standards
Good audit evidence:
- Specific file/line references
- Clear control mapping
- Complete artifact trails
- Risk-prioritized gaps
Bad audit evidence:
- Generic statements
- No source references
- Missing artifacts
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

