CtrlK
BlogDocsLog inGet started
Tessl Logo

qwen3-tts-local

内容创作者与影片与视频编辑在制作视频配音、有声书或无网环境朗读时,请用此技能一键生成多语言、多音色的本地高质量音频。基于Edge-TTS引擎,零配置完全离线,高效产出专业级语音,彻底告别网络限制。

53

Quality

60%

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 ./skills/qwen3-tts-local/qwen3-tts-local/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 skill is well-organized with real, clearly-linked bundle files and concrete voice IDs, but it never shows how to invoke its own scripts, its workflow is descriptive rather than instructional, and the inline voice tables duplicate the reference file. Tightening the duplication and adding an executable generation command would move it from adequate to strong.

Suggestions

Add an executable invocation example for the bundled scripts (e.g. "python scripts/tts_generator.py --text '...' --voice zh-CN-XiaomengNeural --out out.mp3" plus the audio_processor equivalent) so Claude can act without opening the script files.

Remove the inline 音色列表 tables from SKILL.md and point to references/voice-guide.md instead — the duplication inflates token cost and risks the two lists drifting apart.

Replace the abstract 工作流程 ('服务自动执行') with a concrete, ordered procedure including how to verify the output file was generated (e.g. check file exists and is non-empty), and drop the duplicated zero-dependency/offline claims from the 注意事项 section.

DimensionReasoningScore

Conciseness

The body is mostly efficient (tables, short bullets) but contains clear redundancy: "零依赖" and offline claims appear in both 核心功能 and 注意事项; "首次下载后无需网络" is stated twice; and the inline 音色列表 tables duplicate content already in references/voice-guide.md. The 技术说明 section's ❌/✅ comparison is partially padding. It fits anchor 3 — mostly efficient with unnecessary material that could be tightened.

3 / 5

Actionability

There is concrete material — install commands ("pip install edge-tts", "edge-tts --help"), concrete voice IDs, and natural-language usage examples — but the critical execution step is missing: nowhere does the body show how to actually run the bundled scripts (no "python scripts/tts_generator.py --text ... --voice ..." invocation). The 工作流程 section describes what the 'service' does automatically rather than instructing Claude what to do, leaving the core action incomplete.

3 / 5

Workflow Clarity

The 工作流程 lists a 4-step sequence (文本分析 → 音色选择 → 语音生成 → 结果验证) but the steps are abstract labels with no commands, and "服务自动执行" gives Claude no executable sequence. '结果验证' is mentioned as a step name but no validation checkpoint or command is defined, matching anchor 3 (steps listed but checkpoints missing or implicit).

3 / 5

Progressive Disclosure

The 资源索引 section clearly signals one-level-deep, verified references ([scripts/tts_generator.py](scripts/tts_generator.py), [scripts/audio_processor.py](scripts/audio_processor.py), [references/voice-guide.md](references/voice-guide.md) — all exist on disk), but the large inline voice tables duplicate references/voice-guide.md content, i.e. material that belongs in the separate file is inlined in SKILL.md. That matches anchor 3 (structure present, but content that should be separate is inline).

3 / 5

Total

12

/

20

Passed

Description

70%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 solid description with an explicit trigger clause and natural scenario keywords, though the capability list is thinner and more marketing-flavored than the best examples, and the 'fully offline' claim is an over-claim contradicted by the skill's own technical notes. Clear what/when pairing makes it actionable for triggering.

DimensionReasoningScore

Specificity

The description names the domain (local TTS audio) and 1-2 concrete actions — "一键生成多语言、多音色的本地高质量音频" and "基于Edge-TTS引擎" — but coverage is not comprehensive and the phrasing carries marketing fluff ("一键", "高效产出专业级语音", "彻底告别网络限制") rather than more distinct concrete capabilities. It sits between anchor 3 (domain plus 1-2 actions) and anchor 4 (several specific actions), closer to 3 because the action list is thin and padded.

3 / 5

Completeness

Both 'what' and 'when' are present: the trigger clause "在制作视频配音、有声书或无网环境朗读时,请用此技能" is an explicit 'use when' with concrete scenarios, and the 'what' is generating multi-language, multi-voice local audio. It falls short of anchor 5 because the 'what' is diluted by over-claims — notably "零配置完全离线" / "彻底告别网络限制", which the skill body itself contradicts (the 技术说明 section admits it uses Microsoft's online TTS service).

4 / 5

Trigger Term Quality

Good natural keyword coverage: "视频配音" (video voiceover), "有声书" (audiobook), "朗读" (read aloud), "无网环境" (offline environment), "多语言", "多音色" — phrases a user would naturally say. A few common terms are missing, e.g. "语音合成" / "文字转语音" / "TTS" / English equivalents, which keeps it below anchor 5.

4 / 5

Distinctiveness Conflict Risk

The niche is fairly clear — local Edge-TTS-based speech generation for voiceover/audiobook/offline narration — with distinct triggers unlikely to fire for unrelated skills. Minor overlap risk with other audio/TTS or audio-processing skills keeps it just below anchor 5.

4 / 5

Total

15

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
anbeime/skill
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.