category-point-of-view

category-point-of-view is a skill for Claude Code from adam-lagerhausen/b2b-marketing-skills. It costs 46 tokens per session (3,223 once invoked), scanned A, original, MIT.

A structured market viewpoint for a business product or company. It explains the customer problem, the change happening in the market, and the category or strategic idea the company wants to be associated with.

In plain words
What is it for?
It helps shape founder or executive narratives, launch and fundraising stories, market education, content strategy, category language, distribution plans, and ways to measure whether the viewpoint is being adopted.
Why use it?
It helps a company stand out from crowded labels and avoid vague thought leadership. The story starts with a problem customers recognize before connecting that problem to the company’s solution.

Skill for Claude Code

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

Part of the b2b-marketing-skills plugin — 9 skills shipped together

Good fit It helps shape founder or executive narratives, launch and fundraising stories, market education, content strategy, category language, distribution plans, and ways to measure whether the viewpoint is being adopted.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/adam-lagerhausen/b2b-marketing-skills/category-point-of-view
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 adam-lagerhausen/b2b-marketing-skills --skill category-point-of-view
Clone the repo
git clone --depth 1 https://github.com/adam-lagerhausen/b2b-marketing-skills

Made for: Claude Code.

Or install b2b-marketing-skills, the plugin that ships this one along with the rest of its 9 skills.

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 category-point-of-view

README.md
[![agentmods](https://agentmods.dev/badge/skills/adam-lagerhausen/b2b-marketing-skills/category-point-of-view/github.svg)](https://agentmods.dev/skills/adam-lagerhausen/b2b-marketing-skills/category-point-of-view)
Your own site
<a href="https://agentmods.dev/skills/adam-lagerhausen/b2b-marketing-skills/category-point-of-view"><img src="https://agentmods.dev/badge/skills/adam-lagerhausen/b2b-marketing-skills/category-point-of-view/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 category-point-of-view

Your own site · 80×15
<a href="https://agentmods.dev/skills/adam-lagerhausen/b2b-marketing-skills/category-point-of-view"><img src="https://agentmods.dev/badge/skills/adam-lagerhausen/b2b-marketing-skills/category-point-of-view.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,223 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.
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.00046 $0.03223
Opus 5 $0.00023 $0.01612
Sonnet 5 $0.00009 $0.00645
Haiku 4.5 $0.00005 $0.00322

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

Security

Grade A, and why

category-point-of-view 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 12d 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/category-point-of-view/SKILL.md · 356 lines

How it starts

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

Category Point of View

When to use

Use this skill when you need to build, sharpen, or pressure-test a category point of view for a B2B company, product, campaign, founder narrative, executive content program, or market education motion.

Use it for:

  • Defining the problem the company wants to own
  • Creating a category narrative before a launch, fundraise, or executive campaign
  • Moving beyond a crowded label such as "AI CRM," "AI SDR," "copilot," or "workflow automation"
  • Turning product positioning into a broader market belief system
  • Building a content strategy that can survive the coming flood of AI-generated slop
  • Giving practitioners useful language while giving leaders a reason to care
  • Creating a measurement plan for category creation and narrative adoption

Do not use this skill to create a vague brand manifesto, inflated category claim, or thin thought-leadership calendar. A category POV must make a buyer say, "that is exactly the problem we are living with," before it asks them to believe the solution.

Inputs

Ask for or infer as much of the following as possible. If an input is missing, state the assumption and mark confidence as low.

  • Company and product name
  • Product description and core capabilities
  • Existing category or market label
  • Target audience: practitioner, buyer, economic buyer, influencer, industry, company size, maturity
  • Problem the company wants to own
  • Current alternatives, status quo, and competing category labels
  • Market shift that makes the problem newly urgent
  • Practitioner pains and daily workflows
  • Leader-level business consequences
  • Differentiated belief, mechanism, data, benchmark, model, community, or proof
  • Customer language, stories, objections, and examples
  • Existing content, founder opinions, product roadmap, and proof assets
  • Distribution channels and founder or executive strengths
  • Constraints: claims to avoid, regulated topics, competitive boundaries, launch timing, content capacity

Core principles

Read the full file on GitHub · 356 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. 12d ago First seen · 356 lines · 46 tokens per session scan A 3a5d25c74d1a

Subscribe to this mod's changes

category-point-of-view is a skill published in the GitHub repository adam-lagerhausen/b2b-marketing-skills (5 stars, last pushed 2mo ago), licensed MIT. It adds 46 tokens to every session and 3,223 once invoked, about $0.0002 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-31.

Related

Other skills, from other repositories

go-to-market-playbook

A reusable Go-to-Market strategy template for both B2B and B2C launches. Covers positioning, messaging, ICP definition, channel selection, and competitive analysis frameworks. By @WeiYipei.

Gingiris-1031/gingiris-skills · 48 tokens

adoption-leaderboard

Scores a rep's or a team's recent sales calls against a fixed set of five winning-behavior checklists (rapport, upsell signals, renewal risk, customer experience, value realization), then ranks reps lowest-adoption-first so the highest-leverage coaching targets lead. Use when running a team calibration, prepping 1:1…

zime-ai/zime-gtm-skills · 96 tokens

challenger

Audits a B2B sales call transcript against the Challenger Sale framework (teach, tailor, take control, plus the commercial-teaching pitch arc), or sweeps a CRM export for deals with no teaching insight logged. Use when a rep leans on discovery-question skill but rarely brings a point of view, when prepping a rep for a…

zime-ai/zime-gtm-skills · 104 tokens

champion-tracker

Tracks champion strength across a deal's call(s) — builds an action ledger, one row per named contact per cited quote, tagging each as either an act of internal selling (looping in a stakeholder, pushing back for the rep in a room the rep wasn't in) or mere positive sentiment (encouraging words, no action), then reads…

zime-ai/zime-gtm-skills · 112 tokens

end-client-registration

Audits a partner/reseller's end-client deal registration for completeness — partner identity, end-client entity kept distinct from the partner, engagement scope, conflict check against the direct pipeline, confirmed permission to engage the end-client contact, commercial terms, and an expiry window. Use when reviewing…

zime-ai/zime-gtm-skills · 108 tokens

executive-briefing

Writes the short brief a rep sends upward out of one deal — to their own exec or the buyer's exec sponsor — covering deal snapshot, status, what's at risk, and the ask, each claim cited to a quote or a CSV column/cell. Use when someone who will never read the transcript needs to act on one deal, not a call-by-call…

zime-ai/zime-gtm-skills · 86 tokens