diff --git a/skills/.curated/product-marketing-strategy/LICENSE.txt b/skills/.curated/product-marketing-strategy/LICENSE.txt
new file mode 100644
index 00000000..b5ed4ece
--- /dev/null
+++ b/skills/.curated/product-marketing-strategy/LICENSE.txt
@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright (c) Microsoft Corporation.
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.
diff --git a/skills/.curated/product-marketing-strategy/SKILL.md b/skills/.curated/product-marketing-strategy/SKILL.md
new file mode 100644
index 00000000..18c064b5
--- /dev/null
+++ b/skills/.curated/product-marketing-strategy/SKILL.md
@@ -0,0 +1,49 @@
+---
+name: product-marketing-strategy
+description: Define product positioning, ICP, messaging, competitive framing, and launch plans. Use when the user needs a product marketing strategy, positioning statement, message map, battlecard, launch brief, or a PMM review of an existing plan.
+---
+
+# Product Marketing Strategy
+
+## Overview
+
+Use this skill to turn product facts, customer context, and business goals into a clear product marketing plan. Choose the PMM job first, gather only the evidence that matters, then produce the smallest useful deliverable for the decision at hand.
+
+## Workflow
+
+1. Identify the product, target audience, commercial goal, and time horizon. Infer these from the request when possible; only ask when the deliverable would change materially.
+2. Choose the primary PMM task and load the matching reference:
+   - `references/positioning-and-icp.md` for segmentation, ICP definition, category choice, and positioning
+   - `references/messaging-and-proof.md` for value propositions, persona messaging, proof points, and objection handling
+   - `references/competitive-battlecards.md` for competitor framing, talk tracks, and battlecards
+   - `references/launch-planning.md` for launch tiering, briefs, checklists, and launch metrics
+3. Gather evidence from the artifacts already in reach first: product docs, roadmap notes, win-loss summaries, support tickets, pricing pages, sales notes, research interviews, or existing launch plans.
+4. Separate facts from assumptions. When the evidence is thin, state assumptions plainly and note what should be validated next.
+5. Build the smallest deliverable that solves the request: a positioning statement, ICP summary, messaging hierarchy, battlecard, launch brief, or PMM review.
+6. Review the output for clarity, distinctiveness, and proof. Remove claims that are not supported by the available evidence.
+
+## PMM Rules
+
+- Do not invent customer quotes, market data, win rates, competitor weaknesses, or proof points.
+- Prefer one clear position over a stack of vague benefits.
+- Tie every message to a buyer, pain, value, and proof source whenever possible.
+- Keep strategy and copy separate. If the user asks for strategy, include assumptions, tradeoffs, and gaps to validate.
+- Match launch planning depth to the launch tier. Do not produce an eight-week plan for a minor changelog update.
+- Use plain language unless the user explicitly wants brand-polished copy.
+
+## Source Prioritization
+
+Use sources in this order unless the user says otherwise:
+
+- User-provided notes, drafts, product docs, and roadmap material
+- Customer research, win-loss notes, support issues, and sales feedback
+- Existing website, pricing, demo, and enablement assets
+- External competitor and market research when available and necessary
+
+If the source material is incomplete, deliver the best provisional draft you can, mark assumptions clearly, and list the smallest missing facts needed to finalize it.
+
+## Deliverables
+
+- Deliver the exact PMM artifact the user asked for when one is specified.
+- If the request is broad, choose the most decision-relevant artifact and say what you chose.
+- When useful, provide a short executive summary followed by the detailed artifact.
diff --git a/skills/.curated/product-marketing-strategy/agents/openai.yaml b/skills/.curated/product-marketing-strategy/agents/openai.yaml
new file mode 100644
index 00000000..4c65944d
--- /dev/null
+++ b/skills/.curated/product-marketing-strategy/agents/openai.yaml
@@ -0,0 +1,4 @@
+interface:
+  display_name: "Product Marketing Strategy"
+  short_description: "Shape positioning, messaging, and launches"
+  default_prompt: "Use $product-marketing-strategy to define positioning, ICP, messaging, a battlecard, or a launch plan for this product."
diff --git a/skills/.curated/product-marketing-strategy/references/competitive-battlecards.md b/skills/.curated/product-marketing-strategy/references/competitive-battlecards.md
new file mode 100644
index 00000000..86bf7c8b
--- /dev/null
+++ b/skills/.curated/product-marketing-strategy/references/competitive-battlecards.md
@@ -0,0 +1,42 @@
+# Competitive Battlecards
+
+Use this reference when the user needs competitive positioning, battlecards, or help responding to competitor claims in sales or launch contexts.
+
+## Sourcing Rules
+
+- Use first-hand product research, pricing pages, docs, sales notes, reviews, or user-provided material when available.
+- Mark uncertain claims as assumptions or open questions.
+- Do not caricature competitors. Credible battlecards are specific, fair, and usable in live conversations.
+
+## Workflow
+
+1. Identify the competitor tier: direct, adjacent, or status quo.
+2. Capture how they position themselves.
+3. Note where they appear stronger, where they appear weaker, and where the comparison is situational.
+4. Map the comparison to the buyer scenarios where you win or lose.
+5. Turn that into short talk tracks and objection responses.
+
+## Battlecard Template
+
+| Section | What to Capture |
+|---------|-----------------|
+| Competitor | Name, category, and typical buyer |
+| Their pitch | How they describe themselves |
+| Strongest fit | Where they are genuinely compelling |
+| Weakest fit | Where they are less aligned or harder to use |
+| Our advantage | Specific comparison tied to buyer value |
+| Landmines | Claims your team should not make |
+| Talk track | The shortest useful rebuttal or reframing |
+
+## Win-Loss Questions
+
+- Which buyer segment chooses them most often?
+- What reason is given when they win?
+- What evidence exists that we win in a different segment or use case?
+- Is the gap strategic, product-based, pricing-based, or execution-based?
+
+## Talk Track Guidance
+
+- Reframe to buyer fit instead of attacking the competitor.
+- Prefer "best for this scenario" language over absolute superiority claims.
+- Keep sales talk tracks short enough to use live, then attach proof if needed.
diff --git a/skills/.curated/product-marketing-strategy/references/launch-planning.md b/skills/.curated/product-marketing-strategy/references/launch-planning.md
new file mode 100644
index 00000000..67ca3204
--- /dev/null
+++ b/skills/.curated/product-marketing-strategy/references/launch-planning.md
@@ -0,0 +1,64 @@
+# Launch Planning
+
+Use this reference when the user needs a launch brief, rollout checklist, launch tiering, or launch metrics for a product or feature release.
+
+## Launch Tiering
+
+| Tier | Typical Scope | Suggested Planning Depth |
+|------|----------------|--------------------------|
+| Tier 1 | New product, major launch, pricing or category shift | Full brief, cross-functional plan, enablement, campaign timeline |
+| Tier 2 | Significant feature, integration, or expansion release | Focused brief, channel plan, sales and support readiness |
+| Tier 3 | Small feature or improvement | Changelog, lightweight announcement, support updates |
+
+## Launch Brief Template
+
+Capture:
+
+- what is launching
+- who it is for
+- why it matters now
+- the main message
+- launch tier
+- channels and assets needed
+- sales and support enablement needs
+- success metrics and review window
+
+## Planning Workflow
+
+1. Pick the launch tier based on business impact and audience breadth.
+2. Define the audience, goal, and main message before listing channels.
+3. Decide what assets are actually required: landing page, deck updates, FAQ, email, webinar, changelog, or in-product copy.
+4. Confirm enablement for sales, support, and customer success when the release affects them.
+5. Choose a small set of leading and lagging metrics.
+
+## Checklist By Tier
+
+### Tier 1
+
+- Positioning and messaging approved
+- Launch brief shared cross-functionally
+- Sales deck, FAQ, and objection handling updated
+- Website or landing page ready
+- Channel plan scheduled
+- Launch metrics owner assigned
+
+### Tier 2
+
+- Key messages agreed
+- Product page or changelog updated
+- Email or announcement drafted
+- Sales and support briefed
+- Metrics defined
+
+### Tier 3
+
+- Changelog copy written
+- Support docs updated if needed
+- In-product or customer notice prepared
+- Owner assigned to monitor adoption or support issues
+
+## Metrics Guidance
+
+- Leading indicators: traffic, clicks, signups, demo requests, activation starts
+- Lagging indicators: adoption, qualified pipeline, expansion, retention, revenue impact
+- Keep the scorecard proportional to the launch. Not every release needs a campaign dashboard.
diff --git a/skills/.curated/product-marketing-strategy/references/messaging-and-proof.md b/skills/.curated/product-marketing-strategy/references/messaging-and-proof.md
new file mode 100644
index 00000000..0676a886
--- /dev/null
+++ b/skills/.curated/product-marketing-strategy/references/messaging-and-proof.md
@@ -0,0 +1,52 @@
+# Messaging And Proof
+
+Use this reference when the user needs a value proposition, persona messaging, objection handling, or channel-ready message hierarchy.
+
+## Messaging Stack
+
+Build messages from top to bottom:
+
+1. Audience: who this message is for
+2. Problem: what pain, risk, or stalled outcome they care about
+3. Value: what improves because of the product
+4. Mechanism: how the product creates that value
+5. Proof: what evidence makes the claim believable
+
+## Message Hierarchy
+
+| Layer | Purpose |
+|-------|---------|
+| Core promise | One sentence on the main outcome |
+| Supporting benefits | Two to four buyer-relevant gains |
+| Proof points | Product facts, evidence, or examples |
+| Objection handling | Why the buyer should still believe and act |
+
+## Persona Message Template
+
+| Persona | Priority | Message Angle | Evidence Needed |
+|---------|----------|---------------|-----------------|
+| Economic buyer | ROI, speed, risk reduction | Business outcome | Case study, quantified impact, cost comparison |
+| Technical evaluator | Fit, security, integration | Architecture and implementation confidence | Docs, standards, setup details |
+| User or champion | Ease, time saved, job-to-be-done | Day-to-day workflow value | Demo path, screenshots, customer quote |
+
+## Proof Guidance
+
+- Use the strongest available proof first: customer outcomes, product behavior, adoption signals, benchmarks, or credible examples.
+- If proof is weak, tone the claim down instead of over-claiming.
+- Separate proof from aspiration. "Helps teams cut manual routing steps" is safer than "guarantees 40% faster launches" unless evidence exists.
+
+## Objection Handling
+
+For each major objection, capture:
+
+- objection
+- what is actually behind it
+- the shortest honest response
+- the best proof or artifact to support the response
+
+## Channel Adaptation
+
+- Homepage: emphasize category, outcome, and proof fast.
+- Sales deck: lead with problem, value, differentiation, and evidence.
+- Email or outbound: keep one persona, one pain, and one reason to respond.
+- Launch announcement: connect the release to a concrete customer problem and next step.
diff --git a/skills/.curated/product-marketing-strategy/references/positioning-and-icp.md b/skills/.curated/product-marketing-strategy/references/positioning-and-icp.md
new file mode 100644
index 00000000..d760daf9
--- /dev/null
+++ b/skills/.curated/product-marketing-strategy/references/positioning-and-icp.md
@@ -0,0 +1,52 @@
+# Positioning And ICP
+
+Use this reference when the user needs to decide who the product is for, what category it should live in, or how to explain its value clearly.
+
+## Workflow
+
+1. Start with the business objective: pipeline, adoption, retention, expansion, or launch readiness.
+2. Define the best-fit customer segment before writing messaging.
+3. Identify the buyer roles that matter: economic buyer, technical evaluator, day-to-day user, or champion.
+4. List the real alternatives customers compare against, including the status quo.
+5. Turn distinctive product attributes into customer value, then into positioning language.
+6. Validate the draft against evidence from sales, research, or existing customers.
+
+## ICP Template
+
+Capture only the fields that affect positioning or GTM:
+
+| Dimension | Notes |
+|-----------|-------|
+| Company type | Industry, business model, or segment |
+| Size | Team, revenue, or stage band |
+| Buyer roles | Who signs, evaluates, and uses |
+| Pain | What problem is urgent enough to act on |
+| Trigger | What changed so the problem matters now |
+| Proof of fit | Existing customer, usage pattern, or win reason |
+| Exclusions | Who should not be targeted first |
+
+## Segmenting Guidance
+
+- Segment by urgency and fit, not just demographics.
+- Prefer narrow initial focus over broad theoretical TAM.
+- If multiple segments are attractive, rank them by pain intensity, ability to buy, speed to value, and existing proof.
+
+## Positioning Workflow
+
+1. Write down the competitive alternatives, including "do nothing" or "build it internally."
+2. List the product attributes that are genuinely differentiated.
+3. Translate each attribute into buyer value.
+4. Pick the market category that makes the product easiest to understand without underselling it.
+5. Draft a positioning statement and tighten it until it sounds like a claim a buyer could repeat.
+
+## Positioning Statement Template
+
+For `[target customer]` who `[urgent problem or job]`, `[product]` is a `[category]` that `[primary outcome]`. Unlike `[main alternative]`, it `[differentiation backed by proof]`.
+
+## Validation Checklist
+
+- At least one target segment clearly has the strongest pain and fit.
+- The position explains why this product matters now.
+- The main alternative is explicit.
+- The differentiator is specific enough to defend.
+- The draft can be supported by product facts, customer evidence, or measurable proof.