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 (兴坏之端).

75

Quality

92%

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

85%

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

A well-structured, lean instruction-only skill with clear sequencing and explicit validation checkpoints. Its main weakness is actionability: guidance is conceptual and would benefit from a concrete worked example.

Suggestions

Add a short worked example showing a minimal table layout (e.g., a 2-3 row markdown table synchronizing two polities with a marked gap) to make the guidance copy-paste ready.

Concretize step 6 ('Synchronize multiple polities') by showing the column structure to use for parallel polity alignment.

In the Validation section, add an explicit fix-and-retry loop ('if a check fails, correct the table and re-validate') rather than only listing confirmations.

DimensionReasoningScore

Conciseness

Lean body (~24 lines) with no padding or re-explanation of concepts Claude already knows; every section earns its place.

3 / 3

Actionability

Names concrete domain specifics (sources 春秋/历谱谍, table types 世表/年表/月表, parallel columns) but stays at a conceptual level without a worked example or concrete table layout, leaving key details unspecified.

2 / 3

Workflow Clarity

An 8-step numbered sequence is paired with a dedicated Validation section of explicit checkpoints (confirm table type, verify synchronization, check commentary), matching the clear-sequence-with-validation anchor.

3 / 3

Progressive Disclosure

Under 50 lines, single-purpose, no external references needed; well-organized into Overview, Steps, Decision Points, Expected Outcomes, and Validation sections, qualifying for the simple-skill exception.

3 / 3

Total

11

/

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.

A strong, concise description that names concrete capabilities, supplies explicit 'Use when' triggers with natural domain terms, and carves out a distinct niche. It cleanly satisfies every dimension without padding.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'building chronological tables', 'Synchronizes multiple polities', 'marks gaps', and 'adds commentary on patterns of rise and fall' — matching the multiple-specific-actions anchor.

3 / 3

Completeness

Explicitly answers both what (synchronizes polities, marks gaps, adds commentary) and when via the 'Use when building chronological tables...' trigger clause.

3 / 3

Trigger Term Quality

Covers natural domain terms a user would say ('chronological tables', 'historical events across dynasties') plus the named variants 世表, 年表, 月表, giving good coverage rather than jargon.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (chronological tables for historical events across dynasties) with distinct triggers unlikely to conflict with other skills.

3 / 3

Total

12

/

12

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.