CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

70

Quality

85%

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

Overview

A methodology for extracting lessons from historical patterns of dynastic rise and fall (兴坏之端) to guide present governance.

Steps

  1. Observe the beginning - How did a dynasty or state originate?

    • 积善累功
    • 天命
    • Military conquest
  2. Track the development - What sustained the state?

    • 德治
    • 制度
    • 形势
  3. Identify the turning points - What caused decline?

    • 骄奢
    • 失德
    • 形势变化
  4. Analyze the end - How did it fall?

    • Internal rebellion
    • External conquest
    • Gradual decline
  5. Extract principles - What general lessons emerge?

    • 仁义为本
    • 形势虽强
    • 德泽后世
  6. Apply as mirror - Use 居今之世,志古之道,所以自镜也

Decision Points

  • When patterns repeat across multiple cases: establish as general principle
  • When cases contradict: investigate specific circumstances
  • When outcome seems inexplicable: consider 天命

Expected Outcomes

  • Understanding of why states succeed or fail
  • Guidance for current governance decisions
  • Framework for evaluating political situations

Validation

  1. Confirm each case has been analyzed through all four phases: origin, development, turning points, and conclusion
  2. Verify that extracted principles are tested against multiple historical cases — repeated patterns are established as general principles, contradictions are investigated
  3. Check that the analysis functions as a mirror for present governance (居今之世,志古之道,所以自镜也) with actionable insights
Repository
baojie/shiji-kb
Last updated
First committed

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.