CtrlK
BlogDocsLog inGet started
Tessl Logo

chronological-table-construction

Use when building chronological tables (世表, 年表, 月表) to organize historical events across dynasties. Synchronizes multiple polities, marks gaps, and adds commentary on patterns of rise and fall (兴坏之端).

65

Quality

78%

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 ./kg/ontology/ontology-v1/skus/procedural/skill_049/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 a compact, well-structured method skill with concrete examples, clear sequencing, and an explicit validation checklist. The only modest gap is the lack of a feedback/retry loop and slight Overview redundancy.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence with no concept over-explanation, though the Overview line lightly restates the frontmatter description and could be trimmed.

4 / 5

Actionability

Steps are concrete and grounded with named examples ('共和 era for reliable dating', '春秋, 历谱谍'), giving actionable method guidance; as an instruction-only skill the absence of code is appropriate.

4 / 5

Workflow Clarity

Eight steps are clearly sequenced and backed by a dedicated Validation section with three checkpoints, but there is no explicit validate→fix→retry feedback loop (acceptable here since the task is intellectual rather than destructive/batch).

4 / 5

Progressive Disclosure

Under 50 lines with no bundle files and no need for external references, yet organized into clear sections (Overview, Steps, Decision Points, Expected Outcomes, Validation) — meeting the simple-skill exception for a top score.

5 / 5

Total

17

/

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.

The description is specific, trigger-explicit, and highly distinct within a narrow niche, cleanly answering both what the skill does and when to invoke it. Its main limitation is that the 'when' clause reuses the same 'building chronological tables' phrasing as the 'what', offering few additional situational cues.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'building chronological tables', 'Synchronizes multiple polities', 'marks gaps', 'adds commentary on patterns of rise and fall' — giving good coverage with only minor abstraction in the commentary action.

4 / 5

Completeness

Explicitly answers both 'what' (build/synchronize/mark/comment on chronological tables) and 'when' ('Use when building chronological tables...'), with the 'when' tied directly to the same trigger phrase rather than distinct scenario cues.

4 / 5

Trigger Term Quality

Natural trigger phrasing ('Use when building chronological tables', 'historical events across dynasties') plus domain terms (世表, 年表, 月表) gives good coverage, though synonyms and explicit file/output extensions are absent.

4 / 5

Distinctiveness Conflict Risk

A clearly bounded niche — dynasty-spanning chronological table construction with specialized terminology (兴坏之端) — that is unlikely to collide with other skills.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.