Back to skills
SKILL.md
Tinman
ASecuritySecurity auditing and hardening for OpenClaw and system infrastructure.
- 57 stars
- 0 votes
- 0 copies
- 1 view
- Added October 17, 2026
Security analysis
100/100npx -y skills add diegosouzapw/awesome-omni-skill --skill tinman --agent claude-codeAre you the author of Tinman?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/diegosouzapw-tinman)---
name: tinman
version: 1.0.0
description: Security auditing and hardening for OpenClaw and system infrastructure.
metadata:
openclaw:
emoji: ๐ก๏ธ
category: security
---
# Tinman
Security auditing and hardening for OpenClaw and system infrastructure.
## Security Levels
| Level | Description | Response |
|-------|-------------|----------|
| **S0** | Info | Log only |
| **S1** | Low | Notify user |
| **S2** | Medium | Alert + recommend fix |
| **S3** | High | Immediate action required |
| **S4** | Critical | Stop + notify immediately |
## Checks
### OpenClaw Security
| Check | Risk | Action |
|-------|------|--------|
| Credentials in git | S3 | Add to .gitignore, rotate |
| Token expiration | S2 | Refresh tokens |
| Exposed secrets | S4 | Rotate immediately |
| Uncommitted changes | S1 | Review + commit |
### System Security
| Check | Risk | Action |
|-------|------|--------|
| SSH password auth | S2 | Disable, use keys only |
| Open ports | S1 | Review with `ss -tlnp` |
| Unattended upgrades | S2 | Enable automatic updates |
| Firewall status | S2 | Verify ufw/iptables |
## Workflow
### 1. Security Scan
```bash
# Check for credentials in git
git log --all --full-history -- .credentials/
# Check file permissions
ls -la ~/.credentials/
# Check SSH config
cat /etc/ssh/sshd_config | grep -E "PasswordAuthentication|PermitRootLogin"
```
### 2. Report Generation
```markdown
## Security Audit Report
**Date:** 2026-02-20
**Scope:** OpenClaw + System
### Findings
| Level | Issue | Recommendation |
|-------|-------|----------------|
| S2 | Token expires in 3 days | Refresh Google OAuth |
### Actions Taken
- [x] Verified .credentials/ permissions (600)
- [ ] Refresh expiring tokens
```
### 3. Automated Monitoring
```json
{
"name": "daily-security-check",
"schedule": {"kind": "cron", "expr": "0 6 * * *"},
"payload": {
"kind": "agentTurn",
"message": "Run tinman security scan. Check: credential perms, token expiration, git secrets. Report S2+ issues."
},
"sessionTarget": "isolated",
"notify": true
}
```
## Best Practices
1. **Credential hygiene** โ 600 permissions, never in git
2. **Token rotation** โ Before expiration
3. **Regular audits** โ Weekly automated scans
4. **Principle of least privilege** โ Minimal permissions
5. **Audit logging** โ Track all changes
## Emergency Response
If S4 (Critical) detected:
1. **Stop** โ Halt related operations
2. **Assess** โ Scope of exposure
3. **Rotate** โ Change all affected credentials
4. **Review** โ How did it happen
5. **Prevent** โ Update processes
Attribution
Comments
Loading commentsโฆ
Newsletter
Get the weekly list of safe new skills, and the ones we pulled.