agentsclimarketplace

Persona mapping

Skill Dragoon0x/product-skills/skills/research/persona-mapping

The product thinking layer for AI agents. 580 skills. 48 commands. 8 domains. - Product strategy, discovery, execution, analytics, growth, experience, conversion, communication and more.

Install
npx -y skills add Dragoon0x/product-skills --skill persona-mapping

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

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 3 stars3 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.

What its author says it does

Copied from the file, not written here

Build user models that actually inform decisions. Maps motivations, friction points, and decision triggers beyond demographic templates. Use when building for multiple user types or when the agent needs to reason about different users.

SKILL.md

1.6 KB, as published. Nobody here has run it

Persona Mapping

Build user models that actually inform decisions.

How to use

  • /persona-mapping Apply persona constraints to this conversation.

Constraints

What a Persona Must Include

  • Motivation: what drives them to seek this product
  • Context: when and where they encounter the problem
  • Current solution: what they do today (including doing nothing)
  • Decision trigger: what would make them switch
  • Success metric: how they'd know this product is working for them
  • NEVER include demographics unless they directly affect product behavior

What a Persona Must NOT Be

  • A demographic profile with a stock photo
  • An aspirational user you wish you had
  • A composite of all users (that's nobody)
  • Static. Personas should update as you learn more.

Usage Rules

  • MUST have no more than 3 primary personas for any product
  • MUST prioritize: which persona do you serve first?
  • SHOULD include an "anti-persona" (who this product is NOT for)
  • Every feature decision should reference which persona benefits
  • Conflicting persona needs MUST be resolved by priority, not by compromise

Anti-Patterns

  • Personas without behavioral differences (if they'd use the product the same way, they're one persona)
  • Creating personas before talking to real users
  • Personas that live in a document nobody reads
  • Designing for the edge case persona instead of the primary one

Keep looking

Skills are one crate of 328,083. 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.