CtrlK
BlogDocsLog inGet started
Tessl Logo

trust-securing-through-historical-analogy

Use when securing a binding commitment before a long campaign where rivals may slander you in your absence. Based on Gan Mao's (甘茂) method — citing the tale of Zeng Shen's mother (曾参之母) to illustrate how repeated false accusations erode even deep trust, then extracting a formal pledge.

68

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

78%Weight 40%Scale 1-5

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

A tight, well-structured instruction skill with a clear sequenced workflow and an explicit validation section including a feedback loop. The main improvement would be interleaving validation checkpoints directly within the numbered steps.

Suggestions

Interleave validation checkpoints within the numbered steps (e.g., after step 4, 'Confirm the pledge cites a specific place/circumstance before proceeding') rather than isolating them in a trailing section.

Add one or two concrete sample dialogues showing the Present Your Case and Invoke Pledge steps in action to raise actionability from good to fully executable.

Tighten the rhetorical quoted lines in 'Present Your Case' into a reusable template so the phrasing reads as a fill-in pattern rather than three fixed lines.

DimensionReasoningScore

Conciseness

The body is lean with no padding about what trust or analogies are, though the rhetorical quoted lines and the worked example add slightly more than the minimum needed.

4 / 5

Actionability

As an instruction-only skill it provides concrete guidance — specific example phrasings ('My virtue is less than...', 'Remember [place]!') and a worked Zeng Shen example — with only minor gaps in fully specified execution.

4 / 5

Workflow Clarity

Five steps are clearly sequenced and a dedicated Validation section provides explicit checks plus a feedback loop ('if not, the pledge was insufficient'), but the checkpoints live in a trailing section rather than being interleaved within the steps.

4 / 5

Progressive Disclosure

This is a simple under-50-line skill with no bundle files, and the content is cleanly organized into Overview, Steps, Expected Outcomes, and Validation sections — meeting the simple-skill exception for a top score.

5 / 5

Total

17

/

20

Passed

Description

87%Weight 40%Scale 1-5

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-crafted description that clearly states both the trigger conditions and the concrete method, anchored in a specific historical analogy that makes it highly distinct. Minor room for broader synonym coverage in trigger terms.

DimensionReasoningScore

Specificity

The description names several concrete actions — 'securing a binding commitment', 'citing the tale', 'extracting a formal pledge' — giving good coverage, though the actions are framed abstractly within a niche domain.

4 / 5

Completeness

It explicitly answers both what ('securing a binding commitment... extracting a formal pledge' via Gan Mao's method) and when ('Use when securing a binding commitment before a long campaign where rivals may slander you in your absence') with a concrete trigger clause.

5 / 5

Trigger Term Quality

Natural trigger phrases like 'binding commitment', 'long campaign', 'rivals may slander you', and 'trust' cover the main ways a user would request this, with a few synonymous phrasings missing.

4 / 5

Distinctiveness Conflict Risk

The historical-analogy trust-securing niche is highly distinctive with specific triggers ('binding commitment', 'rivals may slander you') unlikely to collide with other skills.

5 / 5

Total

18

/

20

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.

Validation — 16 / 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.