Triage dependency findings by verified affected versions, exposure, exploit conditions, impact, and available fixes.
Instructions your experts follow when using this skill.
Use this for scanner results or a list of advisories.
For every finding capture the advisory ID, package and ecosystem, installed version, affected and fixed ranges, advisory publisher, source URL, and check time. Prefer the package maintainer or vendor advisory, then a recognised vulnerability database. Keep disputed or incomplete data marked as such.
Check whether the package is present in the shipped artifact, which service loads it, whether the vulnerable feature is enabled, who can reach the path, what data or privilege it exposes, and which controls reduce the risk. Mark unproven points unknown.
Return these fields: relevance, urgency, reason, safe target version, workaround, affected owner, validation steps, and deadline basis. Use confirmed, likely, not affected, or unknown for relevance. Severity is an input, not the result.
Never close a finding because the package is transitive or the score is low. Never call it exploitable without the required path evidence. Do not suppress or accept risk; prepare the evidence for the authorised owner.
Phrases that help your experts find this skill.
When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' 'who is my target audience,' 'describe my product,' 'ICP,' 'ideal customer profile,' or wants to avoid repeating foundational information across marketing tasks. Use this at the start of any new project before using other marketing skills — it creates `.agents/product-marketing.md` that all other skills reference for product, audience, and positioning context.
When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitors. For sales-specific battle cards, see sales-enablement.
When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," "PMF survey," "product/market fit survey," "customer interview questions," "interview outreach," "Sales Safari," or "find out why customers churn/convert/buy." Use for analyzing existing research assets, mining online sources, AND running primary research (interviews and surveys). For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.