CtrlK
BlogDocsLog inGet started
Tessl Logo

strategic-decision-framework

Use when prioritizing between competing strategic targets or evaluating conquest options. Weighs prestigious targets (symbolic resources like the nine tripods) against practical targets (territorial expansion) using feasibility, consequence, net benefit, and reputation criteria.

61

Quality

71%

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_139/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

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

A compact, well-organized conceptual framework that avoids over-explaining basics and structures content cleanly. It is held back by abstract, non-executable guidance and topical rather than crisply sequenced workflow steps.

Suggestions

Remove the ceremonial "Overview", "Core Question", and "Expected Outcome" sections whose content restates the description or adds no operational value.

Add a concrete worked example or a reusable decision-matrix template (options as rows, the four criteria as columns) so the guidance is directly actionable rather than abstract.

Reframe the decision flow as a numbered procedure with explicit pass/fail validation gates between steps, replacing the abstract validation questions.

DimensionReasoningScore

Conciseness

The body is mostly efficient with bullets and short sections, but "Overview", "Core Question", and "Expected Outcome" restate what is already clear or add ceremonial framing ("A strategic choice that balances ambition with practicality") that does not earn its place.

2 / 3

Actionability

It gives some concrete guidance — four named criteria with definitions and a three-point validation checklist — but the decision procedure stays abstract with no worked example, decision matrix, or scoring template, leaving key details missing.

2 / 3

Workflow Clarity

A sequence is implied (options -> criteria -> key insight -> validation) and a validation checklist exists, but the main flow is topical rather than a crisp numbered procedure and the checks are abstract ("is that the correct priority for the current situation?") rather than concrete pass/fail gates.

2 / 3

Progressive Disclosure

At under 50 lines with no need for external references and no bundle files, the well-organized section structure (Overview, Options, Decision Criteria, Key Insight, Validation) meets the simple-skill bar for progressive disclosure.

3 / 3

Total

9

/

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.

A well-constructed description that clearly states both its purpose and trigger with concrete, domain-specific elements. Its main weakness is trigger phrasing that is somewhat formal rather than matching how a user would naturally request this skill.

DimensionReasoningScore

Specificity

The description lists multiple concrete elements — the two target types ("prestigious targets", "practical targets") and four named criteria ("feasibility, consequence, net benefit, and reputation") — matching the anchor for listing several specific concrete actions.

3 / 3

Completeness

It explicitly answers both what ("Weighs prestigious targets... against practical targets... using feasibility, consequence, net benefit, and reputation criteria") and when ("Use when prioritizing between competing strategic targets or evaluating conquest options"), with an explicit 'Use when' trigger.

3 / 3

Trigger Term Quality

Trigger phrases like "prioritizing between competing strategic targets" and "evaluating conquest options" are relevant but formal/academic; it misses the casual variations a user would more naturally say (e.g. "which target should I attack first"), so it lands at 'some relevant keywords but missing common variations'.

2 / 3

Distinctiveness Conflict Risk

The highly specific niche — conquest prioritization with symbolic resources like "the nine tripods" and territorial expansion — gives it a clear, distinctive trigger unlikely to fire for unrelated 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.