agentsclimarketplace
Sign in

Cognitive ux product marketing

Skill kfeng209-oss/cognitive-ux/skills/cognitive-ux-product-marketing

Design and audit product-marketing websites for complex software, services, and subscriptions using evidence-informed UX. Use when a visitor must evaluate capabilities, fit, plans, proof, and a demo or trial; return audience paths, capability-to-outcome mapping, transparent comparison, accessibility requirements, and validation metrics.From its SKILL.md

Install
npx -y skills add kfeng209-oss/cognitive-ux --skill cognitive-ux-product-marketing

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 28 days oldThe repository was created 28 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.5 KB, 427 tokens by cl100k_base, as published. Nobody here has run it

Cognitive UX: Product Marketing

Scope

Use for multi-page product marketing and plan evaluation. Use cognitive-ux-sales for one focused campaign; use cognitive-ux-commerce when the visitor purchases inventory.

Intake

  • Identify distinct audiences and their decision criteria.
  • Identify capabilities, differentiators, limits, pricing, and eligibility.
  • Identify trial/demo path, commitment details, and existing proof.

State assumptions that could change the design. Define the primary user task, its consequence of failure, and a measurable success outcome before proposing a layout.

Design procedure

  1. Define audience paths from their job-to-be-done rather than an internal feature taxonomy.
  2. Translate capabilities into observable outcomes, then link each claim to evidence or a clear limitation.
  3. Make plan comparison criteria, usage limits, price basis, renewal, and qualification discoverable before the CTA.
  4. Keep navigation predictable across features, use cases, pricing, security, and support; preserve orientation when visitors compare paths.
  5. Design the demo/trial handoff to explain what data is requested, what happens next, and how to exit.

Label each non-obvious recommendation as Standard / requirement, Evidence-informed default, or Hypothesis to test. Read archetype evidence before making research claims.

Required outputs

  • audience-path map
  • capability-to-outcome and proof ledger
  • plan comparison model
  • demo/trial handoff specification
  • task-based evaluation plan
  • Evidence-to-decision table: decision → mechanism → source → label → limitation → test metric.
  • Accessibility, ethics, and recovery-path checklist.

Guardrails

Do not bury pricing or material limits, present marketing claims as research, or use pressure to substitute for decision support.

Related skills

Use cognitive-ux-sales, cognitive-ux-docs, and cognitive-ux-onboarding. Do not combine multiple archetypes by default; select the primary user task and add another skill only when a secondary task is independently important.

What ships with it: 2 files

1.4 KB alongside SKILL.md

agents/

references/

Keep looking

Skills are one crate of 326,835. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.