historical-pattern-analysis

Use when analyzing dynastic cycles, predicting political decline, or extracting governance lessons from history. Traces patterns of rise and fall (兴坏之端) across origins, development, turning points, and collapse.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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, concise analytical methodology with a clear sequenced workflow and explicit validation checkpoints. The main gap is actionability: the per-step sub-points read as thematic categories rather than concrete, directive guidance.

Suggestions

Convert each step's sub-bullets from loose categories into directive guidance (e.g., "List the founding virtue (积善累功) and cite the specific founding event") so each step has a concrete action.

Add a short worked mini-example applying the four phases to one dynasty to ground the abstract framework.

Specify the expected output format for the final 'apply as mirror' step so the analysis yields a usable artifact.

Dimension	Reasoning	Score
Conciseness	The body is lean and bullet-driven with no padding or re-explanation of concepts Claude already knows; every section earns its place, matching the lean-and-efficient anchor.	3 / 3
Actionability	The six steps give a clear analytical framework but the sub-points are loose categories ("积善累功", "德治", "骄奢") rather than specific, executable actions; guidance is concrete in structure but somewhat abstract per step, sitting between the abstract and copy-paste-ready anchors.	2 / 3
Workflow Clarity	A clear six-step numbered sequence is paired with an explicit Validation section containing checkpoints (confirm all four phases, verify principles tested against multiple cases, check the mirror function), matching the clear-sequence-with-explicit-validation anchor.	3 / 3
Progressive Disclosure	The skill is under 50 lines with well-organized sections (Overview, Steps, Decision Points, Expected Outcomes, Validation) and no external references needed, so per the simple-skills note it qualifies for the top anchor.	3 / 3
	Total	11 / 12 Passed

Description

85%

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 with explicit trigger guidance, concrete actions, and a clear distinct niche. Its only weakness is trigger-term breadth, where a few more natural phrasings users might say would improve coverage.

Suggestions

Add a few more natural trigger phrasings users might actually say (e.g., "comparing historical empires", "why did this empire fall", "lessons from past dynasties") to broaden trigger-term coverage.

Consider mentioning concrete deliverables (e.g., "produce a structured rise-and-fall analysis") to make the output even more specific.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "analyzing dynastic cycles, predicting political decline, or extracting governance lessons" — and enumerates the phases (origins, development, turning points, collapse), matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	Explicitly answers both what ("Traces patterns of rise and fall…across origins, development, turning points, and collapse") and when ("Use when analyzing dynastic cycles, predicting political decline, or extracting governance lessons from history") with an explicit trigger clause.	3 / 3
Trigger Term Quality	Relevant natural terms ("dynastic cycles", "political decline", "governance lessons") are present but coverage of common user phrasings is incomplete; this sits at the 'some relevant keywords but missing common variations' anchor rather than broad coverage.	2 / 3
Distinctiveness Conflict Risk	The dynastic-cycle / governance-lesson niche with its specialized triggers is clearly distinguishable and unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

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: baojie/shiji-kb
Path: kg/ontology/ontology-v1/skus/procedural/skill_052/SKILL.md
Commit: 79c272f

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.