huashu-md-to-pdf

将 Markdown 文档转换为专业的 PDF 白皮书，采用苹果设计风格。支持完整的 Markdown 语法（代码块、表格、引用、列表等）。自动生成封面、目录、页眉页脚。使用场景：技术文档、白皮书、教程、报告等需要专业排版的 Markdown 文档。

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./huashu-md-to-pdf/SKILL.md

Quality

Content

65%Weight 40%Scale 1-3

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

The body is highly actionable with executable commands and config, but is padded with restated feature lists and off-topic promotional content, lacks any output validation step, and references bundle files that do not actually exist.

Suggestions

Remove the self-promotional footer and the '核心功能' list that restates the description to tighten conciseness.

Drop or correct references to non-existent files (scripts/styles.css, templates/cover.html) — either extract them as real one-level-deep reference files or remove the misleading '脚本说明' entries.

Add a brief verification step (e.g. open/inspect the generated PDF, check page count or that the TOC resolved) so the workflow has an explicit checkpoint.

Dimension	Reasoning	Score
Conciseness	Most sections are efficient with concrete command and config snippets, but the '核心功能' list restates the description, the self-promotional footer ('花叔出品 \| 公众号「花叔」...') is off-topic padding, and some design-feature bullets repeat what the script already encodes.	2 / 3
Actionability	Provides copy-paste-ready, executable commands ('python scripts/convert.py input.md', 'pip3 install markdown2 weasyprint', 'brew install pango'), concrete CSS variable config, and FAQ fixes with exact syntax, fully matching the executable/example anchor.	3 / 3
Workflow Clarity	Steps are sequenced (依赖安装 → 使用方法 → 示例) but there is no validation/checkpoint confirming the PDF was produced or verifying output, leaving the sequence present but checkpoints missing for a generation workflow.	2 / 3
Progressive Disclosure	The body references 'scripts/styles.css' and 'templates/cover.html' as separate files, but neither exists in the bundle (only scripts/convert.py is present); they are described as embedded in the script, making the references misleading. Content is otherwise reasonably sectioned but largely inline for a 17KB-script skill.	2 / 3
	Total	9 / 12 Passed

Description

75%Weight 40%Scale 1-3

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 and distinctive with an explicit usage-scenario clause that answers both 'what' and 'when'. It would benefit from a more natural-language 'Use when...' trigger phrasing and a broader enumeration of user-sayable terms.

Suggestions

Add an explicit 'Use when...' trigger clause in user-natural phrasing (e.g. '当用户要把 Markdown 导出为 PDF、生成白皮书或专业排版文档时使用').

Enumerate common user-sayable trigger terms like 'Markdown 转 PDF', '导出 PDF', '生成白皮书' to improve trigger-term coverage.

List the discrete operations as concrete actions (convert, render code blocks/tables, generate cover, generate clickable TOC) to lift specificity toward a comprehensive action set.

Dimension	Reasoning	Score
Specificity	Names the domain ('将 Markdown 文档转换为专业的 PDF 白皮书') and several concrete actions ('自动生成封面、目录、页眉页脚'), but stays centered on a single conversion task rather than a comprehensive list of discrete operations, matching the anchor that names domain and some actions but is not comprehensive.	2 / 3
Completeness	It clearly answers 'what' (convert Markdown to Apple-style PDF whitepaper with cover/TOC/headers) and 'when' via the explicit '使用场景：技术文档、白皮书、教程、报告等' scenario clause, which functions as the required trigger guidance; not level 2 because the 'when' is explicit rather than merely implied.	3 / 3
Trigger Term Quality	Relevant natural terms appear ('Markdown', 'PDF 白皮书', '技术文档', '白皮书', '教程', '报告'), but there is no explicit 'Use when...' trigger phrasing and common variations a user would naturally say (e.g. '把 md 转成 pdf', '导出 PDF') are not enumerated, so coverage is partial.	2 / 3
Distinctiveness Conflict Risk	The niche (Markdown → Apple-design PDF whitepaper) is specific and clearly distinguishable from general document or PDF skills, with distinct triggers unlikely to fire for the wrong skill.	3 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: alchaincyf/huashu-skills
Path: huashu-md-to-pdf/SKILL.md
Commit: 35e7cf3

Reviewed: 12 days ago

Table of Contents

Discovery Implementation Validation

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.