CtrlK
BlogDocsLog inGet started
Tessl Logo

diplomatic-favor-request

Use when requesting assistance from a powerful party at negligible cost to them. Based on Su Dai's (苏代) candlelight metaphor — framing the request as sharing excess that costs nothing ('your candlelight has surplus; share it and lose nothing') to maximize willingness to help.

60

Quality

76%

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

The body is a tight, well-structured instruction skill with concrete phrasing, clear sequencing, and a validation section. Main improvement is reducing minor restatement across Overview/Key Principle/Expected Outcomes.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence, with the metaphor quote and steps carrying the load; minor redundancy between Overview, Key Principle, and Expected Outcomes could be tightened, keeping it just below a 5.

4 / 5

Actionability

For an instruction-only soft skill it gives concrete, usable guidance: numbered steps, the exact metaphor quote to adapt, and the specific emphasis line "No loss to you, great gain for me"; it stops short of fully copy-paste-ready templates.

4 / 5

Workflow Clarity

Five sequenced steps with sub-bullets plus an explicit Validation section provide clear checkpoints; it lacks a true validate→fix→retry feedback loop, but the operation is non-destructive so that is not required.

4 / 5

Progressive Disclosure

Under 50 lines, single-purpose, no bundle files, and well-organized into Overview, Steps, Key Principle, Expected Outcomes, and Validation sections — meeting the simple-skill exception for a top score without external references.

5 / 5

Total

17

/

20

Passed

Description

62%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.

The description has a clear explicit trigger and a distinct, memorable framing, but it leans on the metaphor at the expense of crisp concrete actions and natural trigger synonyms. Tightening the action list and adding common phrasings like "ask a favor" would raise it.

Suggestions

Lead with concrete actions (e.g., "Request a favor by framing it as zero-cost to the giver") before introducing the metaphor.

Add natural trigger synonyms users would say, such as "ask a favor", "request a favor", or "ask for help from someone more powerful".

Trim the embedded metaphor quote in the description; keep a brief reference and let the body carry the full quote.

DimensionReasoningScore

Specificity

It names the domain ("requesting assistance from a powerful party at negligible cost") and a concrete framing action ("framing the request as sharing excess that costs nothing"), but the candlelight metaphor occupies most of the description rather than a comprehensive list of concrete actions.

3 / 5

Completeness

Both the "what" (framing the request as zero-cost sharing) and an explicit "Use when…" trigger are present; the when is reasonably clear but the what is wrapped in metaphor rather than crisp concrete actions, so it is not a 5.

4 / 5

Trigger Term Quality

It includes some relevant natural terms ("requesting assistance", "negligible cost", "willingness to help") but misses common variations a user would actually say such as "ask a favor", "request a favor", or "ask for help from someone powerful".

3 / 5

Distinctiveness Conflict Risk

The niche (requesting a favor from a powerful party by emphasizing negligible cost, anchored by the candlelight metaphor) is fairly distinct and unlikely to trigger the wrong skill, though "requesting assistance" broadly overlaps general help-request skills.

4 / 5

Total

14

/

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.