Fetches secure-code-guardian from jeffallan/claude-skills and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/secure-code-guardian
Restart Cursor to activate secure-code-guardian. Access via /secure-code-guardian in your agent's command palette.
⚠
Security Notice
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.
Threat model — Identify attack surface and threats
Design — Plan security controls
Implement — Write secure code with defense in depth; see code examples below
Validate — Test security controls with explicit checkpoints (see below)
Document — Record security decisions
Validation Checkpoints
After each implementation step, verify:
Authentication: Test brute-force protection (lockout/rate limit triggers), session fixation resistance, token expiration, and invalid-credential error messages (must not leak user existence).
Authorization: Verify horizontal and vertical privilege escalation paths are blocked; test with tokens belonging to different roles/users.
Input handling: Confirm SQL injection payloads (' OR 1=1--) are rejected; confirm XSS payloads (<script>alert(1)</script>) are escaped or rejected.
Headers/CORS: Validate with a security scanner (e.g., curl -I, Mozilla Observatory) that security headers are present and CORS origin allowlist is correct.
Reference Guide
Load detailed guidance based on context:
Topic
Reference
Load When
OWASP
references/owasp-prevention.md
OWASP Top 10 patterns
Authentication
references/authentication.md
Password hashing, JWT
Input Validation
references/input-validation.md
Zod, SQL injection
XSS/CSRF
references/xss-csrf.md
XSS prevention, CSRF
Headers
references/security-headers.md
Helmet, rate limiting
Constraints
MUST DO
Hash passwords with bcrypt/argon2 (never MD5/SHA-1/unsalted hashes)
Use parameterized queries (never string-interpolated SQL)
// NEVER: `SELECT * FROM users WHERE email = '${email}'`// ALWAYS: use positional parametersimport{ Pool }from'pg';const pool =newPool();exportasyncfunctiongetUserByEmail(email:string){const{ rows }=await pool.query('SELECT id, email, role FROM users WHERE email = $1',[email]// value passed separately — never interpolated);return rows[0]??null;}
Input Validation with Zod
import{ z }from'zod';const LoginSchema = z.object({ email: z.string().email().max(254), password: z.string().min(8).max(128),});exportfunctionvalidateLoginInput(raw:unknown){const result = LoginSchema.safeParse(raw);if(!result.success){// Return generic error — never echo raw input backthrownewError('Invalid credentials format');}return result.data;}
JWT Validation
import jwt from'jsonwebtoken';constJWT_SECRET= process.env.JWT_SECRET!;// never hardcodeexportfunctionverifyToken(token:string): jwt.JwtPayload {// Throws if expired, tampered, or wrong algorithmconst payload = jwt.verify(token,JWT_SECRET,{ algorithms:['HS256'],// explicitly allowlist algorithm issuer:'your-app', audience:'your-app',});if(typeof payload ==='string')thrownewError('Invalid token payload');return payload;}
›Access to product documentation and roadmap tools (Jira, Notion, etc.)
›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
1Install product management skill
2Start with user story generation for known feature
3Progress to competitive analysis: research 2-3 competitors
4Use for roadmap prioritization: apply RICE/ICE scoring
5Draft stakeholder communications and refine based on feedback
6Build template library for recurring PM tasks
7Share effective prompts with product team
Common Pitfalls
⚠Not validating competitive research—verify facts before sharing
⚠Accepting user stories without involving engineering team
⚠Over-relying on frameworks without qualitative judgment
⚠Not customizing outputs to company culture and communication style
⚠Skipping stakeholder validation of generated requirements
Best Practices
✓ Do
+Validate research and competitive analysis with real data
+Collaborate with engineering when generating technical requirements
+Customize frameworks and templates to your company context
+Use skill for first drafts, refine with stakeholder input
+Document successful prompt patterns for PM tasks
+Combine AI efficiency with human judgment and intuition
✗ Don't
−Don't publish competitive analysis without fact-checking
−Don't finalize user stories without engineering review
−Don't make prioritization decisions solely on AI scoring
−Don't skip customer validation of generated requirements
−Don't ignore company-specific context and culture
💡 Pro Tips
★Provide context: company goals, constraints, customer feedback
★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
★Use skill for 70% generation + 30% customization to company needs
When to Use This
✓ 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.
Learning Path
1Basic: user stories, feature specs, status updates
