CtrlK
BlogDocsLog inGet started
Tessl Logo

deceptive-standoff-tactic

Use when a small force encounters a much larger enemy and retreat means destruction. Employs psychological deception by advancing, dismounting, and displaying calm to convince the enemy of a hidden ambush, forcing withdrawal.

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

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured, actionable, and includes explicit verification checkpoints for a destructive-context workflow. Mild redundancy across Overview, Expected Outcomes, and the description is the only notable inefficiency.

Suggestions

Collapse the Overview and Expected Outcomes into the Steps/Decision Points where the information already lives, removing restated content.

Merge the Decision Points and Verification sections so pre-commit checks and post-action checks read as one continuous checklist.

DimensionReasoningScore

Conciseness

The body is mostly lean, but the Overview and Expected Outcomes sections restate content already conveyed by the description and Steps, leaving room to tighten.

2 / 3

Actionability

Steps give concrete, specific instructions — 'Halt approximately 2 li (about 1 km)', 'dismount and remove saddles', 'lie down and release horses to graze' — directly executable for an instruction-only skill.

3 / 3

Workflow Clarity

A clearly sequenced 7-step process with an explicit Verification section providing validation checkpoints (confirm retreat risk, validate discipline, check enemy withdrawal) in a high-stakes context.

3 / 3

Progressive Disclosure

Under 50 lines with a single purpose and well-organized sections (Overview, Steps, Decision Points, Expected Outcomes, Verification); no external references are needed, satisfying the simple-skill allowance.

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.

The description is concrete, complete, and clearly niche-scoped, with an explicit Use-when trigger and several named actions. The main weakness is that the trigger terms read as a scenario paraphrase rather than natural user vocabulary.

Suggestions

Add natural-language trigger terms a user might actually say (e.g., 'outnumbered', 'outgunned', 'survive a larger force', 'bluff an ambush') alongside the scenario clause.

Consider trimming the secondary clause to keep the description tight while preserving the what+when structure.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'advancing, dismounting, and displaying calm to convince the enemy of a hidden ambush, forcing withdrawal' — matching the multiple-specific-actions anchor.

3 / 3

Completeness

Explicitly answers both what ('Employs psychological deception...') and when ('Use when a small force encounters...'), with a clear 'Use when' clause.

3 / 3

Trigger Term Quality

The trigger 'small force encounters a much larger enemy and retreat means destruction' is a scenario description rather than natural keywords a user would spontaneously say; coverage of likely user phrasing is partial.

2 / 3

Distinctiveness Conflict Risk

The niche is highly specific (cavalry dismount/saddle-removal deception standoff) with distinct situational triggers, making conflict with other skills unlikely.

3 / 3

Total

11

/

12

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.