CtrlK
BlogDocsLog inGet started
Tessl Logo

jianying-editor

剪映 (JianYing) AI自动化剪辑的高级封装 API (JyWrapper),提供开箱即用的 Python 接口,支持录屏、素材导入、字幕生成、Web 动效合成及项目导出。全面适配 MacOS (Apple Silicon/Intel) 与 Windows,支持 v5.9+ (draft_info.json) 架构、工程自修复、智能配音字幕及录屏变焦。

52

Quality

58%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Failed to scan

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured and offers genuinely executable core guidance (quick-start plus scripts/ commands), but it is undermined by pervasive references to bundle files that do not exist, a duplicated rule, and no explicit validation checkpoint in the workflow. Reconciling the link map with the real bundle is the highest-impact fix.

Suggestions

Reconcile references with the actual bundle: the referenced docs/, rules/ (11 files), examples/ (8 files), prompts/, and tools/ directories are absent — either add these files or remove/rewrite the links so every referenced path resolves; also link the existing references/ directory which is currently orphaned.

Remove the duplicated script-location rule (it appears in both CRITICAL DEVELOPER RULES and 脚本存放位置规范) to reclaim tokens.

Add an explicit validation checkpoint to the quick-start workflow (e.g., run scripts/api_validator.py and inspect the draft with draft_inspector.py before save/export) since this skill performs batch and destructive operations.

DimensionReasoningScore

Conciseness

The body avoids explaining concepts Claude already knows, but the "禁止在 Skill 内部目录创建脚本" rule is stated verbatim twice (CRITICAL DEVELOPER RULES #1 and 脚本存放位置规范) and the 10-path skill-root probe in the quick-start could be tightened, so it is mostly efficient with some redundancy.

2 / 3

Actionability

The quick-start Python code and the scripts/ CLI commands are concrete and copy-paste ready, but a large share of the routing points to files that do not exist (rules/*.md, examples/*.py, docs/*.md, tools/recording/recorder.py), so substantial concrete guidance is incomplete as written.

2 / 3

Workflow Clarity

The quick-start gives a numbered 1-5 sequence, but there are no explicit validation checkpoints or a validate->fix->retry loop, and the Acceptance Checklist it relies on lives in the missing docs/agent-playbook.md — destructive/batch operations therefore lack verification, capping this at 2.

2 / 3

Progressive Disclosure

Sections are clearly organized and one-level-deep in form, but scored against the actual bundle: docs/, rules/, examples/, prompts/, and tools/ are referenced yet absent, while the existing references/ directory is never linked, so navigation resolves only for scripts/ and is broken for the rest.

2 / 3

Total

8

/

12

Passed

Description

67%

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 specific and distinctive about a well-defined niche, but it lacks any explicit "when to use" trigger guidance and is padded with internal technical jargon that weakens trigger-term quality. Adding a Use-when clause and trimming implementation details would lift completeness and trigger quality.

Suggestions

Add an explicit 'Use when...' clause (e.g., use when automating JianYing/剪映 editing, generating drafts, batch-exporting, or adding subtitles/voiceover) to satisfy the completeness requirement.

Move internal jargon out of the description — JyWrapper, v5.9+ draft_info.json architecture, Apple Silicon/Intel belong in the body — and keep natural user-facing terms (剪映, JianYing, video editing automation, subtitle/TTS generation).

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "录屏", "素材导入", "字幕生成", "Web 动效合成", "项目导出" — matching the anchor for several specific concrete actions rather than vague language.

3 / 3

Completeness

It clearly answers "what" (the listed actions plus platform/version support) but has no "Use when..." clause or equivalent explicit trigger guidance, which the guidelines cap at 2.

2 / 3

Trigger Term Quality

Natural terms like "剪映", "JianYing", "剪辑", "录屏", "字幕", "配音" appear, but they are padded with technical jargon a user would not say ("JyWrapper", "v5.9+ (draft_info.json) 架构", "Apple Silicon/Intel") and common natural variations are missing.

2 / 3

Distinctiveness Conflict Risk

It names a clear, narrow niche (剪映/JianYing video-editing automation) with distinct triggers unlikely to overlap with other skills.

3 / 3

Total

10

/

12

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

relative_links

Relative link issues: 22 missing

Warning

Total

15

/

16

Passed

Repository
luoluoluo22/jianying-editor-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.