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.

60

Quality

75%

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

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

The body is a concise, well-organized instruction-only skill with a clear sequence and verification checkpoints. Its main weakness is actionability: directives are abstract and would benefit from concrete sample language.

Suggestions

Add 1–2 concrete examples of what to actually say (e.g., a sample public statement framing credit as duty) to lift actionability.

Tighten the overlap between the Steps list and Key Principles so each section earns its place.

Optionally add a brief feedback loop in Verification (what to do if a checkpoint fails) to approach full workflow clarity.

DimensionReasoningScore

Conciseness

Lean, well-structured body with no padding or explanations of concepts Claude already knows; minor redundancy between the Steps and Key Principles sections could be tightened.

4 / 5

Actionability

Steps give clear directives ('Deflect honors and rewards through ritual humility') but lack concrete examples such as sample phrasing or scripts to actually say, leaving key execution details implicit.

3 / 5

Workflow Clarity

A clearly sequenced 7-step process is paired with a Verification section containing explicit checkpoints (confirm advisors consulted, validate harm acknowledged, check duty framing); minor gaps in error-recovery feedback loops.

4 / 5

Progressive Disclosure

Under 50 lines with no external references needed and well-organized sections (Overview, Steps, Key Principles, Expected Outcomes, Verification), satisfying the simple-skill exception for full marks.

5 / 5

Total

16

/

20

Passed

Description

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

The description clearly states both what the skill does and when to use it, with concrete actions and a distinct niche. Trigger term coverage and specificity could be broadened with more synonyms and explicit user phrasings.

Suggestions

Add natural user phrasings and synonyms to the 'Use when' clause (e.g., 'when the user asks how to handle credit, deflect praise, or respond to ambiguous loyalty situations').

Expand the action list slightly to be more comprehensive (e.g., add 'framing success as duty' or 'acknowledging harm') so specificity approaches full coverage.

Keep the third-person voice but surface 1–2 more concrete trigger keywords users would actually say aloud.

DimensionReasoningScore

Specificity

Names the domain ('navigating credit for achievements that involved rule-breaking') and lists several concrete actions ('appropriate demeanor, ritual humility, and relationship preservation'), with minor coverage gaps.

4 / 5

Completeness

Both 'what' ('Guides appropriate demeanor, ritual humility, and relationship preservation') and an explicit 'when' ('Use when navigating credit for achievements that involved rule-breaking or complex loyalties') are present, though the trigger could list more concrete phrases.

4 / 5

Trigger Term Quality

Relevant natural terms appear ('credit', 'humility', 'loyalties', 'morally ambiguous') but common variations and synonyms a user might say are missing, so coverage is partial rather than comprehensive.

3 / 5

Distinctiveness Conflict Risk

A clear niche (credit/humility after morally ambiguous successes) with distinct triggers; minor overlap risk with general relationship or communication skills.

4 / 5

Total

15

/

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.

Validation — 16 / 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.