| type | skill |
| name | security-snapshot |
| description | Generate a client-ready security hygiene snapshot for a prospect domain. Free lead magnet for consulting practices. Outputs a markdown report covering SSL/TLS grade, HTTP security headers, email authentication (SPF/DMARC), and server fingerprint leaks. Use when the user says /security-snapshot, /snapshot [domain], "run a security check on X", or "generate a security report for [company]". Do NOT use for penetration testing, internal infrastructure audits, or application-layer vulnerability assessment. This is a passive, unauthenticated scan for conversation-starter value, not a full audit. |
| argument-hint | <domain> [--company 'Display Name'] |
| tool_access | ["Bash","Read","Write"] |
| policy_constraints | [{"rule":"Only run passive, unauthenticated scans against the public-facing domain","exception_handling":"Refuse to run if the request implies authenticated probing or penetration testing"},{"rule":"Never store credentials or PII in the report or output directory","exception_handling":"Strip any unexpected credential-shaped strings before writing the markdown file"},{"rule":"Cap external API usage to the documented endpoints (SSL Labs, public DNS lookups, headers fetch)","exception_handling":"Abort and report partial results if a required endpoint is unavailable rather than fall back to an undocumented service"}] |
| required_inputs | [{"name":"domain","type":"string","required":true,"description":"The public domain to scan (e.g. example.com). Must resolve via public DNS."},{"name":"company","type":"string","required":false,"description":"Display name for the company, used in the report header. Defaults to the domain."}] |
| output_shape | {"format":"markdown-file","fields":{"report_path":"absolute path to the saved markdown report","sections":["ssl_tls_grade","http_security_headers","email_authentication","server_fingerprint"],"summary_grade":"overall hygiene grade (A through F) printed to stdout"}} |
When the user types /security-snapshot [domain] or asks for a security check on a prospect, run the security snapshot generator and deliver a client-ready report.
Why this skill exists
Prospects rarely have budget for a full security audit upfront, but they will read a free one-page report that exposes real issues with their public-facing setup. This skill generates that report in under 3 minutes and opens the door for a paid follow-up on security work, AI implementation, or adjacent consulting.
Command
python3 "$HOME/.claude/skills/ai-brain-starter/scripts/security-snapshot.py" <domain> --company "<Display Name>"
The script ships with the starter repo. Output goes to $SNAPSHOTS_DIR if set, otherwise $VAULT_ROOT/security-snapshots/ if VAULT_ROOT is set, otherwise a security-snapshots/ folder next to wherever you run the command from. It takes 60-180 seconds because SSL Labs is slow. The script prints the saved report path to stdout and progress to stderr.
Workflow
- Get the domain. If the user only gave a company name, ask for the domain (e.g., "Is it acme.com or acmecorp.com?"). Do not guess.
- Run the script. Use Bash with a long timeout (180000ms) because SSL Labs polling is slow.
- Read the output. The script saves to
$SNAPSHOTS_DIR/<domain>/<YYYY-MM-DD>-snapshot.md (defaults to $VAULT_ROOT/security-snapshots/ when SNAPSHOTS_DIR is unset). Read the file before summarizing.
- Summarize for the user. Do NOT dump the full report into chat. Give:
- Top 3 findings by severity with one-line reasons
- SSL grade
- Whether SPF + DMARC are both present
- Path to the saved report
- Offer the follow-up. If there are high or critical findings, offer to draft the outreach email that pairs with the report. Match the user's own outreach voice, do not invent a new one.
Voice rules for the delivered report
The script produces the base report. If the user asks you to customize or rewrite any section before sending, follow the generic voice rules in templates/rules/voice-firewall.md:
- No em dashes. Use commas, colons, periods, or parentheses.
- No exclamation marks. Anywhere.
- No hype language ("leverage synergies", "game-changing"). Facts plus plain severity.
