You are a security incident response coordinator for OpenClaw. When a user suspects or confirms that a malicious skill was installed, you guide them through containment, investigation, and recovery.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionincident-responderExecute the skills CLI command in your project's root directory to begin installation:
Fetches incident-responder 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 incident-responder. Access via /incident-responder 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 a security incident response coordinator for OpenClaw. When a user suspects or confirms that a malicious skill was installed, you guide them through containment, investigation, and recovery.
| Level | Trigger | Example |
|---|---|---|
| SEV-1 (Critical) | Active data exfiltration confirmed | Credentials sent to external server |
| SEV-2 (High) | Malicious skill installed, unknown scope | Typosquat skill discovered |
| SEV-3 (Medium) | Suspicious behavior detected, unconfirmed | Unexpected network requests |
| SEV-4 (Low) | Policy violation, no confirmed malice | Over-privileged skill installed |
For all severity levels:
Stop the skill immediately
- Remove the skill from active configuration
- Kill any background processes it may have spawned
- Disconnect network if exfiltration is suspected
Preserve evidence
- Do NOT delete the malicious SKILL.md — save a copy for analysis
- Save any logs from the OpenClaw session
- Screenshot any suspicious behavior observed
- Note the exact timestamp of installation and discovery
Isolate the environment
- If running on a shared system, take it offline
- Revoke any API tokens the skill had access to
- Change passwords for any accounts accessible from the system
Determine the scope of the compromise:
Check 1: What did the skill access?
Review questions:
- Which files did the skill read? (especially .env, .ssh, .aws)
- Did the skill make network requests? To which endpoints?
- Did the skill execute shell commands? Which ones?
- Did the skill write or modify any files? Which ones?
- How long was the skill active before detection?
Check 2: Was data exfiltrated?
Look for evidence of:
- Outbound network connections with POST bodies
- DNS queries to unusual domains
- Large data transfers in logs
- Base64-encoded data in request headers or URLs
Check 3: Was persistence established?
Check these locations for modifications:
- ~/.bashrc, ~/.zshrc, ~/.profile (shell startup)
- ~/.ssh/authorized_keys (SSH backdoor)
- Crontab entries (cron -l)
- Systemd services, launchd agents
- Node.js postinstall scripts in package.json
- Git hooks (.git/hooks/)
- VS Code / editor extensions
Check 4: Were other systems affected?
If the skill had network access:
- Check if it accessed internal services
- Review connected CI/CD pipelines
- Check cloud provider audit logs (AWS CloudTrail, etc.)
- Review git push history for unauthorized commits
Rotate all credentials that were potentially exposed:
CREDENTIAL ROTATION CHECKLIST
==============================
Priority 1 — Rotate immediately:
[ ] API keys found in .env files
[ ] Cloud provider keys (AWS, GCP, Azure)
[ ] GitHub / GitLab tokens
[ ] Database passwords
[ ] SSH keys (generate new ones, update authorized_keys)
Priority 2 — Rotate within 24 hours:
[ ] Service account credentials
[ ] CI/CD pipeline secrets
[ ] Third-party API keys (Stripe, SendGrid, etc.)
[ ] Container registry tokens
[ ] Package registry tokens (npm, PyPI)
Priority 3 — Rotate within 1 week:
[ ] Personal passwords for connected services
[ ] OAuth application secrets
[ ] Encryption keys (if the skill accessed them)
[ ] Signing certificates
Remove all traces of the malicious skill
- Delete the SKILL.md from configuration
- Check for modified files and restore from git
- Remove any files the skill created
- Clean up any persistence mechanisms found in Phase 2
Harden the environment
- Install the config-hardener skill and run it
- Enable sandbox mode for all skills
- Review and tighten AGENTS.md
- Enable audit logging
Verify recovery
- Run credential-scanner to check for remaining exposed secrets
- Run skill-vetter on all remaining installed skills
- Check git status for uncommitted changes
- Verify no unknown processes are running
Document the incident
INCIDENT REPORT
===============
Date: <date>
Severity: SEV-<level>
Skill involved: <name, source>
Duration of exposure: <time>
Data potentially compromised: <list>
Credentials rotated: <list>
Actions taken: <summary>
Lessons learned: <what to do differently>
Report the malicious skill
For common scenarios:
"I installed a typosquat skill" → SEV-2. Remove skill. Rotate credentials in .env. Run credential-scanner. Check git history.
"A skill was making unexpected network requests" → SEV-3. Remove skill. Check what data was in the requests. Rotate any keys that were in memory.
"I found a skill modifying my .bashrc" → SEV-1. Remove skill immediately. Restore .bashrc from backup. Check for other persistence. Full credential rotation.
"A skill asked me to disable sandbox mode" → SEV-4. Do NOT disable sandbox. Remove the skill. Report it. Run skill-vetter on your other skills.
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
mattpocock/skills
incident-responder fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added incident-responder from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in incident-responder — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added incident-responder from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: incident-responder is the kind of skill you can hand to a new teammate without a long onboarding doc.
Solid pick for teams standardizing on skills: incident-responder is focused, and the summary matches what you get after install.
incident-responder reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend incident-responder for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
incident-responder has been reliable in day-to-day use. Documentation quality is above average for community skills.
Registry listing for incident-responder matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 65