CtrlK
BlogDocsLog inGet started
Tessl Logo

explain-like-socrates

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

57

Quality

66%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/explain-like-socrates/SKILL.md

The canonical home for this skill is explain-like-socrates in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

67%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 content gives clear, actionable, well-sequenced guidance for a Socratic explanation style with concrete examples throughout, but carries redundant passages that inflate length without adding guidance value.

Suggestions

Remove duplicated reflection prompts between section 5 and TERMINATION, and consolidate the lecture-avoidance guidance that appears in both DO NOT and the prose, to tighten conciseness.

Trim or merge the DO/DO NOT block with the response-structure section, since the structure already implies most of the same dos and don'ts.

DimensionReasoningScore

Conciseness

The body is mostly efficient and on-point, but noticeable redundancy (reflection prompts repeated across section 5 and TERMINATION, lecture-avoidance stated in both DO NOT and prose, overlapping DO/DO NOT and structure sections) means it could be tightened, matching the 'mostly efficient but some unnecessary explanation' anchor.

3 / 5

Actionability

As an instruction-only skill it provides concrete, specific guidance: a 5-part response structure, quoted example patterns ('Suppose a system needed to remember...'), a worked analogy (vending machine), and example reflection/misconception responses, with only minor gaps keeping it below fully copy-paste-ready.

4 / 5

Workflow Clarity

The response is sequenced as a clear numbered 1-5 workflow (Curiosity Opening -> Reflection) with explicit handling branches for misconceptions, failure, and confusion (return to the analogy); no destructive or batch operations exist that would require validation checkpoints, so this is a clear sequence with minor gaps.

4 / 5

Progressive Disclosure

The skill is a single self-contained SKILL.md with well-organized, clearly headed sections separated by horizontal rules and no nested references; it is over 50 lines with some redundancy, so it sits at good structure rather than the lean optimal anchor.

4 / 5

Total

15

/

20

Passed

Description

66%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 cleanly states both what the skill does and when to use it with natural trigger phrases, but its capability statement is singular and its triggers are broad enough to risk overlap with generic explainers.

Suggestions

Add one or two more concrete capability verbs (e.g., 'guides reasoning through reflective questions and a single analogy') to lift specificity beyond a single action.

Tighten the trigger clause by dropping the awkward 'like socrates' or replacing it with a phrase that signals the Socratic style intent, reducing conflict with generic explanation skills.

DimensionReasoningScore

Specificity

The description names the domain ('Socratic-style dialogue') and one concrete action ('Explains concepts') but does not list multiple distinct capabilities, matching the anchor for naming a domain with 1-2 concrete actions rather than comprehensive coverage.

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'), with concrete trigger phrases; the 'what' is somewhat thin (a single action), so it does not reach the fully comprehensive anchor.

4 / 5

Trigger Term Quality

It surfaces several natural phrases users actually say ('explain', 'teach', 'help understand a concept'), giving good keyword coverage with synonyms, though the trailing 'like socrates' is an unusual trigger phrasing that keeps it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

The Socratic delivery style is a genuine niche, but the trigger terms ('explain', 'teach', 'help understand') are generic and would match many general explanation skills, leaving real overlap risk rather than a clearly distinct trigger surface.

3 / 5

Total

14

/

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.

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