CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

plan-deck-template

海岚旅行方案 PPT 模板(HL-MKT-TPL-08 V3.1):店里的 .pptx 品牌模板文件及其使用说明。方案 PPT 必须以此模板为底制作,委托设计同事时一并提供。

64

Quality

81%

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

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

An exemplary lean operational skill: a dense page-by-page inventory and unambiguous usage rules with a built-in completeness check. The structural weakness is reference integrity — the central template.pptx asset is missing from the bundle and the external specs lack paths.

Suggestions

Ship the actual template.pptx in the skill bundle (or correct the path to where it really lives) so the reference 「模板文件就在本目录下:template.pptx」 resolves.

Give the two spec documents concrete file paths or skill names (e.g., links to HL-MKT-SPEC-04 and HL-MKT-GUIDE-07) instead of title-only citations so navigation is one clear hop.

Move the V3.0/V3.1 changelog and the 2026-09-25 effective date into a short '版本记录' section so the operative guidance stays timeless.

DimensionReasoningScore

Conciseness

The body is lean and dense — a 19-row operational table and terse usage rules with zero explanation of concepts Claude already knows. The only trimmable material is the time-sensitive version/date changelog parenthetical (V3.0/V3.1 changes, effective 2026年9月25日), which is not placed in a deprecated/old-patterns section, so it falls just short of 'every token earns its place'.

4 / 5

Actionability

Fully concrete, instruction-only guidance covering the common cases: hand 「本目录的 template.pptx 路径连同需求单」 to the designer; cover/section/contact pages 「直接用模板的,只改文字」; content pages 「从最接近的模板页开始,替换文字,删去用不上的行、栏、站点,不留空位」; brand elements 「不重画、不改色」. Each directive is specific and executable.

5 / 5

Workflow Clarity

The 怎么用 rules give a clear implicit sequence (commission → base pages on template → replace all placeholders → delete unused elements → keep brand assets → follow specs), including an explicit completeness checkpoint (「一个也不能留下」). It falls short of the top anchor only because there is no final verification step (e.g., checking the finished deck against HL-MKT-SPEC-04 page order).

4 / 5

Progressive Disclosure

The SKILL.md itself is a well-organized overview (page inventory table plus usage rules) pointing one level out to the template and specs. However, the core referenced asset 「template.pptx」 claimed to be 就在本目录下 is absent from the bundle, and the two spec documents (《行程方案 PPT 规范》HL-MKT-SPEC-04, 《品牌与内容设计规范》HL-MKT-GUIDE-07) are cited by name/code without paths, so references are not fully resolvable or clearly signaled.

3 / 5

Total

16

/

20

Passed

Description

73%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 distinctive, well-scoped resource description that clearly identifies what the skill provides and when it applies. Its main weakness is that it names only a couple of usage actions and lacks natural trigger synonyms and an explicit 'Use when' phrasing.

Suggestions

Add an explicit trigger clause such as 「制作、修改或委托方案 PPT / 演示文稿时使用」 to convert the policy-style mandates into clear when-to-use guidance.

Include one or two more concrete actions (e.g., 按模板页型替换文字、删去用不上的栏位) and natural synonyms like 「幻灯片」「演示文稿」 to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the domain clearly (「.pptx 品牌模板」「方案 PPT」) and two concrete usage actions (「必须以此模板为底制作」「委托设计同事时一并提供」), but does not list several specific actions, matching the 'domain plus 1-2 concrete actions' anchor rather than the 'several specific actions' anchor above.

3 / 5

Completeness

Both 'what' (店里的 .pptx 品牌模板文件及其使用说明) and 'when' (方案 PPT 必须以此模板为底制作;委托设计同事时一并提供) are explicitly stated, but the 'when' is phrased as a policy mandate rather than explicit user-trigger phrasing ('Use when...'), so it fits 'both present, when could be more explicit' rather than the top anchor.

4 / 5

Trigger Term Quality

Good natural keyword coverage — 「方案 PPT」「PPT 模板」「.pptx」「品牌模板」 are phrases users would say — with the file extension included, but common synonyms like 「演示文稿」 or 「幻灯片」 are missing, so it falls just short of the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

Scoped to a single brand's proposal PPTs with a unique document code (HL-MKT-TPL-08 V3.1) and shop-specific vocabulary (海岚, 方案 PPT), giving it a clear niche with minimal risk of triggering for unrelated PPT or document skills.

5 / 5

Total

16

/

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

EverMind-AI/Raven

Path

experimental/simulation/scenarios/travel_agency/materials/plan-deck-template/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.