CtrlK
BlogDocsLog inGet started
Tessl Logo

counter-slander-defense

Use when facing coordinated disinformation or slander campaigns targeting your reputation. Identifies warning signs of bribery and planted criticism, and outlines defensive measures including transparent communication and alliance-building.

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_169/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.

The skill is a clean, well-organized single-file advisory with an explicit verification checklist, but its defensive steps are abstract guidance rather than concrete, executable specifics, and the outcomes section is mild filler.

Suggestions

Make each defensive measure concrete and specific — for each step, state exactly what to do or produce (e.g., a specific monitoring checklist, a documentation template) rather than generic directives.

Remove or compress the 'Expected Outcomes' section, which restates benefits Claude can infer from the measures themselves.

Where a step is not directly executable (e.g., 'Build independent alliances'), clarify what concrete action the user/agent can take, so the guidance is actionable rather than aspirational.

DimensionReasoningScore

Conciseness

The body is lean and well-sectioned, but the 'Expected Outcomes' section ('Understanding the mechanism helps prevent future vulnerability') states inferable benefits that Claude could derive, so it could be tightened.

2 / 3

Actionability

A structured numbered checklist plus a Verification section provides some concrete guidance beyond mere description, but steps like 'Maintain transparent communication with leadership' and 'Build independent alliances' are generic and lack specifics on how to actually execute each.

2 / 3

Workflow Clarity

A clearly numbered defensive-measures sequence is paired with a dedicated Verification section containing explicit validation checkpoints ('Confirm...', 'Validate...', 'Check...'), functioning as a checklist for the process.

3 / 3

Progressive Disclosure

At under 50 lines with no need for external references (no bundle files present), the content is well-organized into clearly headed sections, which is sufficient for a 3 on a simple single-file skill.

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 clearly states both purpose and trigger conditions with a distinctive niche, but its capability list stays at an abstract level and the trigger phrasing is more literary than the natural terms a user would speak.

Suggestions

Replace abstract capability verbs with concrete, specific actions (e.g., name the actual techniques or outputs the skill produces) to lift specificity toward 3.

Add common user-spoken variations alongside the formal terms (e.g., 'rumors', 'smear campaign', 'being set up') to broaden trigger-term coverage.

Keep the 'Use when...' clause but pair the formal phrasing with plainer language a user would actually type.

DimensionReasoningScore

Specificity

It names the domain and some actions ('Identifies warning signs of bribery and planted criticism', 'outlines defensive measures including transparent communication and alliance-building'), but these are abstract/meta-descriptions of capability rather than multiple concrete, specific actions.

2 / 3

Completeness

It explicitly answers both 'what' ('Identifies warning signs... and outlines defensive measures') and 'when' via an explicit 'Use when facing...' trigger clause.

3 / 3

Trigger Term Quality

Relevant keywords like 'disinformation', 'slander', and 'reputation' appear, but the phrasing is formal/literary ('coordinated disinformation', 'planted criticism') and lacks the common everyday variations a user would naturally say.

2 / 3

Distinctiveness Conflict Risk

The counter-slander/reputation-defense niche is specific with distinctive triggers ('coordinated disinformation or slander campaigns targeting your reputation'), making it unlikely to fire for unrelated 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.