CtrlK
BlogDocsLog inGet started
Tessl Logo

promise-fulfillment-protocol

Use when deciding whether to honor a commitment after circumstances change, especially after the recipient's death. Applies Ji Zha's sword-promise principle: internal assent creates moral obligation that transcends death.

58

Quality

66%

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

Quality

Content

68%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 well-structured, concise skill with a clear sequenced workflow and validation checklist, but the actionability is constrained by the inherently abstract/ethical nature of the task — it offers principles and a worked example rather than concrete executable steps.

Suggestions

Add concrete decision criteria or a short decision rubric for 'assessing changed circumstances' (e.g., explicit checklist questions) to make the guidance more executable.

Tighten the 'Example Application' into a reusable pattern template rather than a single historical narrative, so the example generalizes to new cases.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's intelligence, with only minor instances of restating the principle; the core quote ('When my heart has already promised...') earns its place rather than padding.

4 / 5

Actionability

Guidance is mostly abstract ('Acknowledge promises made in your heart', 'perform symbolic fulfillment') with no concrete executable procedure or worked decision criteria; it describes the moral stance more than it instructs how to execute it.

3 / 5

Workflow Clarity

The four-step sequence (Recognize -> Assess -> Apply -> Fulfill) is clearly ordered and a Validation section provides checkpoints, though the checkpoints are confirmatory rather than error-recovery feedback loops.

4 / 5

Progressive Disclosure

This is a short, self-contained single-purpose skill (under 50 lines, no external references needed), with clean section headers (Overview, Steps, Example Application, Expected Outcomes, Validation) and no nested references; structure is well-organized per the simple-skill exception.

5 / 5

Total

16

/

20

Passed

Description

65%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 is distinctive with a clear, explicit 'Use when' trigger and a well-defined niche, but it is only moderately specific in enumerating concrete actions and offers limited keyword variation. It reads in third person as required.

Suggestions

Add 1-2 more concrete actions or verbs (e.g., 'evaluate', 'fulfill symbolically', 'decide') to raise specificity beyond the single 'honor a commitment' action.

Include a few more natural trigger phrases or synonyms users might say (e.g., 'broken promise', 'should I keep my word', 'commitment after loss') to broaden keyword coverage.

DimensionReasoningScore

Specificity

Names the domain ('honoring a commitment after circumstances change') and a couple concrete actions ('honor a commitment', 'transcends death') but does not enumerate multiple distinct concrete actions; coverage is adequate but not comprehensive.

3 / 5

Completeness

Provides an explicit 'Use when...' clause ('Use when deciding whether to honor a commitment...') and a clear statement of what the skill applies ('Ji Zha's sword-promise principle'); both what and when are present, though the 'when' is somewhat specialized.

4 / 5

Trigger Term Quality

Includes the natural phrase 'whether to honor a commitment after circumstances change' and 'recipient's death', but relies on one framing rather than covering common variations or synonyms a user would naturally say.

3 / 5

Distinctiveness Conflict Risk

Targets a very specific, unusual niche (post-death commitment honoring via Ji Zha's principle) with triggers unlikely to overlap with other skills, giving minimal conflict risk.

5 / 5

Total

15

/

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.

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.