CtrlK
BlogDocsLog inGet started
Tessl Logo

de-escalation-through-symbolic-pardon

Use when a powerful subordinate has shown disloyalty but direct confrontation is too costly. Based on Emperor Wen's handling of Wu Wang, employs symbolic honors, face-saving exits, and indirect acknowledgment of grievances to reduce tensions.

66

Quality

79%

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_195/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 well-structured, concise, and actionable for an instruction-only skill, with clear sequencing and a verification/feedback loop. It is held back only by minor abstraction in a couple of steps and slightly implicit gating between checkpoints.

Suggestions

Make checkpoints explicit gates (e.g., 'Only proceed to symbolic honors once the underlying grievance is identified') rather than implicit sequencing.

Tighten the Overview and Expected Outcomes sections to remove phrases that restate the description.

Add one concrete negative example (what a face-saving exit is NOT) to sharpen the actionability of Step 5.

DimensionReasoningScore

Conciseness

The body is lean and sectioned without padding concepts Claude already knows; a few phrases in the Overview and Expected Outcomes could be trimmed but nothing is wasteful.

4 / 5

Actionability

Concrete directives ('Do not imprison or punish envoys', 'Bestow gifts associated with age and respect (staff, stool)', 'Accept explanations even when known to be false') give mostly executable guidance for an instruction-only skill, with minor abstraction gaps.

4 / 5

Workflow Clarity

A clearly sequenced 6-step process with a dedicated Verification section and feedback loop ('prepare stronger measures if transgressions continue or escalate'); some checkpoints are implicit rather than explicitly gated.

4 / 5

Progressive Disclosure

A compact single-purpose skill (~48 body lines) with well-organized sections and no need for external references, satisfying the simple-skill exception.

5 / 5

Total

17

/

20

Passed

Description

80%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 strong: it states a clear trigger, concrete techniques, and a distinctive niche with low conflict risk. Its only weakness is limited keyword/synonym coverage owing to the specialized domain.

DimensionReasoningScore

Specificity

Names the domain and lists several concrete techniques ('symbolic honors', 'face-saving exits', 'indirect acknowledgment of grievances'), falling just short of comprehensive coverage.

4 / 5

Completeness

Explicitly answers both what ('employs symbolic honors, face-saving exits, and indirect acknowledgment of grievances to reduce tensions') and when ('Use when a powerful subordinate has shown disloyalty...') with a concrete trigger.

5 / 5

Trigger Term Quality

Includes a natural trigger phrase ('a powerful subordinate has shown disloyalty but direct confrontation is too costly') but the niche domain leaves little room for synonyms or common variations.

3 / 5

Distinctiveness Conflict Risk

A very specific niche (symbolic pardon of a disloyal subordinate, anchored to Emperor Wen's case) with distinct triggers and minimal overlap 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.