distributing-rewards-to-subordinates

Use when distributing monetary rewards or resources received in an official capacity. Ensures fairness and loyalty by publicly displaying resources, allowing self-selection by subordinates, and keeping nothing for personal use.

Quality

79%

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_198/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.

A clear, well-structured procedural skill with concrete steps and an explicit verification section. It is appropriately concise for its scope; the only mild gaps are a few abstract action items and the absence of an error-recovery feedback loop.

Suggestions

Tighten the Overview and Expected Outcomes sections to reduce overlap with the description and focus on instruction.

Make abstract steps actionable, e.g. replace 'Maintain transparency' with a concrete act such as announcing the distribution in a shared channel.

Add a brief feedback loop in Verification, e.g. what to do if a resource is found to have been taken privately or hoarded.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-sectioned, but the Overview and Expected Outcomes sections restate the description's rationale (benefits like 'Builds trust', 'Demonstrates lack of personal greed') rather than instructing, which is minor over-explanation that could be trimmed.	4 / 5
Actionability	Most steps give concrete, executable guidance (e.g., 'Place the resources in a visible, accessible location (e.g., corridor or walkway)', 'Let subordinates... take what they need as they pass by'), with only a couple of abstract steps like 'Maintain transparency - The entire process should be visible to all' leaving minor gaps.	4 / 5
Workflow Clarity	A clear five-step numbered sequence is paired with an explicit three-point Verification section as validation checkpoints, but there is no fix-and-retry feedback loop for when verification fails, keeping it just below a 5.	4 / 5
Progressive Disclosure	This is a simple, single-purpose skill under 50 lines with no need for external references; its clear section headers (Overview, Steps, Decision Points, Expected Outcomes, Verification) make it well-organized and easy to navigate, matching the simple-skill allowance for a 5.	5 / 5
	Total	17 / 20 Passed

Description

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

A well-constructed description that clearly states both purpose and an explicit 'Use when' trigger in third-person voice, with concrete actions and a distinct niche. The main weakness is limited keyword/synonym coverage in the trigger terms.

Suggestions

Add common synonyms a user might naturally say, e.g. 'gifts, bonuses, spoils, or payouts', to broaden trigger-term coverage.

Consider listing one more concrete action (e.g., recording or reporting the distribution) to push specificity toward comprehensive.

Dimension	Reasoning	Score
Specificity	Names the domain and lists three concrete actions ('publicly displaying resources, allowing self-selection by subordinates, and keeping nothing for personal use'), which is several specific actions with only minor coverage gaps; not quite the comprehensive multi-action list of a 5.	4 / 5
Completeness	It explicitly answers both what ('Ensures fairness and loyalty by publicly displaying resources, allowing self-selection...') and when with a concrete 'Use when distributing monetary rewards or resources received in an official capacity' trigger phrase, matching the top anchor.	5 / 5
Trigger Term Quality	It includes relevant natural terms ('distributing monetary rewards', 'resources received in an official capacity') but misses common synonyms and variations users might say (e.g., 'gifts', 'bonuses', 'spoils', ' payouts'), so coverage is partial rather than good.	3 / 5
Distinctiveness Conflict Risk	The niche is highly specific — distributing rewards/resources received in an official capacity to subordinates — with distinct triggers and minimal realistic overlap with other skills.	5 / 5
	Total	17 / 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_198/SKILL.md
Commit: 6b836e3

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