CtrlK
BlogDocsLog inGet started
Tessl Logo

chengfeng-report-videocut-bug

整理、脱敏并上报 chengfeng-videocut 的 GitHub Bug。用户说上报 Bug、反馈剪口播问题、提交 GitHub Issue、这个问题告诉开发者,或要求继续提交已预览的 Bug 草稿时使用。不要用于功能建议、普通排错、代码提交或未获用户确认的自动上报。

79

Quality

100%

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

100%

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

The skill body is well-structured, executable, and concise, with a clear multi-step workflow reinforced by validation checkpoints and a feedback-driven failure section. Progressive disclosure is handled cleanly through a single real, well-signaled script.

DimensionReasoningScore

Conciseness

The body is lean and directive with no explanation of concepts Claude already knows; the dense PLUGIN_ROOT one-liner and JSON schema each earn their place rather than padding.

3 / 3

Actionability

Provides fully executable, copy-paste-ready commands ("node \"$REPORT\" draft ..." / "submit ..."), a concrete JSON input schema, and a routing table — no pseudocode or vague direction.

3 / 3

Workflow Clarity

A flow diagram plus five numbered sections sequence the process, with explicit validation checkpoints (脱敏预览 → 用户确认 → 认证/标签/查重) and feedback loops for confirmation_mismatch/expired/replayed in failure handling.

3 / 3

Progressive Disclosure

The body is an overview that clearly signals the single one-level-deep bundle file scripts/report-bug.cjs (verified present), with no nested references and content appropriately kept inline.

3 / 3

Total

12

/

12

Passed

Description

100%

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 concise, third-person, and fully answers both what and when with strong trigger-term coverage. An explicit exclusion clause further sharpens distinctiveness and reduces conflict risk.

DimensionReasoningScore

Specificity

Names three concrete actions — "整理、脱敏并上报 chengfeng-videocut 的 GitHub Bug" — rather than vague verbs, matching the anchor for multiple specific concrete actions.

3 / 3

Completeness

Explicitly states both what it does (整理、脱敏并上报 GitHub Bug) and when to use it ("用户说...时使用"), plus an explicit exclusion clause ("不要用于功能建议、普通排错、代码提交或未获用户确认的自动上报").

3 / 3

Trigger Term Quality

Lists several natural user phrases ("上报 Bug、反馈剪口播问题、提交 GitHub Issue、这个问题告诉开发者,或要求继续提交已预览的 Bug 草稿") giving good coverage of terms users would actually say.

3 / 3

Distinctiveness Conflict Risk

Tightly scoped to chengfeng-videocut bug reporting with distinct triggers and an explicit don't-use list, making it unlikely to fire for the wrong skill.

3 / 3

Total

12

/

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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
Agentchengfeng/chengfeng-videocut-skills
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.