
Hv Analysis
Structure deep research on a product, company, or market player with a vertical timeline plus horizontal competitive comparison before you commit to build.
Overview
hv-analysis is an agent skill most often used in Idea—competitors (also Validate—scope, Grow—content) that guides dual-axis research: lifecycle narrative plus competitive comparison.
Install
npx skills add https://github.com/kkkkhazix/khazix-skills --skill hv-analysisWhat is this skill?
- JSON schema for 纵轴 (full life timeline) and 横轴 (present-day competitive landscape)
- Meta block captures object type, one-line definition, domain, motive, and researcher context
- Origin section covers background, founders, seed events, and early product shape
- Keyed timeline nodes with decisions, external triggers, and downstream impact
- Stage-based lifecycle slices with core tensions, people, and decisions
- Dual-axis framework: vertical lifecycle plus horizontal competitive comparison
- Schema version 1.0
Adoption & trust: 1.8k installs on skills.sh; 14.1k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are evaluating a market or rival and your notes are a flat bullet list with no timeline, no tradeoffs, and no structured competitive contrast.
Who is it for?
Solo builders doing structured competitor dossiers, category maps, or founder/company deep dives before writing a spec or landing page.
Skip if: Teams that already have a signed PRD and only need implementation tasks, or anyone expecting automated web scraping instead of a research template.
When should I use this skill?
You need systematic research on a product, company, concept, or person with both history and competitive context.
What do I get? / Deliverables
You get a filled horizontal-vertical analysis artifact with origin story, milestone timeline, lifecycle phases, and competitive dimensions ready to inform scope and positioning.
- Completed HV analysis JSON dossier
- Timeline of key nodes with decisions and impacts
- Horizontal competitive comparison for the present moment
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Competitive and origin-story research belongs on the Idea shelf because solo builders use this framework before validation and implementation. The framework’s horizontal axis is explicit competitive contrast, so competitors is the canonical subphase even though it also supports broader research narratives.
Where it fits
Map three direct rivals on the horizontal axis while tracing how the category leader evolved on the vertical timeline.
Document why a niche tool exists today by filling origin, seed events, and phased pivots before you prototype.
Use lifecycle stage contradictions to decide which features are table-stakes versus differentiation for v1.
Turn the one-line definition and competitive gaps into launch messaging angles.
Refresh the horizontal comparison after a competitor ships a major release.
How it compares
Use instead of unstructured chat research when you want a repeatable dossier schema rather than one-off summaries.
Common Questions / FAQ
Who is hv-analysis for?
Indie and solo builders who research products, companies, or concepts before committing engineering time and need a consistent narrative-plus-competitive frame.
When should I use hv-analysis?
During Idea competitor and audience research, during Validate when scoping differentiation, and during Grow when refreshing positioning against new rivals.
Is hv-analysis safe to install?
It is a documentation and JSON template skill with no network or secret access by default; review the Security Audits panel on this page before installing any skill from the community.
SKILL.md
READMESKILL.md - Hv Analysis
{ "$schema": "横纵分析法 / Horizontal-Vertical Analysis Framework", "version": "1.0", "description": "一个用于系统性研究产品、公司、概念或人物的双轴分析框架。纵轴追踪完整生命历程,横轴展开当下竞争对比。", "meta": { "研究对象": { "名称": "string — 研究对象的名称", "类型": "enum: 产品 | 公司 | 概念 | 人物 | 其他", "一句话定义": "string — 用一句话说清楚这个东西是什么", "所属领域": "string — 所在行业/学科/赛道", "研究发起日期": "date — 开始研究的时间", "研究者": "string — 谁在做这个研究", "研究动机": "string — 为什么要研究它,触发点是什么" } }, "纵轴_生命历程": { "description": "从起源到当下的完整时间线,以叙事方式呈现,越详细越多元越好", "起源": { "诞生背景": "string — 它诞生时的时代背景、行业状态、技术环境", "诞生动机": "string — 为什么会出现?解决什么问题?填补什么空缺?", "创始人或发起者": { "是谁": "string", "背景经历": "string — 这些人之前做过什么,为什么是他们来做这件事", "初始愿景": "string — 他们最开始想做成什么样" }, "诞生时间": "date", "诞生地点或环境": "string", "早期形态": "string — 最初的样子是什么,跟现在有什么不同", "种子事件": "string — 有没有某个关键事件或灵感直接促成了它的诞生" }, "关键节点时间线": [ { "时间": "date", "事件名称": "string", "事件描述": "string — 发生了什么", "为什么重要": "string — 这个事件如何改变了后续走向", "决策与选择": "string — 在这个节点上做了什么选择,放弃了什么", "外部触发因素": "string | null — 是否由外部事件(政策、竞品动作、市场变化)触发", "结果与影响": "string — 这个事件的直接和间接后果" } ], "阶段划分": [ { "阶段名称": "string — 例如:萌芽期、快速增长期、转型期、成熟期", "时间跨度": "string — 起止时间", "核心特征": "string — 这个阶段最显著的特点是什么", "核心矛盾": "string — 这个阶段面临的最大挑战或内在张力是什么", "关键人物": ["string — 在这个阶段起关键作用的人"], "关键决策": ["string — 这个阶段做出的重大决策"], "阶段成果": "string — 这个阶段结束时交出了什么答卷" } ], "路径依赖分析": { "锁定性决策": ["string — 哪些早期决策锁定了后来的发展方向,难以逆转"], "错过的岔路口": ["string — 哪些关键时刻本可以走另一条路"], "自我强化机制": "string — 什么机制让它越走越深(网络效应、生态绑定、用户习惯等)" }, "叙事线索": { "主线故事": "string — 如果要用一个故事来概括整个历程,这个故事是什么", "反复出现的主题": ["string — 在不同阶段反复出现的模式、矛盾或主题"], "转折点": ["string — 最戏剧性的转折是什么"], "未解之谜": ["string — 还有哪些信息缺失,需要进一步挖掘"] } }, "横轴_竞争对比": { "description": "在当下这个时间截面上,与竞品/同类进行系统性横向对比", "分析时间截面": "date — 横向对比的基准时间点", "研究对象画像": { "当前定位": "string — 它现在把自己定义成什么", "核心能力": ["string — 它最强的几个点"], "核心短板": ["string — 它最弱的几个点"], "目标用户": "string — 它在服务谁", "商业模式": "string — 它怎么赚钱/怎么维持运转", "技术路线": "string — 底层技术选择是什么", "用户规模与增长": "string — 当前体量和增长趋势", "用户口碑": { "正面评价": ["string — 用户最常夸的点"], "负面评价": ["string — 用户最常骂的点"], "典型使用场景": ["string — 用户主要在什么场景下用它"] } }, "竞品列表": [ { "竞品名称": "string", "竞品类型": "enum: 直接竞品 | 间接竞品 | 潜在竞品 | 替代方案", "一句话定义": "string", "当前定位": "string", "核心能力": ["string"], "核心短板": ["string"], "目标用户": "string", "商业模式": "string", "技术路线": "string", "用户规模与增长": "string", "用户口碑": { "正面评价": ["string"], "负面评价": ["string"], "典型使用场景": ["string"] }, "与研究对象的关键差异": "string — 跟研究对象相比,最本质的区别是什么", "威胁程度": "enum: 高 | 中 | 低", "威胁分析": "string — 为什么构成这个程度的威胁" } ], "维度对比矩阵": { "description": "选择几个最关键的维度,把研究对象和所有竞品拉到一起比", "对比维度": [ { "维度名称": "string — 例如:性能、价格、易用性、生态、社区活跃度", "为什么选这个维度": "string — 这个维度为什么重要", "各方表现": { "研究对象": "string", "竞品A": "string", "竞品B": "string" } } ] }, "竞争格局判断": { "当前格局": "string — 现在是百花齐放、两强争霸、一家独大还是什么", "格局形成原因": "string — 为什么会是这个格局", "格局演变趋势": "string — 接下来可能往哪个方向走", "研究对象的位置": "string — 它在这个格局里处于什么位置" } }, "横纵交叉_洞察": { "description": "纵轴和横轴的交叉分析,这是横纵分析法最有价值的部分", "历史如何塑造了当下的竞争位置": "string — 纵向历程中的哪些决策和事件,决定了它今天在横向对比中的位置", "竞品的纵向对比": "string — 如果把竞品也放到时间线上看,它们的起源和演变有什么不同", "当前优势的历史根源": ["string — 它今天的每个优势,能追溯到历史上的哪个节点"], "当前劣势的历史根源": ["string — 它今天的每个劣势,能追溯到历史上的哪个决策"], "未来推演": { "基于纵向趋势的推演": "string — 如果延续当前的发展轨迹,接下来会怎样", "基于横向竞争的推演": "string — 竞争格局的变化会如何影响它", "最可能的剧本