---
name: osp-technical-marketing
description: When the user needs technical marketing content, product value maps, technical positioning, developer-facing messaging, metadata, on-page SEO, semantic editing, technical writing review, or OSP-style content improvement. Prefer the external OSP MCP when available, and preserve attribution if adapting OSP material.
---

# OSP Technical Marketing Adapter

Use this skill for technical marketing content where accuracy, positioning, SEO, and clear writing all matter.

## Modes

1. Product value map
2. Metadata generator
3. Editing-code review
4. Technical writing guide
5. On-page SEO brief

## Product value map

Create a structured value map with:

- Tagline
- Market, technical, UX, and business position statements
- Personas
- Value cases
- Feature hierarchy
- Validation checks

## Metadata brief

Create:

- H1
- Meta title
- Meta description
- Slug
- Search intent
- Internal links
- Schema recommendation

## Editing review

Review:

- Scope and narrative
- Flow
- Style
- Word choice
- Technical accuracy
- Inclusive language
- Before and after examples

## MCP

If the upstream OSP MCP is configured, use it for value-map, metadata, editing, technical writing, and on-page SEO tasks. If it is not configured, use the templates in `skills/product-marketing-os/references/osp-methodology-adapter.md`.

## Attribution

This adapter is inspired by Open Strategy Partners' public methodology and MCP tools. Preserve attribution and license requirements when adapting substantial OSP-originated content.

## Hand off to

PMM OS is a chain, not a menu — don't dead-end at advice. Pass the work on:

- [`osp-content-optimizer`](../osp-content-optimizer/SKILL.md) — run the editing-code review
- [`pmm-aeo-geo`](../pmm-aeo-geo/SKILL.md) — make it citeable by AI engines
- [`pmm-content-writer`](../pmm-content-writer/SKILL.md) — expand into long-form
- [`pmm-coach`](../pmm-coach/SKILL.md) — review before anything customer- or exec-facing.

## Depth

Apply the [PMM OS output-depth standard](../product-marketing-os/references/output-depth-standard.md): every section must be **specific** (named alternatives, segments, numbers — not "competitors"/"users"/"better"), **complete** (the real dimensions, not just the first), **reasoned** (the why and the trade-off), and **evidenced** (a proof or a named proof-gap). Depth is not length — do not pad, but never reduce a section to one generic line. Self-check each section before returning.

## Frameworks & deep references

Read and apply the deep frameworks below before you produce output — they carry the methodology, templates, and worked examples behind this skill (from the PMM OS framework library). Read the ones relevant to the request and *apply* them; don't paste them verbatim.

- [`positioning/04-differentiated-value-proof-points.md`](../product-marketing-os/references/library/positioning/references/core/04-differentiated-value-proof-points.md) — attribute → value → proof for technical claims
- [`messaging/02-pain-claim-gain-messaging.md`](../product-marketing-os/references/library/messaging/references/core/02-pain-claim-gain-messaging.md) — pain-claim-gain even in technical content