CtrlK
BlogDocsLog inGet started
Tessl Logo

assessing-reward-justification

Use when deciding whether to accept honors or rewards. Analyzes the true basis of your position—merit vs. relationship—and evaluates whether accepting creates contradictions that undermine legitimacy.

67

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./kg/ontology/ontology-v1/skus/procedural/skill_162/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

The body is concise, well-organized, and presents a clear sequenced workflow with explicit verification checkpoints. Its main weakness is actionability: the steps are framed as analytic questions rather than fully executable, decision-yielding instructions.

Suggestions

Convert each analysis step from an open question into an actionable decision rule with a concrete outcome (e.g. 'If position basis is relationship AND reward is merit-based, recommend declining').

Add a short decision matrix or worked example that maps the 5-step answers to an explicit accept/decline recommendation so the skill produces a determinate result.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: it lists numbered analysis steps and principles with no padding, no explanation of basic concepts, and no library/framework boilerplate, matching the level-3 'lean and efficient; every token earns its place' anchor.

3 / 3

Actionability

The guidance is concrete in framing (e.g. 'Why were you given authority? (Ability, relationship, or lack of alternatives?)') but offers only questions and principles rather than executable, decision-producing instructions; there is no code or command but also no specific procedure that deterministically yields an answer, so it sits at level 2 rather than fully actionable level 3.

2 / 3

Workflow Clarity

The analysis is sequenced as an explicit 5-step process and closes with a Verification section containing validation checkpoints ('Confirm that the basis... has been honestly identified before evaluating the reward', 'Check whether accepting creates a logical contradiction'), matching the level-3 anchor of a clear sequence with explicit validation steps.

3 / 3

Progressive Disclosure

This is a short, single-purpose skill (under 50 lines) with no need for external references; the content is organized into clear, well-labeled sections (Overview, Analysis Steps, Key Principle, Warning, Expected Outcome, Verification), so per the simple-skills scoring note it merits a 3 without separate files.

3 / 3

Total

11

/

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.

The description is well-formed with explicit what-and-when triggers and a clearly distinct niche, but its action list is analytic rather than enumerative and its trigger vocabulary covers only a narrow set of natural terms.

Suggestions

Broaden trigger-term coverage with natural synonyms a user would actually say, e.g. 'awards, gifts, promotions, bonuses, or other forms of recognition'.

Convert the analytic verbs into a more concrete enumeration of capabilities (e.g. 'classifies the basis of your position, tests for contradictions, and flags intermediary leverage') to lift specificity toward level 3.

DimensionReasoningScore

Specificity

The description names the domain ('accept honors or rewards') and several concrete analytic actions ('Analyzezes the true basis of your position—merit vs. relationship—and evaluates whether accepting creates contradictions'), but the actions are conceptual/analytic rather than a list of multiple concrete operations, so it sits at level 2 rather than level 3.

2 / 3

Completeness

It explicitly answers both 'what does this do' ('Analyzes the true basis... evaluates whether accepting creates contradictions that undermine legitimacy') and 'when should Claude use it' ('Use when deciding whether to accept honors or rewards'), matching the level-3 anchor for explicit what-and-when triggers.

3 / 3

Trigger Term Quality

'Use when deciding whether to accept honors or rewards' supplies a relevant trigger phrase, but the natural vocabulary users would say is thin (only 'honors or rewards'), missing common variations like 'award', 'gift', 'promotion', or 'recognition', so it does not reach the broad coverage of level 3.

2 / 3

Distinctiveness Conflict Risk

The niche is unusually specific (reward/honor acceptance and legitimacy analysis) and would not naturally overlap with other skills, with distinct triggers tied to that scenario; it matches the level-3 'clear niche with distinct triggers' anchor.

3 / 3

Total

10

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
baojie/shiji-kb
Reviewed

Table of Contents

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.