CtrlK
BlogDocsLog inGet started
Tessl Logo

counter-intelligence-removal-tactic

Use when an effective enemy commander has political vulnerabilities exploitable through disinformation. Plants rumors of rebellion or disloyalty to trigger the commander's replacement by a less competent successor.

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

Quality

Content

85%

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

A lean, well-structured instruction skill with concrete rumor templates and an explicit verification checklist. The only slack is mild redundancy between the intro, steps, and expected outcomes.

Suggestions

Drop the restating intro line or fold it into Prerequisites to remove redundancy with the description.

Merge 'Expected Outcomes' into the relevant steps or trim it, since it largely restates steps 4-5.

Tighten the Verification section into a compact checklist to improve token efficiency.

DimensionReasoningScore

Conciseness

Mostly efficient, but the opening sentence restates the description and 'Expected Outcomes' overlaps the steps; the Verification section is slightly verbose and could be tightened.

2 / 3

Actionability

Provides concrete rumor templates ('Planning to rebel', 'deliberately prolonging the campaign', 'secretly negotiating') and a real example quote ('only two cities remain unconquered, why the delay?'); absence of code is appropriate for an instruction-only skill.

3 / 3

Workflow Clarity

Five steps are clearly sequenced and an explicit Verification checklist supplies validation checkpoints (confirm strained relationship, validate plausible references, ensure a plan to capitalize).

3 / 3

Progressive Disclosure

Under 50 lines with no need for external references, yet organized into clearly labeled sections (Prerequisites, Steps, Historical Example, Expected Outcomes, Verification) — satisfying the rubric's short-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 specific, complete, and distinct, cleanly pairing an explicit 'Use when' trigger with concrete actions. Trigger-term quality is slightly niche rather than covering natural user phrasings broadly.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Plants rumors of rebellion or disloyalty to trigger the commander's replacement by a less competent successor' — naming the mechanism (disinformation) and the desired outcome (replacement).

3 / 3

Completeness

Explicitly answers both — 'Use when an effective enemy commander has political vulnerabilities...' (when) and 'Plants rumors... to trigger the commander's replacement' (what).

3 / 3

Trigger Term Quality

Domain keywords like 'enemy commander', 'political vulnerabilities', and 'disinformation' are relevant but niche, and common phrasings a user might actually say are under-covered compared to the breadth expected at level 3.

2 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (commander removal via political disinformation) with distinct triggers unlikely to collide with other skills.

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.