Use when the partnership is about data or research: licensing and evaluation terms, academic collaboration, and IP and data-rights compliance.
Instructions your experts follow when using this skill.
Use this when the partnership is about data or research rather than go-to-market. Start from the data or research asset, the counterparty (a company, a lab, a university), any existing non-disclosure agreements (NDAs), material transfer agreements (MTAs), or licence drafts, and the intellectual property (IP) and compliance constraints.
Define the asset — a dataset, a model, a protocol, physical samples — the permitted uses, and what is explicitly out of scope.
Evaluation access gets dated terms and a conversion path to a licence. Nothing open-ended.
Licence scope and fees, data-sharing rights, publication and IP ownership, confidentiality, term and termination.
Every clause routes to Legal before it leaves. There are no exceptions to that line.
One row per alliance: its agreements, the key dates (expiry, review, publication windows), the obligations due, and a red/yellow/green compliance grade.
Anything yellow gets a dated cure line with an owner.
Which alliances produced — papers, products, revenue — which stalled, and the renew, expand, or exit call per alliance with its evidence.
The alliance scope, the terms-spine draft, the compliance tracker, and the quarterly portfolio read.
No existing drafts means starting from owner-stated intent marked INFERENCE, with Legal review as the first step. No compliance owner means the owner holds it until one is named.
No term sheet, licence, material transfer agreement, or publication approval goes out without your explicit yes.
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.