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.

64

Quality

76%

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

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 concise, well-organized instruction skill with a clear sequenced workflow and explicit verification checkpoints; its main weakness is actionability depth and the lack of a concrete worked example.

Suggestions

Add a short worked example (a brief scenario walked through the 5 steps) to push actionability toward 5.

Make the verification feedback loop explicit, e.g., 'If a contradiction is found in step 4, revisit the basis identified in step 1 before deciding', to lift workflow clarity to 5.

Trim the Overview/Expected Outcome sections, which restate the frontmatter description and Key Principle, to recover a few tokens toward conciseness 5.

DimensionReasoningScore

Conciseness

The body is lean with short bulleted sections and no padding of concepts Claude already knows; only minor redundancy (Overview re-states the frontmatter, Expected Outcome overlaps the Key Principle) keeps it off 5.

4 / 5

Actionability

Each step poses a concrete diagnostic question with enumerated options (e.g., "Why were you given authority? (Ability, relationship, or lack of alternatives?)"), giving mostly actionable guidance; the gap is the absence of a worked example.

4 / 5

Workflow Clarity

A clear 5-step numbered sequence is paired with a dedicated Verification section of three checkpoints; it falls short of 5 because the feedback loop is implicit rather than an explicit 'if check fails, return to step N'.

4 / 5

Progressive Disclosure

At under 50 lines, single-purpose, with no need for external references and well-organized section headers, it meets the simple-skill exception that allows a 5 on organization alone.

5 / 5

Total

17

/

20

Passed

Description

75%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-structured description that cleanly answers both what and when for a distinct niche, though the action list and trigger-term coverage could be more comprehensive.

Suggestions

Add 1-2 more concrete actions (e.g., 'maps the intermediary's incentives', 'forecasts legitimacy costs') to lift specificity from 3 toward 4-5.

Broaden trigger terms with common synonyms such as 'awards', 'recognition', 'praise', or 'gifts' so users phrasing it differently still surface the skill.

DimensionReasoningScore

Specificity

Names the reward-justification domain and two concrete actions ("Analyzes the true basis of your position", "evaluates whether accepting creates contradictions"), but the coverage is not comprehensive enough for a 4.

3 / 5

Completeness

It explicitly answers both what ("Analyzes the true basis… and evaluates whether accepting creates contradictions") and when ("Use when deciding whether to accept honors or rewards") with a concrete trigger phrase.

5 / 5

Trigger Term Quality

The trigger "deciding whether to accept honors or rewards" supplies relevant natural keywords (honors, rewards, accept), but the niche domain omits common synonyms a user might say such as awards, recognition, or gifts.

3 / 5

Distinctiveness Conflict Risk

The honor/reward justification niche has a distinct, specific trigger with minimal overlap risk against other skills.

5 / 5

Total

16

/

20

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.