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.

67

Quality

80%

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_146/SKILL.md
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.

The body is concise, well-organized, and pairs a clear 5-step workflow with an explicit validation checklist, scoring well across the board. The only soft spot is actionability, where a few steps remain abstract with an unfilled placeholder.

Suggestions

Replace the '[place]' placeholder in step 5 with concrete guidance on how to choose and record a memorable pledge context (e.g., name a specific location, date, or shared artifact to invoke later).

Tighten the abstract steps (1 and 2) into concrete directives, e.g. 'List the specific colleagues or rivals who could speak against you' and 'Pick a well-known story where repetition of a false claim overturned prior trust' rather than open-ended prompts.

DimensionReasoningScore

Conciseness

The body is lean and well-sectioned (Overview, Steps, Expected Outcomes, Validation) and does not explain concepts Claude already knows; nearly every token earns its place, matching the score-3 anchor.

3 / 3

Actionability

Some steps give concrete, usable guidance (quoted lines in step 3, the 'Remember [place]!' cue in step 5), but several steps stay abstract ('Choose a story about false accusations', 'Identify who might speak against you') with an unfilled placeholder, fitting the score-2 anchor rather than fully copy-paste-ready instruction.

2 / 3

Workflow Clarity

A clearly sequenced 5-step process is paired with an explicit Validation checklist (specific memorable context, analogy resonance, durability under first slander), matching the score-3 anchor's clear sequence plus validation checkpoints.

3 / 3

Progressive Disclosure

The skill is under 50 lines, single-purpose, has no bundle files, and is organized into clean sections; per the simple-skills note this warrants a 3 without external file references.

3 / 3

Total

11

/

12

Passed

Description

75%

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 cleanly covers both what the skill does and when to use it with an explicit trigger, and occupies a distinctive niche. It is held back from the top tier by abstract action phrasing and trigger terms a user would not naturally utter.

Suggestions

Add concrete, plain-language capability verbs (e.g., 'drafts a pledge request', 'selects a trust-erosion analogy', 'scripts a reminder invocation') so specificity reads as actionable rather than narrative.

Broaden trigger terms with phrasings a user would actually say (e.g., 'before a long project', 'when others might undermine you', 'securing buy-in') alongside the current niche wording.

DimensionReasoningScore

Specificity

Names the domain and several actions ("securing a binding commitment", "citing the tale", "extracting a formal pledge"), but the actions are rhetorical/abstract rather than a comprehensive set of concrete capabilities, matching the score-2 anchor.

2 / 3

Completeness

Explicitly answers both what ("securing a binding commitment... extracting a formal pledge" via historical analogy) and when ("Use when securing a binding commitment before a long campaign where rivals may slander you in your absence"), matching the score-3 anchor with an explicit trigger.

3 / 3

Trigger Term Quality

Has an explicit "Use when" trigger with relevant phrases ("long campaign", "rivals may slander you", "formal pledge"), but these are niche phrasings a user would rarely say verbatim, missing common natural variations, so it fits the score-2 anchor rather than 3.

2 / 3

Distinctiveness Conflict Risk

Highly niche framing tied to Gan Mao's method and the Zeng Shen mother tale gives it a clear, distinct trigger unlikely to collide with other skills, matching the score-3 anchor.

3 / 3

Total

10

/

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.