CtrlK
BlogDocsLog inGet started
Tessl Logo

counter-insurgency-reward-system

Use when designing military incentive structures to motivate troops and encourage enemy defections. Establishes tiered rewards by enemy rank (大将 to 千石), defection incentives for surrendering units, and multiplier systems for credible payouts.

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

Quality

Content

85%

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

Well-structured and highly actionable, with concrete numbers and a clear sequenced workflow plus verification. The only weakness is mild padding in the 'Expected Outcomes' and 'Decision Points' sections that restates inferable goals.

Suggestions

Trim or remove the 'Expected Outcomes' section — 'High motivation among troops' and 'Encouraged defections' merely restate the skill's purpose and are inferable from the description.

Fold the 'Decision Points' guidance into the relevant steps (e.g., credibility into step 4) rather than presenting it as a separate generic section, or tighten it to only non-obvious tradeoffs.

Keep the lean Steps and Verification structure as-is; it is the strongest part of the body.

DimensionReasoningScore

Conciseness

The Steps and Verification sections are lean and assume competence, but 'Expected Outcomes' ('High motivation among troops', 'Encouraged defections') restates obvious goals and 'Decision Points' offers generic advice Claude could infer. Not score 3: there is inferable content that could be trimmed; not score 1: it is not verbose and does not explain basic concepts.

2 / 3

Actionability

Concrete, copy-paste-ready guidance: exact reward amounts (5000 jin gold, 10,000 household fief), named ranks (大将 down to 千石), and an explicit multiplier ('Double standard military regulations'). As an instruction-only skill its guidance is fully actionable without code.

3 / 3

Workflow Clarity

Five clearly sequenced steps followed by an explicit Verification checklist ('Confirm reward tiers...', 'Validate funding sources...', 'Ensure defection incentives are scaled...'). This is a non-destructive planning skill, so the missing validate-fix-retry loop does not cap the score.

3 / 3

Progressive Disclosure

A ~42-line single-purpose skill organized into Overview, Steps, Decision Points, Expected Outcomes, and Verification with no bundle files present. Per the simple-skills note, clean self-contained organization earns the top score without external references.

3 / 3

Total

11

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, concise description: third-person voice, explicit 'Use when' trigger, multiple concrete capabilities, and a clearly distinct niche. It satisfies every dimension at the top of the scale.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'tiered rewards by enemy rank', 'defection incentives for surrendering units', and 'multiplier systems' — rather than vague language. It is comprehensive enough to clear the 'names multiple specific concrete actions' anchor, not merely naming a domain.

3 / 3

Completeness

Explicitly answers both 'what' (tiered rewards, defection incentives, multiplier systems) and 'when' via the 'Use when designing...' trigger. Not score 2: the when is explicit, not merely implied.

3 / 3

Trigger Term Quality

The 'Use when designing military incentive structures to motivate troops and encourage enemy defections' clause gives natural phrasings a user would actually say. Not score 2: it covers the common variations (motivate troops, defections, rewards) rather than only a single keyword.

3 / 3

Distinctiveness Conflict Risk

Targets a very specific counter-insurgency reward-design niche with distinct triggers, making overlap with other skills unlikely. Not score 2: it is not a generic 'works with documents'-style description that could collide.

3 / 3

Total

12

/

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.