CtrlK
BlogDocsLog inGet started
Tessl Logo

character-scene-extractor

角色和场景提取的规范与方法

54

Quality

61%

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/extractor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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-organized, concise, and gives a clear ordered workflow with named tools and field specs. Its main gaps are the absence of example tool invocations and an explicit verification step before the batch save operations.

Suggestions

Add one example tool invocation with expected arguments/return shape for read_script_for_extraction and save_dedup_characters so the guidance is copy-paste ready.

Insert an explicit verification checkpoint after extraction and before saving (e.g., '确认提取的角色/场景均为当前集真实涉及,且无重复') to close the batch-operation validation gap.

Clarify how to decide reuse-vs-create when names differ slightly (aliases/variants) to make the dedup rule more actionable.

DimensionReasoningScore

Conciseness

The body is lean: field lists with brief annotations, a 6-step workflow, and short rules, with no padding or explanation of concepts Claude already knows — every section earns its tokens, matching the 'lean and efficient' anchor.

3 / 3

Actionability

It names concrete tools (read_script_for_extraction, save_dedup_characters, etc.) and specific field specs with word counts, but shows no example tool invocations or argument shapes, so guidance is concrete yet incomplete — the level-2 anchor rather than copy-paste-ready level 3.

2 / 3

Workflow Clarity

The six steps are clearly sequenced and include a dedup/reuse rule, but there is no explicit verification checkpoint (e.g., confirm extracted entities match the current episode) for the batch save operations, which the rubric caps at 2 for batch/destructive workflows.

2 / 3

Progressive Disclosure

The skill is under 50 lines with no external references needed, and content is well-organized into clearly labeled sections (角色/场景/道具提取规范, 使用步骤, 当前集规则), meeting the simple-skill allowance for a top score on organization alone.

3 / 3

Total

10

/

12

Passed

Description

50%

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 identifies the skill's domain and core action but is terse and lacks both a comprehensive action list and an explicit 'use when' trigger clause. It is adequate but would benefit from concrete capability verbs and trigger guidance.

Suggestions

Add concrete actions the skill performs, e.g. '读取剧本并提取角色、场景、道具,复用已有数据并关联到当前集' to raise specificity.

Append an explicit trigger clause such as '当需要为某一集剧本补齐角色和场景时使用' to answer the 'when' question and improve completeness.

Include more natural trigger terms (道具, 剧本, 当前集, 去重) to broaden trigger-term coverage and reduce overlap with generic extraction skills.

DimensionReasoningScore

Specificity

The description names the domain ('角色和场景提取') and one action ('提取' / extraction) plus '规范与方法', but does not enumerate multiple concrete actions like save, dedup, or associate, so it lands at the 'names domain and some actions' anchor rather than the comprehensive level 3.

2 / 3

Completeness

It states what the skill does (character and scene extraction norms/methods) but provides no 'Use when...' clause or equivalent trigger for when Claude should invoke it, so 'when' is missing rather than explicit — exactly the level-2 anchor.

2 / 3

Trigger Term Quality

It surfaces relevant natural terms ('角色', '场景', '提取') a user might say, but offers no common variations or related terms (e.g., 道具/props, 剧本/script), matching the 'some relevant keywords but missing common variations' anchor.

2 / 3

Distinctiveness Conflict Risk

'角色和场景提取' targets a reasonably specific niche, but without explicit triggers or mention of the script/episode context it could still overlap with broader extraction skills, fitting the 'somewhat specific but could still overlap' anchor rather than the clearly-distinct level 3.

2 / 3

Total

8

/

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

description_field

'description' is very short (13 chars), consider making it more detailed

Warning

Total

15

/

16

Passed

Repository
chatfire-AI/huobao-drama
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.