Provides control categorization by type (preventive, detective, corrective) and layer (network, application, data, endpoint, process), with templates for building threat-to-control mappings and calculating coverage gaps
Includes a standard control library with 15+ pre-built controls covering authentication, encryption, logging, access control, and availability, each mapped to
Confirm successful installation by checking the skill directory location:
.cursor/skills/threat-mitigation-mapping
Restart Cursor to activate threat-mitigation-mapping. Access via /threat-mitigation-mapping 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.
from dataclasses import dataclass, field
from enum import Enum
from typing import List, Dict, Optional, Set
from datetime import datetime
classControlType(Enum): PREVENTIVE ="preventive" DETECTIVE ="detective" CORRECTIVE ="corrective"classControlLayer(Enum): NETWORK ="network" APPLICATION ="application" DATA ="data" ENDPOINT ="endpoint" PROCESS ="process" PHYSICAL ="physical"classImplementationStatus(Enum): NOT_IMPLEMENTED ="not_implemented" PARTIAL ="partial" IMPLEMENTED ="implemented" VERIFIED ="verified"classEffectiveness(Enum): NONE =0 LOW =1 MEDIUM =2 HIGH =3 VERY_HIGH =4@dataclassclassSecurityControl:id:str name:str description:str control_type: ControlType
layer: ControlLayer
effectiveness: Effectiveness
implementation_cost:str# Low, Medium, High maintenance_cost:str status: ImplementationStatus = ImplementationStatus.NOT_IMPLEMENTED
mitigates_threats: List[str]= field(default_factory=list) dependencies: List[str]= field(default_factory=list) technologies: List[str]= field(default_factory=list) compliance_refs: List[str]= field(default_factory=list)defcoverage_score(self)->float:"""Calculate coverage score based on status and effectiveness.""" status_multiplier ={ ImplementationStatus.NOT_IMPLEMENTED:0.0, ImplementationStatus.PARTIAL:0.5, ImplementationStatus.IMPLEMENTED:0.8, ImplementationStatus.VERIFIED:1.0,}return self.effectiveness.value * status_multiplier[self.status]@dataclassclassThreat:id:str name:str category:str# STRIDE category description:str impact:str# Critical, High, Medium, Low likelihood:str risk_score:float@dataclassclassMitigationMapping: threat: Threat
controls: List[SecurityControl] residual_risk:str="Unknown" notes:str=""defcalculate_coverage(self)->float:"""Calculate how well controls cover the threat."""ifnot self.controls:return0.0 total_score =sum(c.coverage_score()for c in self.controls) max_possible =len(self.controls)* Effectiveness.VERY_HIGH.value
return(total_score / max_possible)*100if max_possible >0else0defhas_defense_in_depth(self)->bool:"""Check if multiple layers are covered.""" layers =set(c.layer for c in self.controls if c.status != ImplementationStatus.NOT_IMPLEMENTED)returnlen(layers)>=2defhas_control_diversity(self)->bool:"""Check if multiple control types are present.""" types =set(c.control_type for c in self.controls if c.status != ImplementationStatus.NOT_IMPLEMENTED)returnlen(types)>=2@dataclassclassMitigationPlan: name:str threats: List[Threat]= field(default_factory=list) controls: List[SecurityControl]= field(default_factory=list) mappings: List[MitigationMapping]= field(default_factory=list)defget_unmapped_threats(self)-> List[Threat]:"""Find threats without mitigations.""" mapped_ids ={m.threat.idfor m in self.mappings}return[t for t in self.threats if t.idnotin mapped_ids]defget_control_coverage(self)-> Dict[str,float]:"""Get coverage percentage for each threat."""return{ m.threat
β
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
βΊ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