security-audit

Identify and remediate security misconfigurations and exposed credentials in Clawdbot deployments.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/bobvarkey/diabetes-buddy --skill security-audit-bobvarkey
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-audit
Source: https://github.com/bobvarkey/diabetes-buddy/tree/main/skills/security-audit
Command: npx skills add https://github.com/bobvarkey/diabetes-buddy --skill security-audit-bobvarkey

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Comprehensive security auditing for Clawdbot deployments, scanning for exposed credentials, open ports, weak configurations, and vulnerabilities, with an auto-fix mode to remediate issues.

Core Features & Use Cases

  • Credential scanning for API keys, tokens, and hardcoded secrets
  • Port discovery and configuration checks to minimize exposure
  • Docker hygiene and runtime security validations
  • Auto-fix workflow to apply secure defaults and generate reports
  • JSON-friendly reporting for integration and automation

Quick Start

Run the audit script to perform a security assessment of your Clawdbot setup.

Frequently Asked Questions about security-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scan my Docker deployment for exposed credentials and secrets?

Run an automated security audit to scan your Docker deployment for exposed credentials and secrets. This process inspects code, configuration, and runtime environments to identify hardcoded API keys and tokens, then optionally applies secure defaults to remediate them.

What is the best way to automate security misconfiguration checks for Clawdbot?

The best way to automate security misconfiguration checks for Clawdbot is using a scripted audit workflow that validates port configurations and Docker hygiene. It generates reproducible audit reports with optional JSON output for seamless integration into your automation pipeline.

Can I auto-fix weak configurations and open ports found during a security audit?

Yes, you can auto-fix weak configurations and open ports found during a security audit using the auto-fix workflow. This mode applies secure defaults to minimize exposure across your code, configuration, and Docker environments while generating a report of the changes.

How do I get JSON output from a security audit for CI/CD integration?

You can get JSON output from a security audit for CI/CD integration by enabling the JSON-friendly reporting feature. This format structures the results of credential, port, config, and Docker checks for automated parsing and pipeline integration.

Does the security audit check Docker runtime environments or just configuration files?

The security audit checks both Docker runtime environments and configuration files. It performs Docker hygiene validations and runtime security checks alongside static configuration and credential scanning to provide comprehensive coverage.