CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

explain-like-socrates

Explains concepts using Socratic-style dialogue. Use when the user asks to explain, teach or help understand a concept like socrates.

Quality

80%

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 ./skills/explain-like-socrates/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

73%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 well-structured, actionable style guide with concrete example phrasings, a clear five-stage response sequence, and explicit feedback and termination handling. Its main weakness is redundancy — Tone, Reflection, and Termination repeat guidance already stated elsewhere — which costs tokens without adding new instruction.

Suggestions

Merge the Tone section into the intro and fold Termination into Reflection to remove repeated lecture-avoidance and closing-prompt guidance, cutting token cost without losing instruction.

Trim the three reflection-prompt examples to one; the bolded variant adds no new guidance.

Add one short worked example exchange showing the full five-stage pattern end-to-end to make the style fully concrete and lift actionability.

DimensionReasoningScore

Conciseness

Mostly efficient directive lists, but redundancy inflates the token budget: the Tone section repeats the intro's lecture-avoidance guidance, Termination overlaps Reflection, and three reflection-prompt variants are given where one would do. It is not the several-padded-sections verbosity of a 2, but clearly could be tightened.

3 / 5

Actionability

Concrete example phrasings for each stage ('Suppose a system needed to remember something from a previous step. What benefit might that give us?', the vending-machine analogy, 'That is an interesting way to see it. But consider this…') make the style executable. A full worked example dialogue showing all five stages end-to-end would close the gap to 5; it is well above the high-level-hints level of 2-3.

4 / 5

Workflow Clarity

Five numbered response stages (Curiosity Opening, Guided Reasoning, Single Analogy, Clarification, Reflection) in a clear sequence, with explicit feedback loops for error recovery ('If the user remains confused: Return to the analogy and simplify the reasoning', the 3-step misconception handling) and explicit termination criteria. This is a conversational style skill with no destructive or batch operations, so the validation cap does not apply.

5 / 5

Progressive Disclosure

A single-file instruction skill with clear section headers and no external references needed; nothing belongs in a separate file. Minor organization gaps: the Tone and Termination sections duplicate guidance already covered elsewhere, and heading levels alternate between single-# and double-## sections. Not a 5 because the section consolidation is imperfect, well above the unstructured monolith of a 1-2.

4 / 5

Total

16

/

20

Passed

Description

78%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 strong description that clearly and explicitly states both what the skill does and when to use it, with natural trigger terms and a distinctive Socratic framing. Its only weaknesses are a single-action capability statement and slightly awkward trigger phrasing that leaves minor overlap risk with general teaching skills.

DimensionReasoningScore

Specificity

'Explains concepts using Socratic-style dialogue' names the domain plus one concrete action, matching the 'names domain and 1-2 concrete actions' anchor; it does not list the several specific actions needed for a 4, and is clearly above the domain-only level of 2.

3 / 5

Completeness

It explicitly answers both what ('Explains concepts using Socratic-style dialogue') and when ('Use when the user asks to explain, teach or help understand a concept like socrates') with concrete trigger phrases, matching the top anchor; the missing-use-when cap does not apply.

5 / 5

Trigger Term Quality

'explain, teach or help understand' plus the distinctive 'like socrates' hook are natural phrases users would say, giving good keyword coverage; common variants like 'clarify', 'what is X', or 'how does X work' are missing, keeping it below a 5.

4 / 5

Distinctiveness Conflict Risk

The Socratic framing carves a mostly distinct niche with the 'like socrates' qualifier, but the broad trigger verbs ('explain', 'teach') carry minor overlap risk with general explanation skills, and the trailing phrase 'a concept like socrates' is slightly ambiguous.

4 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

skills/explain-like-socrates/SKILL.md

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.