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.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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

Quality

Content

70%

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

A concise, well-structured reasoning skill with a clear sequenced workflow and validation checkpoints, appropriate for its simple single-purpose scope. The main weaknesses are mild verbosity in the Outcomes section and abstract actionability where the symbolic-fulfillment path lacks concrete guidance.

Suggestions

Trim the 'Expected Outcomes' section or fold its one essential point into the Overview to reduce padding and lift conciseness from 2 to 3.

Make the symbolic-fulfillment branch actionable by giving concrete options (e.g., 'deliver the item to the recipient's heir or grave, publicly declare the promise kept, or perform the act the recipient would have wanted') so actionability reaches 3.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with well-organized sections and no over-explanation of concepts Claude already knows, but the 'Expected Outcomes' section ('Maintenance of personal integrity', 'Reputation for trustworthiness that transcends circumstances') is mild padding that could be trimmed, and the Overview repeats the frontmatter description.	2 / 3
Actionability	Guidance is concrete enough to follow — a four-step procedure plus a worked example — but the steps remain abstract directives ('Complete the promised action regardless', 'perform symbolic fulfillment') without specifying how to choose or execute symbolic fulfillment, leaving the instruction partially incomplete.	2 / 3
Workflow Clarity	As a simple, single-purpose reasoning skill under 50 lines, the four steps are clearly sequenced and the explicit Validation section provides three verification checkpoints; per the simple-skills scoring note this qualifies for a 3.	3 / 3
Progressive Disclosure	The skill is under 50 lines with no need for external references, and content is organized into clearly labeled sections (Overview, Steps, Example, Outcomes, Validation); per the guideline this earns a 3 on well-organized sections alone.	3 / 3
	Total	10 / 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.

A well-structured description with an explicit 'Use when' trigger and a distinctive, conflict-free niche, but it is light on concrete capability breadth and natural trigger-term coverage. Strengthening the action list and adding everyday trigger phrasing would raise specificity and trigger quality.

Suggestions

List the concrete actions the skill performs (e.g., 'Evaluate whether an internal promise still binds you, decide between direct or symbolic fulfillment, and verify integrity was preserved') to lift specificity from 2 to 3.

Broaden trigger terms with everyday phrasings users would actually say, such as 'keeping a promise', 'honoring a pledge', or 'what to do when someone you promised has died', to improve trigger_term_quality.

Dimension	Reasoning	Score
Specificity	The description names the domain ('honor a commitment after circumstances change', 'recipient's death') and the governing principle, but does not list multiple concrete distinct actions — it describes one decision ('deciding whether to honor') rather than a set of capabilities.	2 / 3
Completeness	It explicitly answers both 'what' ('Applies Ji Zha's sword-promise principle: internal assent creates moral obligation') and 'when' ('Use when deciding whether to honor a commitment after circumstances change, especially after the recipient's death') with an explicit trigger clause.	3 / 3
Trigger Term Quality	It includes relevant natural terms ('commitment', 'honor a commitment', 'recipient's death') in an explicit 'Use when' clause, but coverage of common variations is thin and the vocabulary is niche rather than the everyday phrasing a user would naturally say.	2 / 3
Distinctiveness Conflict Risk	The niche is highly specific — Ji Zha's sword-promise principle and death-of-recipient commitments — making it clearly distinguishable and very unlikely to trigger for the wrong skill.	3 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

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
Path: kg/ontology/ontology-v1/skus/procedural/skill_065/SKILL.md
Commit: 79c272f

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.