CtrlK
BlogDocsLog inGet started
Tessl Logo

accepting-fair-weather-followers

Use when managing follower loyalty during adversity or processing feelings of betrayal after supporters depart. Applies the marketplace analogy (dawn crowds vs. dusk emptiness) to reframe departures as natural human behavior rather than personal betrayal, enabling magnanimous leadership.

62

Quality

72%

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

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 compact, well-structured instructional skill with a strong validation/feedback section and clear sequencing. The weakest dimensions are conciseness, which leans on truisms Claude already knows, and actionability, where the guidance stays attitudinal rather than concrete.

Suggestions

Trim universal-truth statements ('Death is inevitable', 'Wealth attracts many friends; poverty drives them away') to the minimum needed to anchor the marketplace analogy, since Claude already knows these.

Add one concrete example scenario or short sample dialogue showing how to welcome a returning follower without shame or demands, to move the guidance from attitudinal to directly applicable.

Consider collapsing the 'Core Principles' and 'Application to Leadership' bullets, which restate the analogy, to reduce overlap with the 'Steps for the Leader' section.

DimensionReasoningScore

Conciseness

The body is lean and well-organized, but several load-bearing lines state truisms Claude already knows ('Death is inevitable for all living things', 'Wealth attracts many friends; poverty drives them away'), fitting the 'mostly efficient but includes some unnecessary explanation' anchor; it is not a 3 because not every token earns its place against Claude's prior knowledge, and not a 1 because there is no padding or library/background exposition.

2 / 3

Actionability

It gives concrete behavioral dos and don'ts ('Do not demand loyalty oaths or apologies', 'Welcome them back when circumstances improve', 'Do not shame returning followers'), but the guidance is attitudinal rather than fully executable and lacks concrete scenarios or example dialogue, matching the 'some concrete guidance but incomplete' anchor; it is not a 3 because nothing is copy-paste ready, and not a 1 because specific directives are present rather than vague description.

2 / 3

Workflow Clarity

A clear sequenced 'Steps for the Leader' section is paired with an explicit 'Validation' section that forms a feedback loop ('if bitterness or desire for revenge persists ... revisit the framework', and checks on welcoming returning followers and long-term retention), matching the anchor for clear sequence with explicit validation steps and feedback loops.

3 / 3

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ absent) and the skill is a single-purpose document under 50 lines with well-organized sections (Overview, Core Principles, Steps, Expected Outcomes, Validation); per the simple-skills scoring note this earns a 3 for clear organization without external references.

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.

A well-constructed description with an explicit 'Use when' trigger, a clear what-statement, and a distinctive niche. Its main weakness is that the named actions are abstract attitudinal reframes rather than concrete operations, and the trigger terms lean literary over colloquial.

DimensionReasoningScore

Specificity

Names the domain and several actions ('managing follower loyalty during adversity', 'processing feelings of betrayal after supporters depart', 'reframe departures', 'enabling magnanimous leadership'), but these are abstract attitudinal actions rather than concrete operations, matching the anchor that names domain and some actions but is not comprehensive; it is not a 3 because no multiple concrete executable actions are listed, and not a 1 because the domain and actions are explicitly named.

2 / 3

Completeness

It explicitly answers both halves: an explicit 'Use when managing follower loyalty during adversity or processing feelings of betrayal after supporters depart' trigger, plus a what-statement ('Applies the marketplace analogy ... to reframe departures as natural human behavior rather than personal betrayal'), matching the anchor that clearly answers both what and when with explicit triggers.

3 / 3

Trigger Term Quality

Relevant keywords are present ('follower loyalty', 'adversity', 'feelings of betrayal', 'supporters depart'), but the phrasing is formal/literary and misses common colloquial variations a user would naturally say (e.g. 'my followers abandoned me', 'people left when things got hard'), fitting the 'some relevant keywords but missing common variations' anchor rather than full coverage.

2 / 3

Distinctiveness Conflict Risk

The niche is highly specific and distinctive ('marketplace analogy', 'fair-weather followers', 'magnanimous leadership', 'dawn crowds vs. dusk emptiness'), making it very unlikely to trigger for the wrong skill, matching the '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.