CtrlK
BlogDocsLog inGet started
Tessl Logo

sima-qian-style

将现代文本改写为司马迁《史记》文笔风格。 **触发场景**(主动使用): - 用户明确要求"用太史公文笔改写"、"以史记风格写..."、"太史公曰"、"列传体" - 用户要求将现代文本转为文言文,且强调古雅、简洁、有文史韵味 - 用户提供人物传记、历史事件、技术概念等素材,要求古风改写 - 用户询问"司马迁会怎么写这件事" **功能**: - 三层转换:现代名词古化 → 白话转文言 → 太史公风格 - 应用《史记》特有句式(开篇定式、层递并列、简短断言、对话穿插动作等) - 应用《史记》修辞(白描、先抑后扬、排比对仗、跳跃式剪辑等) - 可选输出"太史公曰"评论段(50-80字精简版) **不做什么**: - 不复述《史记》原文内容 - 不模拟司马迁的历史观点 - 不套用《史记》名句 - 只学习语言形式、句法结构、修辞节奏 本技能基于《史记》130篇语料分析,适用于人物传记、历史事件、技术概念等现代素材的古风改写。

71

Quality

89%

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

83%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 content is highly actionable and well-sequenced with concrete templates, examples, and a verification checklist. Its main weakness is conciseness due to repeated self-check and example blocks. Progressive disclosure is strong but references a non-existent evals/ directory.

Suggestions

De-duplicate the 自检功能 section against the inline 第6步 自检与润色 checklist — they repeat nearly identical items, costing ~30 lines of context.

Trim the repeated 太史公曰 examples (the 106-vs-52字删减示例 is shown in full twice); keep one concise instance and reference the rest.

Remove or create the referenced evals/ directory (cited in 参考文档 as '乔布斯列传、葛底斯堡演说等4个完整示例') to keep navigation promises intact.

DimensionReasoningScore

Conciseness

The body is large (~530 lines) with considerable repetition: workflow steps are restated in the 自检功能 section, the 太史公曰 example appears multiple times, and some explanatory asides restate concepts. It is mostly efficient but could be tightened by de-duplicating the self-check and example blocks.

3 / 5

Actionability

It provides concrete, copy-paste-ready patterns with explicit templates (X者,Y也), worked examples, replacement tables (是→为, 有→具), and a checklist of specific operations like deleting 的/地/得/了 — fully actionable guidance.

5 / 5

Workflow Clarity

The three-step conversion method (现代名词→文言→太史公) is clearly sequenced with explicit checkpoints, a numbered 解析/句式/修辞/自检 process, and a feedback-loop self-check checklist (自检与润色) for verification before output.

5 / 5

Progressive Disclosure

Structure is good with three real one-level-deep references (modern-terms.md, classical-chinese.md, style-features.md) clearly signaled in the body and listed in 参考文档; however the referenced evals/ directory does not exist, a minor navigation gap.

4 / 5

Total

17

/

20

Passed

Description

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

The description is highly specific and complete, clearly stating both what the skill does and when to use it with concrete trigger phrases. It carves a distinct niche with minimal conflict risk. Minor room for more explicit synonym enumeration in trigger terms.

Suggestions

Consolidate trigger phrases into a single inline 'Use when...' clause at the top of the description rather than spreading them across a bullet list, which is the anchor format for a score-5 description.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions: 三层转换, applying 《史记》句式 (开篇定式、层递并列、简短断言), applying 修辞 (白描、先抑后扬), and optional 太史公曰 output, giving comprehensive coverage of capabilities.

5 / 5

Completeness

It explicitly answers 'what' (三层转换, 句式, 修辞, optional 太史公曰) under 功能, and 'when' under 触发场景 with concrete trigger phrases like '用户明确要求用太史公文笔改写' and '司马迁会怎么写这件事'.

5 / 5

Trigger Term Quality

It includes natural phrases users would say like '用太史公文笔改写', '以史记风格写', '太史公曰', '列传体', and '司马迁会怎么写这件事'; coverage is strong but a few common synonyms (e.g. '司马迁', '史记') are not all enumerated as explicit triggers.

4 / 5

Distinctiveness Conflict Risk

The niche is highly specific (司马迁《史记》文笔改写) with distinct triggers like 太史公曰 and 列传体, making conflict with other skills minimal.

5 / 5

Total

19

/

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

skill_md_line_count

SKILL.md is long (529 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository
baojie/shiji-kb
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.