CtrlK
BlogDocsLog inGet started
Tessl Logo

historical-interview-scripts

自媒体创作者在策划历史名人访谈短视频时,当需要融合古今反差与网络热梗打造爆款,使用本技能可自动生成包含吸睛标题、主持人串词与爆笑问答的完整结构化脚本,轻松产出高传播力的趣味短视频文案。

62

Quality

73%

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/historical-interview-scripts/historical-interview-scripts/SKILL.md
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.

A well-structured, highly actionable instruction skill: clear workflows with feedback loops, a precise output template, and an excellent progressive-disclosure layer with real, well-linked reference files. Its main weakness is redundancy — the skill brief and constraints are repeated across multiple sections and the single-agent mode duplicates the 4-agent flow, inflating token cost without adding guidance.

Suggestions

Merge the 角色设定/核心技能 sections into 任务目标 and fold 注意事项 into 约束条件 — these currently restate the same brief and constraints almost verbatim, costing ~40 lines of tokens.

Compress the 单一智能体模拟协作模式 section to a one-line note pointing at the 4-step standard flow (it currently re-walks the identical sequence) or move it into references/multi-agent-collaboration.md.

Make the 质量检查 step concretely checkable: replace qualitative items like '验证幽默感是否自然' with the QC agent's existing four criteria (历史准确性/娱乐性/传播性/制作友好性) as an explicit checklist with pass conditions.

DimensionReasoningScore

Conciseness

Mostly efficient — no space is wasted explaining concepts Claude already knows — but the same brief is restated three times (任务目标 vs 角色设定/核心技能, and 注意事项 duplicating 约束条件 almost verbatim) and the single-agent simulation section re-walks the 4-agent flow, so it clearly could be tightened; not a 2 because each individual section is reasonably tight rather than padded.

3 / 5

Actionability

Concrete, executable guidance throughout: a fully specified output-format template, named memes ("破防了", "栓Q", "榜一大哥"), illustrative constraints ("镜头给到苏轼一个无语的白眼特写"), and three usage examples — matching the 'mostly executable, minor gaps' anchor; a 5 is withheld because a complete worked script example is delegated to references rather than shown inline.

4 / 5

Workflow Clarity

A clear 4-step standard flow (理解需求→素材准备→文案创作→质量检查) with optional branches, a mode-selection table, and a quality checkpoint with an explicit feedback loop ("如不达标,返回至创作阶段微调") matches the score-4 anchor; not a 5 because the checkpoints (e.g., "验证幽默感是否自然") are qualitative and lack explicit checklist criteria or error-recovery detail.

4 / 5

Progressive Disclosure

Verified against the actual bundle: all six referenced files exist, links are well-signaled in text and consolidated in an annotated 资源索引 section, and details (agent roles, full pipeline, character/meme libraries) are appropriately split into one-level-deep references — good structure with only minor organization gaps from the redundant inline sections (duplicated constraint lists and role definitions), which keeps it below the clean score-5 anchor.

4 / 5

Total

15

/

20

Passed

Description

78%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 strong description: it names the audience, an explicit trigger condition, and concrete deliverables (title, host transitions, Q&A script) in a distinct niche, written in third person without fluff. It could reach the top anchor by adding a couple of natural trigger synonyms and slightly more explicit trigger phrasing.

DimensionReasoningScore

Specificity

Names concrete deliverables — "完整结构化脚本" broken into "吸睛标题、主持人串词与爆笑问答" — which matches the anchor for several specific actions with minor coverage gaps (output format and multi-character scope are only implied), not comprehensive enough for a 5.

4 / 5

Completeness

Both 'what' (generates a complete structured script with named components) and an explicit 'when' ("在策划历史名人访谈短视频时,当需要融合古今反差与网络热梗打造爆款") are present, satisfying the score-4 anchor; the 'when' clause does not enumerate as many concrete trigger phrases as the score-5 example, so 5 does not fit.

4 / 5

Trigger Term Quality

Natural phrases a user would say are present ("历史名人访谈", "短视频", "网络热梗", "爆款"), giving good keyword coverage; a few natural synonyms are missing (e.g., 搞笑历史、趣味历史内容、穿越), so it falls just short of the comprehensive-synonym anchor at 5.

4 / 5

Distinctiveness Conflict Risk

The niche — comedic fictional interviews of historical figures for short-video platforms, fusing memes with history — is clearly distinct with its own trigger vocabulary, making accidental triggering of other skills unlikely; this matches the clear-niche anchor, and the score-4 anchor's 'minor overlap risk with closely related skills' fits less well.

5 / 5

Total

17

/

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
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.