CtrlK
BlogDocsLog inGet started
Tessl Logo

price-stabilization-method

Use when stabilizing commodity prices, preventing merchant manipulation, or implementing the 平准 system. Covers government buy-low/sell-high intervention, 均输 distribution, and salt-iron monopoly policies.

70

Quality

86%

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

72%

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

A concise, well-organized self-contained skill body with a clear step sequence and a validation checklist. Its weakness is actionability and workflow integration: guidance is abstract and validation is appended rather than woven in as feedback loops.

Suggestions

Add concrete trigger criteria for intervention — e.g., a price band or relative threshold defining 'too high (贵)' and 'too low (贱)' — so the buy-low/sell-high steps are actionable rather than abstract directives.

Integrate validation as inline feedback checkpoints (e.g., 'after releasing goods, confirm prices stabilized; if not, adjust release volume') instead of only a final appendix section.

Attach quantifiable success metrics to the Expected Outcomes (富商大贾无所牟大利, 万物不得腾踊) so the verification steps can be checked concretely rather than by assertion.

DimensionReasoningScore

Conciseness

Lean bullet-driven sections with no padding of concepts Claude already knows; the only minor redundancy is the intro restating the description, but every section earns its place.

3 / 3

Actionability

Steps name policy actions ('Release goods from government stores', 'Sell at reasonable prices') but stay abstract — no price thresholds, trigger criteria, or metrics for 'too high (贵)'/'too low (贱)', leaving key details missing.

2 / 3

Workflow Clarity

Step 1–4 are clearly sequenced and a Validation section exists, but checkpoints are appended rather than integrated and there is no validate→fix→retry feedback loop.

2 / 3

Progressive Disclosure

No bundle files exist and none are needed; the single-purpose, self-contained body uses well-organized sections (Core Principle, Implementation Steps, Supporting Policies, Outcomes, Warning, Validation), qualifying for 3 under the simple-skill note.

3 / 3

Total

10

/

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, third-person description with an explicit 'Use when' trigger and a clear 'what' clause covering concrete policies. It is specific, distinctive, and free of vague fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and policies — 'stabilizing commodity prices, preventing merchant manipulation', 'government buy-low/sell-high intervention, 均输 distribution, and salt-iron monopoly policies' — matching the 'multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicit 'Use when stabilizing commodity prices, preventing merchant manipulation, or implementing the 平准 system' trigger plus a 'Covers government buy-low/sell-high intervention...' clause answers both when and what.

3 / 3

Trigger Term Quality

Natural domain terms a user would actually say ('stabilizing commodity prices', 'preventing merchant manipulation', '平准 system', 'salt-iron monopoly') give good coverage rather than jargon.

3 / 3

Distinctiveness Conflict Risk

The narrow Han-dynasty economic-policy niche (平准/均输/盐铁) has distinct triggers and is unlikely to fire for unrelated skills.

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.