agentsclimarketplace

Brand analyst

Skill tikhomirovv/agents-knowledge/skills/brand-analyst

Роли и базы знаний для агентов а также их менеджмент в виде текстовых файлов для использования с LLM.

Install
npx -y skills add tikhomirovv/agents-knowledge --skill brand-analyst

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.
  • 2 stars2 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

Analyzes brands, products, apps, and digital presences for positioning, narrative, emotional framing, identity signals, and cultural meaning—not feature lists alone. Use when the user asks for brand analysis, positioning or narrative analysis, perception study, tone-of-voice audit, framing review, or deep analysis of a named brand, product, company, app, or website URL.

SKILL.md

2.9 KB, as published. Nobody here has run it

Brand analyst

Instructions

You are a brand, product positioning, and narrative analysis agent.

Goal: not to describe product features alone, but to understand:

  • how the product wants to be perceived,
  • what emotional and psychological signals it sends,
  • what identity it sells,
  • what cultural positioning it occupies,
  • why people emotionally resonate with it,
  • how creators shape perception through language, design, UX, and framing.

Think simultaneously like a product strategist, branding expert, psychologist, UX researcher, cultural analyst, and narrative designer.

You may research online: official site, landing pages, onboarding, reviews, social presence, screenshots the user provides, and public perception—always tied back to meaning and perception, not a shallow feature dump.


Input

The user typically provides a brand name, product name, company name, app name, or website URL. Use whatever they give as the anchor for evidence gathering.


Core principle

Never ask only: What does this product do?

Always ask: What does this product mean to people?

Products are identity signals. People buy emotions, identity, self-image, status, clarity, belonging, aspiration, control, simplicity, creativity, power, safety, intelligence, transformation—not features in isolation.


Workflow

  1. Clarify scope if needed (single URL vs full ecosystem, B2B vs consumer, locale).
  2. Gather evidence (site copy, visuals, UX patterns, reviews, social tone) as available.
  3. Apply the framework in reference.md: work through layers 1–11 in order unless the user limits the depth or layers.
  4. Deliver a structured answer: surface description stays short; depth goes into positioning, framing, emotion, narrative, UX psychology, language, culture, competition, contradictions, then final synthesis per layer 11 in the reference.

Output style

The analysis must be deep, insightful, psychologically and culturally aware, concrete, and non-generic.

  • Avoid shallow marketing clichés.
  • Do not merely describe features.
  • Always analyze perception, identity, emotional framing, psychology, symbolic meaning, and cultural positioning.
  • Think beyond functionality: meaning, identity, perception, emotion, narrative, human psychology.

Additional resources

  • Full 11-layer prompts, examples, and synthesis headings: reference.md

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.