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

78%

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

72%

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

A concise, well-organized strategy skill with clear sequencing and a validation section. Actionability and workflow clarity trail slightly because some steps are abstract framing and the validation for the destructive document-burning step is not a true pre-action checkpoint.

Suggestions

Add concrete criteria or a short procedure for distinguishing 'unable to pay' from 'unwilling to pay' so the categorization step is fully actionable.

Reframe the Validation section as a pre-destruction gate: confirm categorization and community reach BEFORE burning documents, with an explicit 'if check fails, do not proceed' loop.

Tighten abstract framing steps ('Frame it as', 'Let the community spread the story') into concrete actions the operator performs.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes competence — it never explains concepts Claude already knows and each section earns its tokens, including the quoted rhetorical scripts which serve as concrete copy rather than filler.	3 / 3
Actionability	Concrete steps and copy-paste scripts ('With a lord like this, how could we betray him?') are present, but several steps are abstract framing ('Frame it as', 'Let the community spread the story') and key implementation details like how to assess ability to pay are missing.	2 / 3
Workflow Clarity	The four-phase sequence is clear and a Validation section exists, but for a destructive batch operation (burning debt documents) the validation is post-hoc rather than an integrated pre-destruction gate with an explicit validate-fix-retry feedback loop.	2 / 3
Progressive Disclosure	Under 50 lines with no need for external references, and well-organized into Overview, Steps, Decision Points, Expected Outcomes, and Validation sections — matching the simple-skill allowance for a top score.	3 / 3
	Total	10 / 12 Passed

Description

85%

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 strong, specific description with an explicit trigger clause and clear, concrete actions. Trigger-term coverage is the only weak spot, lacking common synonyms a user might naturally say.

Suggestions

Add common trigger synonyms such as 'debt relief', 'debt cancellation', or 'loan write-off' so the description matches more natural user phrasings.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Categorizes debtors by ability to pay, publicly burns uncollectible debt documents at a community gathering, and frames forgiveness as investment in loyalty and reputation' — matching the multiple-specific-actions anchor.	3 / 3
Completeness	Explicitly answers both 'what' (categorize, burn documents, frame forgiveness) and 'when' via a 'Use when...' trigger clause, matching the top anchor.	3 / 3
Trigger Term Quality	'Use when managing uncollectible debts or converting financial obligations into political capital' uses natural terms, but misses common variations a user might say such as 'debt relief', 'debt cancellation', or 'loan write-off'.	2 / 3
Distinctiveness Conflict Risk	The debt-forgiveness-as-political-capital niche is highly specific with distinct triggers unlikely to collide with other skills.	3 / 3
	Total	11 / 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_152/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.