product-meaning-extractor

product-meaning-extractor is a skill for Claude Code from AnastasiyaW/codex-claude-code-config. It costs 155 tokens per session (2,437 once invoked), scanned A, original, MIT.

A product-analysis process for understanding what a product is really worth before making a video, presentation, or advertisement. It gathers product information, visuals, brand details, and customer language, then identifies the core problem and change it creates.

In plain words
What is it for?
Use it to prepare a product brief, identify the main audience problem and product mechanism, define the tone and visual direction, and shape a stronger story for marketing content.
Why use it?
It prevents promotional content from becoming a list of features without a clear reason for the product to matter.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the claude-code-config plugin — 57 skills, 8 agents shipped together

Good fit Use it to prepare a product brief, identify the main audience problem and product mechanism, define the tone and visual direction, and shape a stronger story for marketing content.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/anastasiyaw/codex-claude-code-config/product-meaning-extractor
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add AnastasiyaW/codex-claude-code-config --skill product-meaning-extractor
Clone the repo
git clone --depth 1 https://github.com/AnastasiyaW/codex-claude-code-config

Made for: Claude Code.

Or install claude-code-config, the plugin that ships this one along with the rest of its 57 skills, 8 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for product-meaning-extractor

README.md
[![agentmods](https://agentmods.dev/badge/skills/anastasiyaw/codex-claude-code-config/product-meaning-extractor/github.svg)](https://agentmods.dev/skills/anastasiyaw/codex-claude-code-config/product-meaning-extractor)
Your own site
<a href="https://agentmods.dev/skills/anastasiyaw/codex-claude-code-config/product-meaning-extractor"><img src="https://agentmods.dev/badge/skills/anastasiyaw/codex-claude-code-config/product-meaning-extractor/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for product-meaning-extractor

Your own site · 80×15
<a href="https://agentmods.dev/skills/anastasiyaw/codex-claude-code-config/product-meaning-extractor"><img src="https://agentmods.dev/badge/skills/anastasiyaw/codex-claude-code-config/product-meaning-extractor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 155 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,437 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00155 $0.02437
Opus 5 $0.00077 $0.01218
Sonnet 5 $0.00031 $0.00487
Haiku 4.5 $0.00015 $0.00244

Measured 3d ago against content hash f931f4e0af66, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

product-meaning-extractor scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/video-production/product-meaning-extractor/SKILL.md · 214 lines

How it starts

The opening of the file, as written. The whole thing — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Product Meaning Extractor

Extract the REAL value from a product before writing a single line of video/presentation code. Without this step, content is a flat list of features. With it, content tells a story.

Why This Exists

A feature list alone may not explain why the product matters to this audience. Product analysis connects capabilities to a relevant, supportable customer outcome; it does not guarantee engagement.

This skill forces you to find what actually matters: the enemy, the transformation, the mechanism, and the emotional hook. Everything else flows from these.

Process

Step 1: Gather Raw Material

From the product URL:

  1. Visit the site, extract ALL text (hero, features, pricing, about, FAQ)
  2. Screenshot key visuals (hero, before/after, product shots)
  3. Extract brand colors from CSS (--primary, --accent, meta theme-color)
  4. Note the tone: formal/casual, technical/simple, premium/accessible

From reviews/testimonials (if available):

  1. Find testimonials on the site itself
  2. Check App Store / Product Hunt / G2 / Trustpilot / Reddit mentions
  3. Extract relevant VERBATIM customer phrases with their source, author/context, and date. Do not turn a paraphrase or invented phrase into a customer quotation.

Evidence travels with the brief: For each factual number, capability, comparison, customer name, or testimonial, retain the source URL/file and relevant scope/date. Separate verified observations, attributed vendor claims, and hypotheses. Examples below illustrate a structure, not facts about the current product. If evidence is missing, use [needs data], omit the claim, or write a clearly labelled hypothesis; continue the useful brief without inventing proof to fill a field.

Step 2: The "So What?" Test

For EVERY feature on the site, ask "So what?" until you reach the real value. Most features need 3-4 "so what?" iterations:

Feature: "Outputs .PSD with layers"
So what? → "You can edit individual elements"
So what? → "You don't redo the whole job if one thing is wrong"
So what? → "It saves hours of re-work and frustration"
REAL VALUE: "Never redo work from scratch again"

Read the full file on GitHub · 214 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago Changed · +17 lines f931f4e0af66
  2. 10d ago First seen · 197 lines · 155 tokens per session scan A 0ee6c7e52148

Subscribe to this mod's changes

product-meaning-extractor is a skill published in the GitHub repository AnastasiyaW/codex-claude-code-config (149 stars, last pushed yesterday), licensed MIT. It adds 155 tokens to every session and 2,437 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.