BytesAgain is a curated directory of 60,000+ AI agent skills from ClawHub, GitHub, LobeHub, and Dify. Search skills by keyword in 7 languages, browse by role (developer, creator, trader, marketer) or by use case.

How do I find AI skills on BytesAgain?

Use the search bar on BytesAgain.com to search by keyword in 7 languages. You can also browse by role (developer, creator, trader, marketer) or by use case. Each skill shows install instructions for Claude, Cursor, OpenClaw, Continue, and more.

Yes, BytesAgain is completely free. No registration required for searching skills. The MCP API is also free with rate limits.

Does BytesAgain have an API for AI agents?

Yes! BytesAgain provides a free MCP SSE endpoint at /api/mcp/sse for AI agents, plus a REST API at /api/mcp?action=search&q= . No authentication needed.

Can I request a new AI skill on BytesAgain?

Yes! Visit the Requests page on BytesAgain.com to submit a skill request. Your request will be visible to the community and notified to the site admin.

🦀 ClawHub✦ BytesAgain

Compliance

by @bytesagain-lab

Track compliance requirements and generate audit trail reports. Use when auditing controls, checking policies, generating audit trails.

Versionv2.0.0

Downloads691

Installs2

Stars⭐ 1

#clawhub

View on ClawHub →

TERMINAL

clawhub install compliance

📖 About This Skill

name: "Compliance" description: "Track compliance requirements and generate audit trail reports. Use when auditing controls, checking policies, generating audit trails." version: "2.0.0" author: "BytesAgain" homepage: https://bytesagain.com source: https://github.com/bytesagain/ai-skills tags: ["encryption", "protection", "compliance", "security", "privacy"]

Compliance

Security toolkit for logging, tracking, and exporting compliance-related activities. Each command records timestamped entries to its own log file. Call without arguments to view recent entries; call with arguments to record a new entry.

Commands

| Command | What it does | |---------|-------------| | compliance generate | Record a generate entry (no args = show recent) | | compliance check-strength | Record a check-strength entry (no args = show recent) | | compliance rotate | Record a rotate entry (no args = show recent) | | compliance audit | Record an audit entry (no args = show recent) | | compliance store | Record a store entry (no args = show recent) | | compliance retrieve | Record a retrieve entry (no args = show recent) | | compliance expire | Record an expire entry (no args = show recent) | | compliance policy | Record a policy entry (no args = show recent) | | compliance report | Record a report entry (no args = show recent) | | compliance hash | Record a hash entry (no args = show recent) | | compliance verify | Record a verify entry (no args = show recent) | | compliance revoke | Record a revoke entry (no args = show recent) | | compliance stats | Show summary statistics across all log files | | compliance export | Export all data to json, csv, or txt format | | compliance search | Search all log entries for a keyword | | compliance recent | Show the 20 most recent history entries | | compliance status | Health check — version, entry count, disk usage, last activity | | compliance help | Show help message | | compliance version | Show version (v2.0.0) |

Data Storage

All data is stored locally in ~/.local/share/compliance/. Each command writes to its own .log file (e.g., audit.log, policy.log). A unified history.log tracks all activity with timestamps.

Requirements

Bash 4+

Standard Unix utilities (wc, du, tail, grep, date, sed)

When to Use

Logging compliance audit findings, policy checks, and security events with timestamps

Tracking credential rotations, revocations, and strength checks over time

Recording data store/retrieve operations for audit trail purposes

Searching historical compliance entries by keyword

Exporting compliance records to JSON, CSV, or plain text for regulatory reporting

Examples

# Record an audit finding
compliance audit "reviewed access controls for prod database — 3 issues found"
Log a credential rotation
compliance rotate "rotated API keys for payment gateway"
Record a policy update
compliance policy "updated data retention policy to 90 days"
Check password strength assessment
compliance check-strength "admin account meets complexity requirements"
Search all logs for "database"
compliance search database
Export compliance records to JSON
compliance export json
View overall stats
compliance stats

⚡ When to Use

Trigger	Action
- Tracking credential rotations, revocations, and strength checks over time
- Recording data store/retrieve operations for audit trail purposes
- Searching historical compliance entries by keyword
- Exporting compliance records to JSON, CSV, or plain text for regulatory reporting

💡 Examples

# Record an audit finding
compliance audit "reviewed access controls for prod database — 3 issues found"
Log a credential rotation
compliance rotate "rotated API keys for payment gateway"
Record a policy update
compliance policy "updated data retention policy to 90 days"
Check password strength assessment
compliance check-strength "admin account meets complexity requirements"
Search all logs for "database"
compliance search database
Export compliance records to JSON
compliance export json
View overall stats
compliance stats