CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

huashu-data-pro

数据分析与办公提效全能助手。覆盖数据处理、分析洞察、报告撰写、PPT制作、数据可视化的端到端工作流。 始终从专家视角出发,帮用户多想一步。遇到不确定的问题主动与用户确认。 支持:Excel数据分析、投放数据复盘、ROI测算、数据可视化、报告生成、PPT制作、公式生成。 当用户提到"分析数据"、"做报告"、"做PPT"、"Excel"、"投放分析"、"ROI"、"复盘"、 "周报"、"月报"、"数据处理"、"图表"、"可视化"、"汇报"、"表格"、"公式"时使用此技能。

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured overview that puts decision logic, constraints, and pitfalls in SKILL.md while delegating detailed workflows, templates, and style specs to real one-level-deep reference files. The main gaps are a dangling external reference in the index, a missing fix-and-retry loop after the generation self-check, and a promotional footer that wastes context tokens.

Suggestions

Remove or fix the two out-of-bundle references ("~/.claude/skills/image-to-slides/references/proven-styles-gallery.md" and the "design-philosophy" skill) — either inline the needed content as a local reference file or drop the rows, since the external path does not exist.

Turn the "生成后自检" checklist into a feedback loop: state explicitly that failed checks are fixed and re-verified before delivering the report.

Delete the promotional footer (author, public account, follower count, book titles) — it consumes context tokens with no operational value for executing the skill.

DimensionReasoningScore

Conciseness

The body is dense and token-efficient — decision tables, exact hex values, thresholds ("辅助文字≥10pt", "堆叠图<3%合并为「其他」"), and pitfall lists that are project-specific knowledge Claude would not already have. It is not 5 because the promotional footer ("花叔出品 | 公众号「花叔」| 30万+粉丝...") and the overlap among three philosophy sections (核心哲学/设计哲学/分析哲学) are tokens that do not earn their place; it is not 3 because nothing explains concepts Claude already knows.

4 / 5

Actionability

Concrete, executable guidance throughout: an exact playwright screenshot command with flags, named scripts ("scripts/html2pptx.js", "scripts/read_excel.py"), a specific dependency list with an auto-install policy, and precise design constraints. It is not 5 because the bulk of runnable code lives in the referenced files and the body itself contains only one complete command; it is not 3 because the inline guidance is specific and directly executable, not high-level hints.

4 / 5

Workflow Clarity

A clear sequence is present — format decision table → style selection → generation → "生成后自检" checklist — reinforced by "不确定时必须问" checkpoints and the 分析输出结构 template. It is not 5 because the self-check is a one-pass checklist with no explicit fix-and-retry feedback loop, and the detailed step-by-step workflows are delegated to references/workflows.md rather than sequenced with checkpoints inline; it is not 3 because validation checkpoints are explicit and the decision flow is unambiguous.

4 / 5

Progressive Disclosure

Good bundle structure: a "参考文件索引" table mapping needs to files, inline pointers at point of use, and all five referenced files (visual-design-system.md, report-style-gallery.md, html-templates.md, workflows.md, ad-analytics.md) present and one level deep. It is not 5 because two index entries point outside the bundle — "~/.claude/skills/image-to-slides/references/proven-styles-gallery.md" (verified nonexistent) and the "design-philosophy" skill — creating broken navigation; it is not 3 because references are clearly signaled with purpose and nothing that belongs in a separate file is inlined.

4 / 5

Total

16

/

20

Passed

Description

85%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 with explicit capabilities, an explicit use-when clause, and an unusually rich set of natural trigger phrases. The main weaknesses are the broad grab of generic office-productivity triggers (Excel, 做PPT, 图表) that raises conflict risk with specialized skills, and the absence of file-extension triggers.

Suggestions

Add file-extension triggers such as '.xlsx' and '.pptx' to the trigger list to reach full natural-term coverage.

Narrow or qualify the generic triggers (Excel, 做PPT, 图表, 表格) — e.g. tie them to the analysis/report context ("Excel投放数据分析") — to reduce overlap with dedicated spreadsheet or presentation skills.

Trim the soft behavioral claims ("始终从专家视角出发,帮用户多想一步") which describe attitude rather than capability and add tokens without adding trigger value.

DimensionReasoningScore

Specificity

The description lists seven concrete capabilities ("Excel数据分析、投放数据复盘、ROI测算、数据可视化、报告生成、PPT制作、公式生成") plus the end-to-end workflow scope, matching the comprehensive multi-action anchor. It is not 4 because coverage of the domain's actions is comprehensive rather than having minor gaps, and the vague framing ('全能助手') is confined to the opening line.

5 / 5

Completeness

Both questions are answered explicitly: 'what' via "覆盖数据处理、分析洞察、报告撰写、PPT制作、数据可视化的端到端工作流" and "支持:Excel数据分析、投放数据复盘、ROI测算...", and 'when' via "当用户提到'分析数据'、'做报告'...时使用此技能" with concrete trigger phrases — a textbook match for the top anchor.

5 / 5

Trigger Term Quality

Fifteen natural Chinese trigger phrases including synonym clusters ("做报告"/"汇报"/"周报"/"月报", "图表"/"可视化") give excellent keyword coverage a user would actually say. It falls short of the 5 anchor because file extensions (.xlsx, .pptx) are absent from the trigger list, unlike the anchor-5 example which includes them.

4 / 5

Distinctiveness Conflict Risk

The ad-analysis niche terms ("投放分析", "ROI", "复盘") are distinctive, but the skill also claims generic territory ("Excel", "做PPT", "图表", "表格", "公式", "周报") that would collide with any dedicated spreadsheet, presentation, or visualization skill. It is not 4 because 'Excel' and '做PPT' are triggers nearly any office-productivity skill would also claim; it is not 2 because the 投放/复盘 marketing-analysis framing gives it a real niche.

3 / 5

Total

17

/

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

alchaincyf/huashu-skills

Path

huashu-data-pro/SKILL.md

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.