CtrlK
BlogDocsLog inGet started
Tessl Logo

hv-analysis

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

71

Quality

89%

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

SKILL.md
Quality
Evals
Security

Quality

Content

77%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 content is a highly actionable, well-sequenced research workflow with strong validation checkpoints (sufficiency self-checks and a delivery checklist) and copy-paste-ready commands. Its main weaknesses are moderate verbosity (CSS details duplicated from the bundled script) and progressive-disclosure gaps: the provided references/schema.json is never linked from SKILL.md while style-guide content that could live in a reference is inlined.

Suggestions

Reference references/schema.json from the body (e.g., in 第一步/第二步: '分析结构字段见 references/schema.json') so the bundled analysis schema is discoverable instead of orphaned.

Trim the '脚本内置的排版规范' section to a one-line pointer ('排版已内置,无需手动调整;细节见 scripts/md_to_pdf.py') — the CSS color/font/margin details duplicate the script itself.

Move the 写作风格 guide into a references/ file (e.g. references/writing-style.md) and keep a short summary plus the 绝对禁区 list in SKILL.md; this also resolves the dangling 'khazix-writer skill' reference.

DimensionReasoningScore

Conciseness

The body is mostly efficient, purpose-built guidance (word-count targets, forbidden-phrase lists, A/B/C competitor branching), but includes unnecessary padding: the "脚本内置的排版规范" section enumerates the script's internal CSS ("H1标题=#1a5276深蓝、H2=#1e8449绿色..."、页眉、页脚) even while stating "无需手动调整", duplicating what already lives in md_to_pdf.py, and per-section 篇幅 guidance is repeated again in the 篇幅总览 table. This matches the score-3 anchor (mostly efficient with some unnecessary explanation that could be tightened) rather than 4, where such redundancy would be only minor.

3 / 5

Actionability

Guidance is copy-paste ready throughout: exact install command ("pip install weasyprint markdown --break-system-packages"), a ready-to-embed sub-agent prompt block including a concrete arxiv API call ("curl -s \"https://export.arxiv.org/api/query?search_query=all:关键词1+AND+all:关键词2&max_results=10\""), a concrete conversion invocation with arguments, explicit per-section word ranges, scene A/B/C branching rules, a report structure template, and file-naming conventions. This matches the score-5 anchor (fully executable commands covering common cases); nothing here is pseudocode or vague.

5 / 5

Workflow Clarity

The five-step sequence (前置准备 → 第一步信息收集 → 第二步纵向 → 第三步横向 → 第四步交汇 → 第五步PDF生成) is clearly ordered, and validation is explicit with feedback loops: the 信息充分性自检 ("信息不够就再补搜。不要凑合。"), source-priority rules, and a 13-item 质检清单 before delivery. This matches the score-5 anchor (clear sequence, explicit validation steps, error-recovery loops, checklist for a complex process).

5 / 5

Progressive Disclosure

The bundle provides references/schema.json and scripts/md_to_pdf.py, and the script is clearly and repeatedly referenced from the body — but references/schema.json is never mentioned anywhere in SKILL.md, leaving a whole detailed analysis-structure file orphaned and unnavigable. Meanwhile, sizable content that belongs in a reference file (the ~45-line 写作风格 guide, the inlined CSS 排版规范) is inlined in SKILL.md, and the body points to an external non-bundled skill ("详细定义请参考 khazix-writer skill") which slightly contradicts its own claim that the style guide is built in. This matches the score-3 anchor (some structure, references not clearly signaled, content that should be separate is inline); it is not 4 because a provided reference file is entirely unreachable from the overview.

3 / 5

Total

16

/

20

Passed

Description

96%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.

A strong description: it explicitly states what the skill does (dual-axis analysis producing a polished PDF report) and when to use it, with an unusually rich set of natural trigger phrases and explicit negative boundaries against sibling skills. The only weakness is that several of its trigger phrases are generic enough to overlap with other general research skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions covering the full pipeline: "纵轴追踪从诞生到当下的完整生命历程(以叙事故事呈现)", "横轴在当下时间截面上与竞品/同类进行系统性横向对比", "交叉两条轴产出独到洞察", and "最终产出一份排版精美的PDF研究报告". Coverage is comprehensive across the skill's four capability stages, matching the score-5 anchor; it is not the level-4 anchor because no capability stage is missing.

5 / 5

Completeness

Both 'what' and 'when' are answered explicitly and concretely: what is stated via the dual-axis description and PDF deliverable; when is stated via "当用户想要系统性研究一个产品、公司、概念、技术或人物时使用", an explicit trigger-word list, implicit-context guidance, and explicit negative boundaries ("不要用于简单的名词解释...不要用于公众号写作...不要用于纯标题摘要生成"). This matches the score-5 anchor exactly; the level-4 anchor's weaker 'when' does not apply.

5 / 5

Trigger Term Quality

Trigger coverage is comprehensive and natural, including many colloquial synonyms a Chinese-speaking user would actually say: "研究一下", "帮我分析", "深度研究", "做个研究", "调研一下", "竞品分析", "帮我摸清楚", "帮我搞懂", "帮我做个deep research", plus edge phrasings like "帮我了解一下XX" and "XX是什么来头". This matches the score-5 anchor (comprehensive natural terms including synonyms), well above the 4 anchor which expects missing terms.

5 / 5

Distinctiveness Conflict Risk

It carves a clear niche (横纵分析法 deep research) and explicitly disambiguates against named sibling skills ("不要用于公众号写作(那个用 khazix-writer)", "不要用于纯标题摘要生成(用 wechat-title)"), but broadly applicable trigger phrases like "帮我分析", "深度研究", "调研一下" retain some overlap risk with other general research/analysis skills not named here. This sits between the 4 anchor (mostly distinct, minor overlap with closely related skills) and the 5 anchor; it is not 5 because those generic research triggers could still route to a different research skill.

4 / 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.

Validation — 16 / 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.