theory-analysis-product-positioning

Code cross-source evidence into structured product-positioning insights with JSON and Markdown outputs.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/TimLai666/skills --skill theory-analysis-product-positioning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: theory-analysis-product-positioning
Source: https://github.com/TimLai666/skills/tree/main/theory-analysis-product-positioning
Command: npx skills add https://github.com/TimLai666/skills --skill theory-analysis-product-positioning

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Analysts can convert diverse cross-source evidence into a consistent, structured product-positioning view with traceable quotes and optional theory_annotations for downstream integration.

Core Features & Use Cases

  • Code evidence into four dimensions: attributes, functions, benefits, and usage context.
  • Export theory_annotations compatible with review-mining-stp for downstream analysis.
  • Support multiple sources (interviews, customer tickets, social posts, notes) with references for grounding.
  • Produce JSON and Markdown outputs suitable for reports and dashboards.

Quick Start

Provide analysis_goal and evidence_items (with item_id, content, and content_type) to generate structured JSON and Markdown outputs.

Frequently Asked Questions about theory-analysis-product-positioning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze product positioning from multi-source evidence like interviews and support tickets?

Analyzing product positioning from multi-source evidence requires coding diverse inputs into consistent dimensions. This Skill processes interviews, support tickets, and posts to code cross-source evidence into structured attributes, functions, benefits, and usage context insights.

What is theory_annotations export for product positioning analysis?

Theory_annotations export provides structured metadata compatible with downstream STP analysis. When coding cross-source evidence into product positioning insights, this optional export enables traceable integration with review-mining-stp for further downstream analysis.

How to code evidence into product positioning dimensions consistently?

To code evidence into product positioning dimensions, provide an analysis goal and evidence items with item IDs, content, and content type. The Skill codes these into four structured dimensions: attributes, functions, benefits, and usage context, producing JSON and Markdown outputs.

Can I use cross-source evidence coding for social media posts and notes?

Cross-source evidence coding supports social media posts and notes alongside interviews and support tickets. You provide item content and content type, and optionally source type and context tags, to generate structured product positioning insights with traceable references.

Do I need specific input formats to generate structured product positioning insights?

Generating structured product positioning insights requires an analysis goal and evidence items containing item ID, content, and content type. Optional fields like source type, source reference, and context tags enhance grounding but are not required to produce JSON and Markdown outputs.

What is the best way to convert diverse customer feedback into a structured STP view?

Converting diverse customer feedback into a structured STP view involves cross-source evidence coding across four dimensions. This approach builds a consistent product positioning perspective with traceable quotes and optional theory annotations for downstream integration.