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

77%

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

70%

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

A short, well-organized procedural skill with a clear step sequence and explicit verification checkpoints — its strongest qualities. It loses points on motivational padding in Expected Outcomes and soft decision-point guidance that could be more concrete.

Suggestions

Trim or remove the "Expected Outcomes" rationale lines (e.g., "Demonstrates lack of personal greed") so every line is instructional.

Make decision points more concrete — specify how to handle scarcity, hesitation, or disputes instead of only "encourage them to take what they need".

Tighten the Overview so it does not restate the frontmatter description verbatim.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with clear short sections, but the "Expected Outcomes" block ("Demonstrates lack of personal greed", "Creates reputation for fairness and generosity") is motivational rationale Claude does not need to execute, fitting the mostly-efficient-but-could-be-tightened anchor.	2 / 3
Actionability	Steps include concrete specifics ("corridor or walkway", "personal residence") but decision points stay soft ("encourage them to take what they need") and nothing is copy-paste executable, matching the some-concrete-guidance-but-incomplete anchor rather than a fully executable score 3.	2 / 3
Workflow Clarity	A clear numbered 5-step sequence is paired with a dedicated Verification section of three explicit validation checkpoints, satisfying the clear-sequence-with-explicit-validation anchor; verification is present so the destructive/batch cap at 2 does not apply.	3 / 3
Progressive Disclosure	The skill is under 50 lines, single-purpose, and needs no external references; its well-organized sections (Overview, Steps, Decision Points, Expected Outcomes, Verification) meet the guideline that such simple skills can score 3 on structure alone.	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 well-constructed description that explicitly pairs a "Use when" trigger with concrete capabilities and occupies a distinct niche. Its only weakness is trigger-term breadth: it uses one phrasing rather than covering common synonyms a user might say.

Suggestions

Broaden trigger terms to include common synonyms users might say, e.g. "distributing bonuses, allocating funds, or sharing out rewards received in an official capacity".

Optionally name the audience more directly ("to subordinates or team members") to sharpen the when-trigger.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — "publicly displaying resources, allowing self-selection by subordinates, and keeping nothing for personal use" — matching the anchor for listing several specific concrete actions, rather than the score-2 single-domain example.	3 / 3
Completeness	It opens with an explicit "Use when distributing monetary rewards or resources..." trigger (the when) and follows with what it does ("Ensures fairness and loyalty by publicly displaying resources..."), satisfying the both-what-and-when-with-explicit-triggers anchor.	3 / 3
Trigger Term Quality	"distributing monetary rewards or resources received in an official capacity" supplies relevant natural keywords but offers no common variations (e.g., bonuses, allocating, sharing out, prize money), so it is not the broad coverage of a score 3.	2 / 3
Distinctiveness Conflict Risk	The niche — distributing rewards/resources received in an official capacity to subordinates via public self-selection — is distinct and unlikely to trigger for unrelated skills, fitting the clear-niche-with-distinct-triggers anchor.	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_198/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.