CtrlK
BlogDocsLog inGet started
Tessl Logo

testing-enemy-arrogance

Use when probing enemy leadership's judgment quality and decision-making state. Based on Zhong's grain-request test against Wu: make a resource request, observe whether wise counsel is heeded or ignored, and interpret the response to assess arrogance and internal divisions for attack timing.

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

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Testing Enemy Arrogance

Overview

A reconnaissance procedure to assess whether enemy leadership has become overconfident, demonstrated by Zhong's grain request test.

Steps

  1. Observe enemy behavior - Note signs of pride, dismissiveness, or poor judgment
  2. Make a request that tests generosity - Request grain or resources
  3. Monitor decision process - See if they ignore wise counsel
  4. Interpret results:
    • If they grant request despite advisor warnings = arrogance confirmed
    • If they listen to cautious advisors = still dangerous

Example Application

Zhong observed: "The King of Wu has become arrogant in his governance. Let me test by requesting grain."

  • Wu King granted request against Zixu's advice
  • This confirmed Wu's leadership was compromised

Expected Outcomes

  • Intelligence on enemy decision-making quality
  • Evidence of internal divisions
  • Timing information for attack planning

Verification

  1. Confirm that the test request was designed to reveal whether enemy leadership heeds or ignores wise counsel.
  2. Validate the interpretation: granting the request against advisor warnings confirms arrogance; cautious refusal suggests the enemy remains dangerous.
  3. Check whether evidence of internal divisions (e.g., advisor being overruled) provides actionable timing intelligence for offensive planning.
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.