debt-forgiveness-goodwill-strategy

Use when managing uncollectible debts or converting financial obligations into political capital. Categorizes debtors by ability to pay, publicly burns uncollectible debt documents at a community gathering, and frames forgiveness as investment in loyalty and reputation rather than loss.

Quality

75%

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

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.

This instruction-only skill is concise, concrete, and well-organized, with a clear multi-step workflow and a dedicated validation section that the rubric specifically rewards. The only gap is the absence of explicit error-recovery/feedback loops in the validation steps.

Suggestions

Convert the Validation bullets into a feedback loop: after each verification fails, state the corrective action and that you should re-check before proceeding.

Tighten the ceremonial quotes or mark them clearly as illustrative reframes so they read as actionable framing rather than narrative filler.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes competence — it does not explain what debts or forgiveness are — though the illustrative quoted reframes ("With a lord like this...") add a touch of flavor that could be trimmed.	4 / 5
Actionability	Steps are concrete and specific (gather debtors, provide food, review ability to pay, negotiate schedules, burn documents, make declarations), giving actionable guidance with only minor gaps in execution detail.	4 / 5
Workflow Clarity	A clear four-phase sequence (Assessment → Categorize → Ceremony → Communication) is paired with an explicit Validation section of checkpoints; it lacks formal fix-and-retry feedback loops, capping it just below 5.	4 / 5
Progressive Disclosure	Under 50 lines with no need for external references, the content is cleanly split into well-labeled sections (Overview, Steps, Decision Points, Expected Outcomes, Validation), matching the simple-skill exception.	5 / 5
	Total	17 / 20 Passed

Description

71%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 third-person, opens with an explicit "Use when" trigger, and enumerates concrete actions, giving it strong specificity and distinctiveness. Its main weakness is trigger-term breadth: the phrasing is somewhat specialized and lacks natural synonyms users would spontaneously say.

Suggestions

Broaden trigger terms with more natural phrasings a user might say (e.g. "forgiving debts", "writing off bad debts", "building goodwill with debtors") in addition to the specialized wording.

Add a short clause naming the domain context (e.g. "community or patronage settings") to make the 'when' even more concrete and self-selecting.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — "Categorizes debtors by ability to pay", "publicly burns uncollectible debt documents at a community gathering", "frames forgiveness as investment" — with only minor coverage gaps.	4 / 5
Completeness	Clearly states what the skill does (categorize, burn documents, frame forgiveness) and when to use it ("Use when managing uncollectible debts..."), with the 'when' specific but slightly narrow.	4 / 5
Trigger Term Quality	"Use when managing uncollectible debts or converting financial obligations into political capital" gives relevant triggers, but terms are specialized and lack common synonyms or variations a user might naturally say.	3 / 5
Distinctiveness Conflict Risk	Occupies a very specific niche — debt forgiveness converted to political/reputation capital — with distinct triggers and minimal risk of overlapping unrelated skills.	5 / 5
	Total	16 / 20 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_152/SKILL.md
Commit: 6b836e3

Reviewed: 8 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.