security-audit
Skill1 starsChanged 7 months agoMITView on GitHub
When the user asks for a security audit or security check of the IronClaw deployment, perform the following checks and report findings with severity levels (CRITICAL, WARNING, INFO). Print a summary table: SECURITY: Never print, echo, or include actual secret values (API keys, tokens, encryption keys, passwords) in the audit output. Only report whether they are set or not.
- Reads credentials
192 other projects use a version of this.
Adopted by
Most recently taken up by
- danbooru/danboorutheir own version, first seen Nov 16, 2026
- justinisaiah/claude-skillstheir own version, first seen Nov 16, 2026
- narumiruna/skillstheir own version, first seen Nov 15, 2026
- runkids/my-skillstheir own version, first seen Nov 15, 2026
- swap-cameroon/kuro-antigravity-configtheir own version, first seen Nov 15, 2026
- XavierEr/appsec-agent-skillstheir own version, first seen Nov 15, 2026
Used with
Projects with it also use create-stories, story-done and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
lilangMaxSkillcreate-stories
Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.
Also in 11 projects that use this
lilangMaxSkillstory-done
End-of-story completion review. Reads the story file, verifies each acceptance criterion against the implementation, checks for GDD/ADR deviations, prompts code review, updates story status to Complete, and surfaces the next ready story from the sprint.
Also in 11 projects that use this
nicepkgSkillcommunity-led-growth
Expert in community-led growth (CLG) - leveraging user communities to drive acquisition, retention, and expansion. Covers building developer communities, user groups, ambassador programs, and turning customers into advocates. Knows the difference between community as a feature vs community as a growth engine, and how to measure community ROI. Use when "community-led, CLG, ambassador program, champion program, user community, developer community, word of mouth, user group, " mentioned.
Also in 5 projects that use this
nicepkgSkillph-community-outreach
Engage Reddit, Indie Hackers, Hacker News and other communities for Product Hunt launches. Use this skill to identify relevant communities, craft appropriate posts, and drive cross-platform engagement without appearing spammy.
Also in 5 projects that use this
- +7 more from lilangMax
- +1 more from nicepkg
Other versions192 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 192
- ruvnet/claude-flow★ 80ksame name
- ruvnet/ruflo★ 79ksame name
- PostHog/posthog★ 41ksame name
- Donchitos/Claude-Code-Game-Studios★ 39ksame name
- cloudflare/security-audit-skill★ 18ksame name
- rommapp/romm★ 14ksame name
- kubeshark/kubeshark★ 12ksame name
- maximhq/bifrost★ 9.6ksame name
- mono/SkiaSharp★ 5.6ksame name
- MaxMiksa/Auto-Company★ 3.2ksame name
182 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- add-agentSkill
- add-remote-accessSkill
- add-telegramSkill
- configureSkill
- resetSkill
- setupSkill
- startSkill
- stopSkill
- switch-agentSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 174 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 3
When the user asks for a security audit or security check of the IronClaw deployment, perform the following checks and report findings with …
“Common” is measured: kept by at least 6 in 10 of the 174 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Security Audit Skill
When the user asks for a security audit or security check of the IronClaw deployment, perform the following checks and report findings with severity levels (CRITICAL, WARNING, INFO).
Checks to perform
- Encryption key — Check if
IRONCLAW_ENCRYPTION_KEYis set (exists) in the environment. IMPORTANT: Do NOT print or read the actual value — only check for existence. Use thefile_readtool to check if.envcontains a line starting withIRONCLAW_ENCRYPTION_KEY=(without revealing the value). If not set, report as CRITICAL: credentials at rest are unencrypted. - Mount allowlist — Use
file_readto check if~/.config/ironclaw/mount-allowlist.jsonexists. If it exists, verify it has a validallowedarray and adeniedarray. If missing, report as WARNING: sandbox mount permissions are unconfigured (no extra mounts allowed, but no custom deny rules either). - Gateway token — Check if
.envcontains a line starting withGATEWAY_WS_TOKEN=(without revealing the value). If not set, report as CRITICAL: gateway WebSocket connections are unauthenticated. - Environment file — Use
file_readto read the.envfile. Check that it exists and that secret values (API keys, tokens, passwords) are not empty or placeholder values. Do NOT include the actual secret values in your output. Report as WARNING if any required secrets appear to be missing or placeholder. If.envdoes not exist, report as INFO. - Docker sandbox — Use
bashto rundocker info(thedockercommand is not in the bash allowlist, so report if you cannot check). Check if the sandbox image is available. Report as WARNING if Docker is not running or the image is missing.
Output format
Print a summary table:
IronClaw Security Audit
========================
[CRITICAL] Encryption key not set — credentials stored unencrypted
[OK] Mount allowlist configured
[WARNING] Gateway token not set
[INFO] No .env file found
[OK] Docker running, sandbox image available
Summary: 1 critical, 1 warning, 1 infoSECURITY: Never print, echo, or include actual secret values (API keys, tokens, encryption keys, passwords) in the audit output. Only report whether they are set or not.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

