CtrlK
BlogDocsLog inGet started
Tessl Logo

hv-analysis

横纵分析法(Horizontal-Vertical Analysis)深度研究Skill。由数字生命卡兹克提出,融合了索绪尔的历时-共时分析、社会科学的纵向-横截面研究设计、商学院案例研究法与竞争战略分析的核心思想。 当用户想要系统性研究一个产品、公司、概念、技术或人物时使用。核心是双轴分析:纵轴追踪从诞生到当下的完整生命历程(以叙事故事呈现),横轴在当下时间截面上与竞品/同类进行系统性横向对比,最后交叉两条轴产出独到洞察。最终产出一份排版精美的PDF研究报告。 触发词包括但不限于:横纵分析、研究一下、帮我分析、深度研究、做个研究、调研一下、竞品分析、帮我看看这个东西怎么样、这个产品/公司/概念是怎么回事、帮我摸清楚、帮我搞懂、帮我做个deep research。 即使用户只是说"帮我了解一下XX"或"XX是什么来头",只要上下文暗示需要系统性的深度研究(而非简单的概念解释),都应该触发。也适用于用户丢来一个产品名、公司名、技术名词说"帮我研究一下这个"的场景。 不要用于简单的名词解释(用户只是问"XX是什么")、不要用于公众号写作(那个用khazix-writer)、不要用于纯标题摘要生成(用wechat-title)。

66

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./hv-analysis/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, actionable multi-step research workflow with explicit checkpoints and a quality checklist. Its main weaknesses are padding in the writing-style section and an orphaned reference file (references/schema.json) that is never linked from the body.

Suggestions

Condense the '写作风格' section into a short checklist of do/don't elements rather than re-explaining each rhetorical device at length; rely on Claude's competence to reduce token load (improves conciseness).

Reference the bundled output schema from the body — e.g. '报告字段结构见 references/schema.json' — so the report-output schema is discovered via progressive disclosure instead of remaining an orphaned file (improves progressive_disclosure).

Add an explicit validation checkpoint before PDF generation — e.g. 'Verify the first-line H1 and the 研究时间/所属领域/研究对象类型 meta line are present, and re-run md_to_pdf.py if WeasyPrint reports errors' — so the PDF step has a clear feedback loop (improves workflow_clarity).

DimensionReasoningScore

Conciseness

Mostly efficient task guidance, but the '写作风格' section re-explains style elements ('节奏感','层层剥开的修辞','文化升维','回环呼应') at length and the prose is discursive ('宁可写长写细,也不要蜻蜓点水'), adding padding beyond what Claude needs. Not 4 because the over-explanation is more than minor; not 2 because it does not explain basics Claude already knows and is not severely verbose.

3 / 5

Actionability

Provides concrete, copy-paste-ready commands ('pip install weasyprint markdown --break-system-packages','python [skill目录]/scripts/md_to_pdf.py input.md output.pdf --title … --author …', arxiv 'curl -s "https://export.arxiv.org/api/query?search_query=…"') covering common cases. Not 5 because sub-agent search prompts are described in prose rather than given as ready-to-paste templates; not 3 because the guidance is executable, not pseudocode.

4 / 5

Workflow Clarity

Clear 5-step sequence with explicit checkpoints ('信息充分性自检…信息不够就再补搜', a '质检清单' with checkboxes) and a re-search feedback loop; no destructive/batch cap applies since output is a generated report. Not 5 because there is no explicit validate-the-PDF-output step or recovery path if WeasyPrint fails; not 3 because checkpoints are explicit rather than implicit.

4 / 5

Progressive Disclosure

Good section structure and a clearly signaled script reference ('scripts/md_to_pdf.py'), but the bundled 'references/schema.json' (~7.8KB report-output schema) is never referenced from the body, and report-structure content that could point to it is inlined. Not 4 because the unreferenced bundle file is a real organization gap; not 2 because structure is reasonable, not minimal or buried.

3 / 5

Total

14

/

20

Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, trigger-rich, and explicitly answers both what and when, with clear negative boundaries against adjacent skills. It is a strong, well-targeted description with only minor specificity gaps.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('双轴分析','纵轴追踪从诞生到当下的完整生命历程','横轴…系统性横向对比','交叉两条轴产出独到洞察','产出一份排版精美的PDF研究报告'), with only minor coverage gaps. Not 5 because it does not give a full enumerated action inventory; not 3 because more than 1-2 actions are named.

4 / 5

Completeness

Explicitly answers both 'what' (双轴分析法→PDF研究报告) and 'when' ('当用户想要系统性研究一个产品、公司、概念、技术或人物时使用' plus concrete trigger phrases). Not 4 because the 'when' is explicit and specific rather than weakly implied.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases including colloquial synonyms and an English variant ('横纵分析','研究一下','帮我分析','深度研究','调研一下','竞品分析','帮我摸清楚','帮我搞懂','帮我做个deep research'). Not 4 because synonyms and user-natural variations are thoroughly covered.

5 / 5

Distinctiveness Conflict Risk

Clear niche with an explicit negative-boundary clause ('不要用于简单的名词解释…不要用于公众号写作…那个用khazix-writer…用wechat-title') that minimizes conflict risk. Not 4 because competing skills are explicitly excluded rather than merely having minor overlap.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
KKKKhazix/khazix-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.