product-marketing-context

Create or update a product marketing context document from repository content.

3.1k|223|Updated Jan 25, 2022
One-click install
npx skills add https://github.com/yoopta-editor/Yoopta-Editor --skill product-marketing-context-yoopta-editor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-marketing-context
Source: https://github.com/yoopta-editor/Yoopta-Editor/tree/main/.agents/skills/product-marketing-context
Command: npx skills add https://github.com/yoopta-editor/Yoopta-Editor --skill product-marketing-context-yoopta-editor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill creates and maintains a product marketing context document to avoid repetitive foundational marketing information.

Core Features & Use Cases

  • Auto-draft from codebase: study the repo (README, landing pages, marketing copy, package.json) to draft the initial context.
  • Centralized storage: saves the document at .claude/product-marketing-context.md for cross-skill reference.
  • Iterative updates: allows updates as the product and messaging evolve, enabling other marketing skills to reference it.

Quick Start

Ask the Skill to create or update the product marketing context. You can auto-draft from the repository or start from scratch, then review and refine the resulting document.

Frequently Asked Questions about product-marketing-context

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I centralize product marketing context to avoid repeating foundational information?

You can centralize product marketing context by generating a structured markdown document at .claude/product-marketing-context.md. This stores your positioning and messaging details in one repository location for cross-skill reference.

Can I auto-draft marketing positioning from my codebase?

Yes, you can auto-draft marketing positioning by scanning your repository. The system reads your README, landing pages, marketing copy, and package.json to generate an initial structured context document.

How do I keep my marketing context document updated as the product evolves?

You can iteratively update your marketing context document by prompting the skill to revise existing sections. This supports consistency as your product messaging evolves and other marketing skills reference the file.

What's the best way to maintain consistent product messaging across different marketing tasks?

The best way to maintain consistent product messaging is saving a centralized context document in your repository. Other marketing skills can reference this file to align with your established positioning.

Does this approach work without any existing marketing documentation in the repository?

Yes, it works without existing marketing documentation. When no foundational files are found, the skill starts from scratch to help you build the initial product marketing context document manually.

Why should I use a centralized markdown file for product context instead of ad-hoc documentation?

A centralized markdown file for product context avoids repetitive foundational information entry. It ensures all downstream marketing skills reference a single source of truth, keeping messaging consistent across tasks.