CtrlK
BlogDocsLog inGet started
Tessl Logo

managing-credit-humility

Use when navigating credit for achievements that involved rule-breaking or complex loyalties. Guides appropriate demeanor, ritual humility, and relationship preservation after morally ambiguous successes.

63

Quality

73%

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_166/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

The content is concise and cleanly organized with a verification section, but its steps read as abstract principles rather than concrete, executable behavioral guidance with error-recovery loops.

Suggestions

Make each step concrete and verifiable: instead of 'Deflect honors and rewards through ritual humility', give the actual phrasing or action (e.g., 'credit advisors by name and attribute the outcome to the team').

Extend Verification with an error-recovery loop: specify what to do if a relationship shows resentment after these steps (e.g., re-acknowledge the harm privately before any further public statement).

DimensionReasoningScore

Conciseness

The body is lean — a one-sentence overview, terse steps, and short principle/outcome/verification lists — with no padding or explanation of concepts Claude already knows, matching the level-3 anchor.

3 / 3

Actionability

Steps like 'Deflect honors and rewards through ritual humility' and 'Frame your actions as duty rather than favor' describe attitudes rather than concrete, executable actions, landing at level 2 rather than fully actionable guidance.

2 / 3

Workflow Clarity

A 7-step sequence and a separate Verification section are present, but the steps are loosely-coupled principles rather than a dependent workflow, and verification is confirm-only with no error-recovery feedback loop.

2 / 3

Progressive Disclosure

Under 50 lines with no need for external references and well-organized into Overview/Steps/Key Principles/Expected Outcomes/Verification sections, meeting the simple-skill exception for a level-3 score.

3 / 3

Total

10

/

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 an explicit 'Use when' trigger and a distinctive niche, but its capability language is somewhat abstract and its trigger terms lean literary rather than conversational.

Suggestions

Replace abstract phrasing like 'appropriate demeanor' with concrete actions (e.g., 'deflect praise, name the advisors you relied on, avoid claiming sole credit').

Add natural user-facing trigger phrasing (e.g., 'when someone thanks you for a result that involved bending the rules') alongside 'morally ambiguous successes' and 'complex loyalties'.

DimensionReasoningScore

Specificity

It lists several behaviors ('appropriate demeanor, ritual humility, and relationship preservation'), but 'appropriate demeanor' is abstract and the actions read as thematic domains rather than the concrete, copy-ready actions of a level-3 anchor.

2 / 3

Completeness

It explicitly answers both 'what' ('Guides appropriate demeanor, ritual humility, and relationship preservation') and 'when' with an explicit 'Use when' trigger, matching the level-3 anchor.

3 / 3

Trigger Term Quality

'credit for achievements' and 'rule-breaking' are plausible user phrases, but 'morally ambiguous successes' and 'complex loyalties' are literary rather than natural keywords a user would actually say.

2 / 3

Distinctiveness Conflict Risk

The domain (credit/humility after morally ambiguous successes) is a clear niche with distinct triggers unlikely to overlap with other skills.

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.