CtrlK
BlogDocsLog inGet started
Tessl Logo

user-guide

HanaAgent 用户说明书。解答用户关于软件使用方法、功能介绍、常见问题和实用技巧的疑问。 MANDATORY TRIGGERS: 怎么用, 使用方法, 说明书, 帮助文档, 新手指南, 怎么设置, 功能介绍, how to use, user guide, help, getting started, 教程, tutorial, 这是什么功能, 怎么操作

58

Quality

68%

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

Fix and improve this skill with Tessl

tessl review fix ./skills2set/user-guide/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 comprehensive, well-structured, and highly concrete reference manual that gives Claude what it needs to answer user questions about HanaAgent. Its weaknesses are significant redundancy (the tips section and FAQ restate earlier content) and the absence of any progressive disclosure into separate reference files despite the document's length.

Suggestions

Remove or collapse section 十四 (实用技巧), since nearly every tip duplicates content already covered in sections 二–十一; cross-reference instead of restating.

Split the long-tail detail (Yuan cognitive frameworks, theme list, full FAQ) into one-level-deep reference files under references/ and link to them from SKILL.md to improve progressive disclosure.

Trim conversational/marketing prose (e.g. '住在你电脑里的伙伴', the OpenClaw comparison table) to leaner reference phrasing that assumes the reader's competence.

DimensionReasoningScore

Conciseness

Noticeably verbose: section 十四 (实用技巧) restates ~10 items already covered in earlier sections (skills, scripts, /xing, multi-Agent, desk linkage, remote, pinned memory, /compact, /rc, vision bridge), the FAQ repeats Owner/vision/MCP answers, and conversational analogies ('住在你电脑里的伙伴') pad the context.

2 / 5

Actionability

Concrete, specific guidance throughout: exact settings paths ('设置 → 供应商'), slash commands (/compact, /rc, /exitrc), keyboard shortcuts (Shift+Enter, Cmd/Ctrl+click), and file paths (.hanako/, HANA_HOME), with only minor descriptive gaps.

4 / 5

Workflow Clarity

Embedded procedures (首次打开 setup, 电脑控制开启方法) are clearly numbered, but the bulk is reference material rather than sequenced workflows, and no validation checkpoints appear because no destructive/batch operations are described.

3 / 5

Progressive Disclosure

Well-sectioned with 14 numbered headers plus FAQ, but everything is inlined in a single ~560-line file with no bundle files; detailed sections (Yuan cognitive frameworks, theme variants, full FAQ) could be split into one-level-deep references.

3 / 5

Total

12

/

20

Passed

Description

86%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 strong: it states what the skill does, provides a comprehensive bilingual set of natural trigger terms, and gives explicit 'when to use' guidance in third person. Its main weakness is that the 'what' is expressed as question categories rather than concrete actions.

DimensionReasoningScore

Specificity

Names the domain (HanaAgent user guide) and lists four question categories ('使用方法、功能介绍、常见问题和实用技巧'), but these are topic areas rather than concrete actions, and coverage is not comprehensive.

3 / 5

Completeness

Explicitly answers both 'what' ('解答用户关于软件使用方法、功能介绍、常见问题和实用技巧的疑问') and 'when' via the MANDATORY TRIGGERS clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural trigger terms across Chinese and English with synonyms ('怎么用', '使用方法', '说明书', '新手指南', 'how to use', 'user guide', 'getting started', '教程', 'tutorial'), matching the anchor for full coverage including synonyms.

5 / 5

Distinctiveness Conflict Risk

A user guide for a specific software (HanaAgent) is a clear niche with mostly distinct triggers; minor overlap risk from generic terms like 'help' and 'tutorial'.

4 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (568 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository
liliMozi/openhanako
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.