New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Product Marketing

by Nexus-JPF in Nexus-JPF/note-companion

When the user wants to create or update their product marketing context document.

MITAuto-check passedMarketing & SEO

Install Product Marketing

skills CLI
$ npx skills add Nexus-JPF/note-companion --skill product-marketing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Nexus-JPF/note-companion product-marketing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Nexus-JPF/note-companion.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/product-marketing .claude/skills/product-marketing && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
product-marketing
GitHub stars
870
Used in
4 other repos
Token cost
~2.3k tokens
SKILL.md length
993 words
Files
2
Skills in repo
18
Repo updated
First seen
Licence
MIT

At a glance

When the user wants to create or update their product marketing context document.

  • Works in 12 steps: Check for Existing Context → Gather Information → Product Overview → …
  • Wants to create
  • SKILL.md covers Workflow, Sections to Capture, Step 3: Create the Document and Step 4: Confirm, Version, and…, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Product Marketing is an agent skill from Nexus-JPF/note-companion. 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…

Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `evals/evals.json`).

It sits in Marketing & SEO, covering Positioning and messaging. The repository describes itself as: Note Companion: AI assistant for Obsidian that goes beyond just a chat. (prev File Organizer 2000). The licence is MIT.

When your agent uses it

  • Wants to create
  • Update their product marketing context document
  • The user mentions product context
  • Marketing context

Example prompts

  • “product context,”
  • “marketing context,”
  • “set up context,”
  • “/product-marketing”

Workflow steps

12 steps, taken from the step headings in SKILL.md.

  1. Check for Existing Context
  2. Gather Information
  3. Product Overview
  4. Target Audience
  5. Personas (B2B only)
  6. Problems & Pain Points
  7. Competitive Landscape
  8. Differentiation
  9. Objections & Anti-Personas
  10. Switching Dynamics
  11. Customer Language
  12. Brand Voice

What it can do on your machine

Read from SKILL.md and the folder at commit 9cad635. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Product Marketing loads about 2.3k tokens when it runs. Until then it costs about 142 tokens; SKILL.md has 993 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~142
When it runs · the whole SKILL.md, loaded when a task matches
~2.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Nexus-JPF/note-companion at commit 9cad635, republished under its MIT licence (© Nexus-JPF). 993 words, ~2,348 tokens.

Download SKILL.mdSave it as .claude/skills/product-marketing/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
product-marketing
description
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.
metadata.version
2.1.0

Product Marketing Context

You help users create and maintain a product marketing context document. This captures foundational positioning and messaging information that other marketing skills reference, so users don't repeat themselves.

The document is stored at .agents/product-marketing.md.

Workflow

Step 1: Check for Existing Context

First, check if .agents/product-marketing.md already exists. Also check .claude/product-marketing.md and the legacy filename product-marketing-context.md (in either .agents/ or .claude/) for older setups — if found anywhere other than .agents/product-marketing.md, offer to move it to the canonical location.

If it exists:

  • Read it and summarize what's captured — note its current Document version and the last few Changelog entries so the user sees where the doc stands and what's changed recently
  • Ask which sections they want to update
  • Only gather info for those sections
  • On any substantive save, bump the version and add a changelog entry (see Step 4). This doc is the shared context every other marketing skill reads, so a dated paper trail of what changed and why is worth keeping.

If it doesn't exist, offer two options:

  1. Auto-draft from codebase (recommended): You'll study the repo—README, landing pages, marketing copy, package.json, etc.—and draft a V1 of the context document. The user then reviews, corrects, and fills gaps. This is faster than starting from scratch.

  2. Start from scratch: Walk through each section conversationally, gathering info one section at a time.

Most users prefer option 1. After presenting the draft, ask: "What needs correcting? What's missing?"

Step 2: Gather Information

If auto-drafting:

  1. Read the codebase: README, landing pages, marketing copy, about pages, meta descriptions, package.json, any existing docs
  2. Draft all sections based on what you find
  3. Present the draft and ask what needs correcting or is missing
  4. Iterate until the user is satisfied

If starting from scratch: Walk through each section below conversationally, one at a time. Don't dump all questions at once.

For each section:

  1. Briefly explain what you're capturing
  2. Ask relevant questions
  3. Confirm accuracy
  4. Move to the next

Push for verbatim customer language — exact phrases are more valuable than polished descriptions because they reflect how customers actually think and speak, which makes copy more resonant.

Sections to Capture

1. Product Overview
  • One-line description
  • What it does (2-3 sentences)
  • Product category (what "shelf" you sit on—how customers search for you)
  • Product type (SaaS, marketplace, e-commerce, service, etc.)
  • Business model and pricing
2. Target Audience
  • Target company type (industry, size, stage)
  • Target decision-makers (roles, departments)
  • Primary use case (the main problem you solve)
  • Jobs to be done (2-3 things customers "hire" you for)
  • Specific use cases or scenarios
3. Personas (B2B only)

If multiple stakeholders are involved in buying, capture for each:

  • User, Champion, Decision Maker, Financial Buyer, Technical Influencer
  • What each cares about, their challenge, and the value you promise them
4. Problems & Pain Points
  • Core challenge customers face before finding you
  • Why current solutions fall short
  • What it costs them (time, money, opportunities)
  • Emotional tension (stress, fear, doubt)
5. Competitive Landscape
  • Direct competitors: Same solution, same problem (e.g., Calendly vs SavvyCal)
  • Secondary competitors: Different solution, same problem (e.g., Calendly vs Superhuman scheduling)
  • Indirect competitors: Conflicting approach (e.g., Calendly vs personal assistant)
  • How each falls short for customers
6. Differentiation
  • Key differentiators (capabilities alternatives lack)
  • How you solve it differently
  • Why that's better (benefits)
  • Why customers choose you over alternatives
7. Objections & Anti-Personas
  • Top 3 objections heard in sales and how to address them
  • Who is NOT a good fit (anti-persona)
8. Switching Dynamics

The JTBD Four Forces:

  • Push: What frustrations drive them away from current solution
  • Pull: What attracts them to you
  • Habit: What keeps them stuck with current approach
  • Anxiety: What worries them about switching
Show full SKILL.md (384 more words)Show less
9. Customer Language
  • How customers describe the problem (verbatim)
  • How they describe your solution (verbatim)
  • Words/phrases to use
  • Words/phrases to avoid
  • Glossary of product-specific terms
10. Brand Voice
  • Tone (professional, casual, playful, etc.)
  • Communication style (direct, conversational, technical)
  • Brand personality (3-5 adjectives)
11. Proof Points
  • Key metrics or results to cite
  • Notable customers/logos
  • Testimonial snippets
  • Main value themes and supporting evidence
12. Goals
  • Primary business goal
  • Key conversion action (what you want people to do)
  • Current metrics (if known)

Step 3: Create the Document

After gathering information, create .agents/product-marketing.md with this structure:

markdown
# Product Marketing Context

**Document version:** v1
**Last updated:** [date]

## Product Overview
**One-liner:**
**What it does:**
**Product category:**
**Product type:**
**Business model:**

## Target Audience
**Target companies:**
**Decision-makers:**
**Primary use case:**
**Jobs to be done:**
-
**Use cases:**
-

## Personas
| Persona | Cares about | Challenge | Value we promise |
|---------|-------------|-----------|------------------|
| | | | |

## Problems & Pain Points
**Core problem:**
**Why alternatives fall short:**
-
**What it costs them:**
**Emotional tension:**

## Competitive Landscape
**Direct:** [Competitor] — falls short because...
**Secondary:** [Approach] — falls short because...
**Indirect:** [Alternative] — falls short because...

## Differentiation
**Key differentiators:**
-
**How we do it differently:**
**Why that's better:**
**Why customers choose us:**

## Objections
| Objection | Response |
|-----------|----------|
| | |

**Anti-persona:**

## Switching Dynamics
**Push:**
**Pull:**
**Habit:**
**Anxiety:**

## Customer Language
**How they describe the problem:**
- "[verbatim]"
**How they describe us:**
- "[verbatim]"
**Words to use:**
**Words to avoid:**
**Glossary:**
| Term | Meaning |
|------|---------|
| | |

## Brand Voice
**Tone:**
**Style:**
**Personality:**

## Proof Points
**Metrics:**
**Customers:**
**Testimonials:**
> "[quote]" — [who]
**Value themes:**
| Theme | Proof |
|-------|-------|
| | |

## Goals
**Business goal:**
**Conversion action:**
**Current metrics:**

## Changelog
*Newest first. One line per revision: what changed and why.*
- v1 ([date]) — Initial context.

Step 4: Confirm, Version, and Save

  • Show the completed document
  • Ask if anything needs adjustment
  • Set the version and changelog — this is the paper trail for a doc every other skill reads:
    • New document: set Document version: v1 and a single Changelog entry — - v1 ([today]) — Initial context.
    • Updating an existing document: increment the version (v2 → v3 …), update Last updated to today, and prepend a new Changelog entry at the top of the list (newest first) summarizing what changed and why in one line. Never rewrite or reorder past entries.
    • A good entry names the sections touched and the reason, not "updated the doc." Examples:
      • - v3 (2026-07-16) — Repositioned from "email tool" to "deliverability platform"; added RevOps to the ICP.
      • - v2 (2026-06-02) — Rewrote value prop and objections after 5 customer interviews; added competitor Acme.
    • Use today's date in ISO form (YYYY-MM-DD) for the entry and Last updated.
    • Pure typo-only fix: don't bump the version or add a changelog entry — just save the correction. Every other change bumps the version and gets an entry. When the change is a real repositioning, say so plainly — downstream skills will now generate against the new context.
  • Save to .agents/product-marketing.md
  • Tell them: "Other marketing skills will now use this context automatically. The Changelog at the bottom tracks every revision — check it to see how your positioning has evolved. Run /product-marketing anytime to update it."

Tips

  • Be specific: Ask "What's the #1 frustration that brings them to you?" not "What problem do they solve?"
  • Capture exact words: Customer language beats polished descriptions
  • Ask for examples: "Can you give me an example?" unlocks better answers
  • Validate as you go: Summarize each section and confirm before moving on
  • Skip what doesn't apply: Not every product needs all sections (e.g., Personas for B2C)

© Nexus-JPF, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .agents/skills/product-marketing of Nexus-JPF/note-companion.

  • SKILL.md
  • evals/evals.json

Open the folder on GitHubat commit 9cad635

Used in 4 other repositories

We found 4 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 4 other GitHub owners. This page covers the copy in Nexus-JPF/note-companion, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Product Marketing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Product Marketing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Product Marketing this skillNexus-JPF/note-companion8704 repos~2.3kAutomated safety check: PassMIT
Marketing OsYuzzyuk/marketing-os540—~2.5kAutomated safety check: PassMIT
Revenue Centric Designheliocosta-dev/revenue-centric-design740—~1.6kAutomated safety check: PassCustom licence
Startup Positioningferdinandobons/startup-skill1.2k—~4.6kAutomated safety check: PassMIT
Stanley Druckenmiller Investmenttradermonty/claude-trading-skills3k1 repos~2kAutomated safety check: PassMIT
B2b Playbookweilun88313/B2B-Playbook203—~3.1kAutomated safety check: PassProprietary

Similar skills

  • Marketing Os

    Yuzzyuk/marketing-os

    A complete marketing department in one skill. An agent skill from Yuzzyuk/marketing-os.

    540 GitHub stars~2.5k tokensUpdated 1 mo ago
    Marketing & SEOAuto-check passed

  • Revenue Centric Design

    heliocosta-dev/revenue-centric-design

    Playbook for designing SaaS and startup products that convert, retain, and monetize — landing pages & CRO, checkout & forms, onboarding/activation, churn reduction, pricing psychology, dashboards…

    740 GitHub stars~1.6k tokensUpdated 1 mo ago
    Marketing & SEOAuto-check passed

  • Startup Positioning

    ferdinandobons/startup-skill

    Market positioning strategy using the April Dunford framework, enriched with JTBD discovery, Moore positioning statement, and Neumeier's Onliness Test.

    1.2k GitHub stars~4.6k tokensUpdated 3 mo ago
    Marketing & SEOAuto-check passed

  • Stanley Druckenmiller Investment

    tradermonty/claude-trading-skills

    Druckenmiller Strategy Synthesizer - Integrates 8 upstream skill outputs (Market Breadth, Uptrend Analysis, Market Top, Macro Regime, FTD Detector, VCP Screener, Theme Detector, CANSLIM Screener)…

    3k GitHub starsUsed in 1 repo~2k tokens
    Marketing & SEOAuto-check passed

  • B2b Playbook

    weilun88313/B2B-Playbook

    Turn B2B marketing work into evidence-aware outputs using market, positioning, demand, account-program, lifecycle, and tool-selection guidance.

    203 GitHub stars~3.1k tokensUpdated 29 days ago
    Marketing & SEOAuto-check passed

  • Research Brand

    onvoyage-ai/gtm-engineer-skills

    Researches a company from its URL and produces a Brand DNA file covering positioning, audience, competitors, voice, and messaging.

    1.3k GitHub stars~1.3k tokensUpdated 4 mo ago
    Marketing & SEOAuto-check passed

More from Nexus-JPF/note-companion

All 18 skills in this repo

  • Analytics

    Nexus-JPF/note-companion

    When the user wants to set up, improve, or audit analytics tracking and measurement.

    870 GitHub starsUsed in 7 repos~2.2k tokens
    Auto-check passed

  • Customer Research

    Nexus-JPF/note-companion

    When the user wants to conduct, analyze, or synthesize customer research.

    870 GitHub starsUsed in 6 repos~3.2k tokens
    Auto-check passed

  • Marketing Plan

    Nexus-JPF/note-companion

    When the user needs a comprehensive marketing plan for a client, a company they advise, or their own product.

    870 GitHub starsUsed in 5 repos~5.2k tokens
    Auto-check passed

  • Competitor Profiling

    Nexus-JPF/note-companion

    When the user wants to research, profile, or analyze competitors from their URLs.

    870 GitHub starsUsed in 4 repos~3.5k tokens
    Auto-check passed

  • Onboarding

    Nexus-JPF/note-companion

    When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value.

    870 GitHub starsUsed in 4 repos~1.6k tokens
    Auto-check passed

  • Image

    Nexus-JPF/note-companion

    When the user wants to create, generate, edit, or optimize images for marketing — blog heroes, social graphics, product mockups, profile banners, listing visuals, or brand assets.

    870 GitHub starsUsed in 3 repos~3.9k tokens
    Auto-check passed

Categories

Questions about Product Marketing

What does Product Marketing do?

When the user wants to create or update their product marketing context document. Product Marketing is an agent skill from Nexus-JPF/note-companion. When the user wants to create or update their product marketing context document.

When should I use Product Marketing?

Product Marketing fits situations like: wants to create; update their product marketing context document; the user mentions product context; marketing context.

How do I install Product Marketing in Claude Code?

Run `npx skills add Nexus-JPF/note-companion --skill product-marketing -a claude-code`. Or copy the skill folder (.agents/skills/product-marketing in Nexus-JPF/note-companion) into .claude/skills/product-marketing in your project. Claude Code loads it when a task matches its description.

How do I install Product Marketing in Codex?

Run `npx skills add Nexus-JPF/note-companion --skill product-marketing -a codex`. Or copy the skill folder (.agents/skills/product-marketing in Nexus-JPF/note-companion) into .agents/skills/product-marketing in your project. Codex loads it when a task matches its description.

Can I use Product Marketing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Nexus-JPF/note-companion --skill product-marketing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/product-marketing, .gemini/skills/product-marketing, .github/skills/product-marketing and .opencode/skills/product-marketing in your project.

What does Product Marketing need to run?

SKILL.md names no scripts, command-line tools or credentials: Product Marketing is instructions for the agent only.

Does Product Marketing access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Product Marketing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Product Marketing use?

Product Marketing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Product Marketing use?

About 2.3k tokens (SKILL.md is roughly 9.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Product Marketing?

Skills that share tags, products or a category with Product Marketing: Marketing Os (Yuzzyuk/marketing-os, 540 stars), Revenue Centric Design (heliocosta-dev/revenue-centric-design, 740 stars), Startup Positioning (ferdinandobons/startup-skill, 1.2k stars) and Stanley Druckenmiller Investment (tradermonty/claude-trading-skills, 3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Product Marketing?

Nexus-JPF (a GitHub organization) maintains it in Nexus-JPF/note-companion, which has 870 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 7, 2026.

Source: Nexus-JPF/note-companion on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.