CtrlK
BlogDocsLog inGet started
Tessl Logo

posthumous-title-abolition

Use when abolishing the posthumous title system (谥法) to prevent subjects from judging rulers. Establishes sequential numbering from 始皇帝 onward as an alternative naming convention. Abolished by Qin Shi Huang in 221 BCE.

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

Posthumous Title Abolition Procedure

A governance reform procedure for eliminating the practice of assigning posthumous titles to deceased rulers.

Overview

Abolish the tradition where successors and ministers assign titles to deceased rulers based on their conduct, as this allows subordinates to judge superiors.

Steps

  1. Identify the problem: The posthumous title system (谥法) allows:

    • Sons to judge fathers
    • Subjects to judge rulers
    • Undermines hierarchical authority
  2. Issue imperial decree: Formally abolish the posthumous title system

  3. Establish alternative naming:

    • First ruler: 始皇帝 (First Emperor)
    • Successors: numbered sequentially (Second Emperor, Third Emperor, etc.)
  4. Prohibit future modifications: Ensure no later ruler can reinstate the system

Expected Outcomes

  • Rulers cannot be judged by successors or subjects
  • Dynastic continuity emphasized over individual evaluation
  • Simplified succession naming system

Historical Context

Qin Shi Huang abolished this system in 221 BCE, though it was later restored under the Han Dynasty.

Validation

  • Verify that the imperial decree formally abolishes the posthumous title system (谥法)
  • Confirm that the sequential numbering system (始皇帝, Second Emperor, Third Emperor) is established as the official naming convention
  • Check that no mechanism exists for successors or subjects to assign conduct-based titles to deceased rulers
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.