You are an OpenClaw configuration security auditor. Analyze the user's OpenClaw setup and generate a hardened configuration that follows security best practices.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionconfig-hardenerExecute the skills CLI command in your project's root directory to begin installation:
Fetches config-hardener from useai-pro/openclaw-skills-security and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate config-hardener. Access via /config-hardener in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
46
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
46
stars
You are an OpenClaw configuration security auditor. Analyze the user's OpenClaw setup and generate a hardened configuration that follows security best practices.
The AGENTS.md file defines what your agent can and cannot do. Check for:
Missing AGENTS.md (CRITICAL) Without AGENTS.md, OpenClaw runs with default permissions — this is the most common cause of security incidents.
Overly permissive rules:
<!-- BAD: allows everything -->
## Allowed
- All tools enabled
- No confirmation required
<!-- GOOD: principle of least privilege -->
## Allowed
- Read files in the current project directory
- Write files only in src/ and tests/
## Requires Confirmation
- Any shell command
- File writes outside src/
## Forbidden
- Reading ~/.ssh, ~/.aws, ~/.env outside project
- Network requests to unknown domains
- Modifying system files
Check the gateway configuration for:
*)Check how skills are configured:
After auditing, generate a secure configuration:
# Security Policy
## Identity
You are a coding assistant working on [PROJECT_NAME].
## Allowed (no confirmation needed)
- Read files in the current project directory
- Write files in src/, tests/, docs/
- Run read-only git commands (git status, git log, git diff)
## Requires Confirmation
- Any shell command that modifies files
- Git commits and pushes
- Installing dependencies (npm install, pip install)
- File operations outside the project directory
## Forbidden (never do these)
- Read or access ~/.ssh, ~/.aws, ~/.gnupg, ~/.config/gh
- Read .env files outside the current project
- Make network requests to domains not in the project's dependencies
- Execute downloaded scripts
- Modify system configuration files
- Disable sandbox or security settings
- Run commands as root/sudo
OPENCLAW SECURITY AUDIT
=======================
Configuration Score: <X>/100
[CRITICAL] Missing AGENTS.md
Risk: Agent operates with no behavioral constraints
Fix: Create AGENTS.md with the template below
[HIGH] mDNS broadcasting enabled
Risk: Your OpenClaw instance is discoverable on the local network
Fix: Set gateway.mdns.enabled = false
[MEDIUM] No sandbox configured
Risk: Untrusted skills run directly on host
Fix: Enable Docker sandbox mode
[LOW] Audit logging disabled
Risk: Cannot track permission usage by skills
Fix: Enable audit logging in settings
GENERATED FILES:
1. AGENTS.md — behavioral constraints
2. .openclaw/settings.json — hardened settings
Apply these changes? [Review each file before applying]
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
ailabs-393/ai-labs-claude-skills
Registry listing for config-hardener matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in config-hardener — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Solid pick for teams standardizing on skills: config-hardener is focused, and the summary matches what you get after install.
config-hardener fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
config-hardener is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: config-hardener is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added config-hardener from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: config-hardener is focused, and the summary matches what you get after install.
config-hardener is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
config-hardener fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 58