CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

informal-launch-captions

为“非正式发布会”官方模板设计或修改全屏视频内的中英双语花字,包括渐变材质字、 流光、关键词动效、造型标签与实片排版。仅在选用该模板或用户明确要求该模板的 字幕风格时使用;不改变普通字幕的默认样式,不负责生成底层视频或配乐。

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

67%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 unusually dense, prescriptive instruction-only skill: it specifies fonts, sizes, timings, CSS mechanics, and a precise JSON contract, with two explicit pre-submit validation checks. Its main costs are systematic rule duplication between the usage and contract sections and the lack of a single worked HTML example showing what a compliant output looks like.

Suggestions

State each rendering rule once: keep the normative version in 文档与渲染契约 and reduce the 使用方式 and 实片排版 restatements of root opacity:1, render-from-0s, no-infinite, and screenCopy-once-only to brief pointers, cutting a substantial token block.

Add one compact worked example of a compliant output — a minimal HTML/CSS snippet for a gradient title group plus the filled-in JSON object — so the contract can be verified by pattern-match rather than reconstructed from constraints.

Promote the detailed rendering contract (units, exit attributes, html_js/GSAP rules) into a single one-level-deep reference file (e.g. references/rendering-contract.md) and keep an overview plus the pre-submit checklist in SKILL.md.

DimensionReasoningScore

Conciseness

There is no fluff and no re-teaching of known concepts (CSS keyframes, GSAP, background-clip are assumed), but key rules are systematically restated: root-container "opacity:1" appears in 使用方式, 实片排版, and 渲染契约; render-from-0s and the no-"infinite" rule appear twice (lines 23 and 76); screenCopy completeness/once-only appears twice (lines 21 and 75). This is more than minor trimmable over-explanation, so it fits 'mostly efficient but could be tightened' rather than 4.

3 / 5

Actionability

Guidance is highly concrete: named fonts (PingFang SC / Noto Sans CJK SC / Microsoft YaHei), numeric ranges (中文 3.5%–6.5%、英文 1.6%–2.4% of canvas width; 0.3–0.8s entrance; ≥约3s label reading), exact CSS mechanics (background-clip:text, animation-fill-mode:both/forwards, data-motion-exit values), a copy-paste-ready JSON output contract, and the window.__hf={duration,seek(t,o)} API. Not 5: no worked HTML/CSS example of an actual caption design, which is the skill's primary artifact.

4 / 5

Workflow Clarity

The flow is unambiguous ("直接设计当前字幕,并按文末契约返回 JSON,不输出计划或调用其他工具") and includes two explicit checkpoints: "核对一次 HTML 的全部可见文字…应与本次 screenCopy 完全相同" and "提交前检查入场、流光高光经过、稳定期与末态". Not 5: the sequence is embedded in prose rather than ordered steps, and there is no error-recovery loop for a failed check.

4 / 5

Progressive Disclosure

Five well-organized sections plus a semantic effects table, and every path mentioned exists at runtime (no skill bundle files are referenced; vendor/gsap.min.js is a runtime library). Not 5: at roughly 60 dense lines — above the simple-skill threshold — the detailed rendering contract and material/motion specifications could be split into a one-level-deep reference file.

4 / 5

Total

15

/

20

Passed

Description

92%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 tight, well-scoped description: it names the exact template, enumerates the concrete caption-design capabilities it covers, states an explicit use-only-when trigger condition, and fences off neighboring responsibilities. The only weakness is the absence of English-language trigger phrasings for a deliberately bilingual workflow.

DimensionReasoningScore

Specificity

"为'非正式发布会'官方模板设计或修改全屏视频内的中英双语花字,包括渐变材质字、流光、关键词动效、造型标签与实片排版" enumerates five concrete deliverable types (gradient-material type, light sweeps, keyword motion, look labels, footage layout) on top of the design/modify actions — comprehensive within the declared scope. Not 4: no visible coverage gaps inside that niche.

5 / 5

Completeness

Both halves are explicit: the "what" (design/modify bilingual on-video caption typography with the enumerated effects) and the "when" ("仅在选用该模板或用户明确要求该模板的字幕风格时使用"), reinforced by explicit exclusions (won't restyle normal captions, won't generate video or music). Not 4: the trigger condition is fully concrete, not merely present-but-vague.

5 / 5

Trigger Term Quality

Natural keywords are present — "花字", "字幕风格", "官方模板", "非正式发布会" — and would match how a user requests this skill. Not 5: despite the bilingual use case, no English trigger phrasings or further synonyms of the template name are included, so a few natural terms are missing.

4 / 5

Distinctiveness Conflict Risk

The skill is pinned to a single named official template and explicitly disclaims adjacent territory ("不改变普通字幕的默认样式,不负责生成底层视频或配乐"), giving it a clear niche with minimal risk of firing for generic caption or video skills. Not 4: the explicit non-goals remove even minor overlap with closely related skills.

5 / 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

agentscope-ai/QwenPaw

Path

plugins/apps/qwenpaw-creator/backend/skills/informal-launch-captions/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.