security-expert
Infrastructure security covering secrets, access control, and environment hardening. Use when configuring access control, SSH, or API keys, reviewing infrastructure for security posture, before committing code that touches secrets or credentials, or setting up new servers or services.
- License 许可
- MIT
- 所属仓库
- muratovv/ai-hats
- 最近更新
- 2026-11-05
- Stars
- ★ 3
- Forks
- 1
01 前言 Front Matter
- name
- security-expert
- license
- MIT
- description
- Infrastructure security covering secrets, access control, and environment hardening. Use when configuring access control, SSH, or API keys, reviewing infrastructure for security posture, before committing code that touches secrets or credentials, or setting up new servers or services.
03 SKILL.md 正文
Infrastructure Security Expert
Maintain zero-trust environment and protect production data.
When to Use
Infrastructure hardening — secrets, access control, SSH, env, server setup. Two siblings own adjacent surfaces: the trust model of an AI agent that can act on infra (where agent output meets privileged execution) is trust-boundary-mapping, and security review of application code is a lens of domain-reviewer. This skill is the infra/credential layer, not the agent design or the code diff.
1. Secret Management
- Scanning: Before any commit, search for leaked keys/passwords/tokens.
- Vaulting: All credentials in Ansible/Tofu must be encrypted (
ansible-vault,sensitivevariables). - Rotation: If a secret is leaked, immediately rotate it and notify the user.
2. Access Control
- Least Privilege: Configure SSH and API access with minimum necessary permissions.
- Audit: Regularly verify who has access to infrastructure nodes and gateways.
3. Environment Protection
- Templates: Use
.env.exampletemplates. Never commit actual.envfiles. - Hardening: Follow CIS benchmarks when configuring servers via Ansible.
Anti-Patterns
- Committing secrets "temporarily" — they're in git history forever
- Broad permissions for convenience — least privilege always
- Security as afterthought — integrate from the start, not as a final check
04 同仓库更多 Skills
tool-evaluation-protocol
Time-bounded protocol for evaluating new tools, libraries, or methodologies before adoption. Use when evaluating a candidate dependency for the project, researching a methodology (e.g. ML/LLM frameworks, testing approaches), or following up on a hype-driven recommendation.
systematic-debugging
4-phase bug-fix protocol (evidence, pattern, hypothesis, verify). Use when investigating any error, failure, or unexpected behavior, handling bug reports from users or monitoring, or diagnosing test failures with non-obvious causes.
skill-template
Canonical template and validation guide for ai-hats skills. Use when creating a new skill, reviewing an existing one for structural compliance, or deciding which pattern fits a new behavior.
skill-optimization
Audit and refactor library components to eliminate redundancy and staleness. Use during periodic library maintenance, after adding multiple new skills or rules, when a role's token budget is too high, or after retrospectives identify component issues.
silent-fallback-gate
PreToolUse hook — refuses an Edit or Write that adds an inert broad except. Use when a Python edit was blocked for a silent fallback.
retro-to-framework
Convert an observation about agent behavior — from a retrospective or from a single incident — into a framework-level change (hook, rule, skill, skill update). Use after a retrospective identifies problems that are not project-specific, after an incident where an agent misapplied a component it had read, when CLAUDE.md band-aids accumulate (more than 3 per-project rules that could be generic), or when the same problem recurs across multiple projects.